![]() Only administrators of the account can add new users. Please note there are rare exceptions to being able to refund via our Search or POS, due to bank restrictions or card restrictions (based on amount, cardholder policy, etc) or configuration restrictions set between the merchant and E-xact. Refunds can be conducted in Search by selecting the particular transaction record you would like to refund, or in POS screen. Please note only the last 4 digits of the credit card numbers are visible. You can view approved and declined transactions and read a transaction detail for each one sent to E-xact’s system. ![]() Under Transactions, transactions can be found by a variety of parameters including cardholder name, date, card type. Within this area you can view the transactional activity of the merchant customer.Ī demonstration of RPM functions is available upon login. Simply enter the User Login and password you have received from E-xact or your customer. Developers should access this area to monitor production-level testing.Read Only – no access to POS and refund functions.To view transactions in the Production Account, please refer to the information below.Įach E-xact customer receives User logins and passwords for E-xact’s RPM accessed on our website. The pre-authorization will remain for a few days on the cardholder’s card. The bank may view this as “mischievous” conduct on the card.Īlso note that pre-authorizations will only be charged to a cardholder if they are followed by a pre-authorization completion. Don’t forge an expiration date or name.It can alert banks of possible “mischievous activity” and could result in Make sure to refund any purchases made with the card.We suggest you input small currency amounts such as a cent or a dollar so as to not exceed any credit limit on the card. You will shortly exceed the credit limit on the card, and possibly block the cardholder’s card. ![]() E-xact does not have test credit card numbers for production-level transactions. ![]() If you decide to test the production environment with real credit cards, please use common sense. Testing with credit cards within the production environment Developers should test further to see that the Production environment is connecting properly. Once the Production IDs are entered into E-xact’s component software, the connection to E-xact’s servers and the bank networks has been established. Production IDs are passed along after the merchant has completed registering with E-xact. Testing with valid test credit cards within the test environment You can sign up for a test account, here: You can send test transactions through to our gateway and receive a response back from our network to verify that the transactions are being communicated properly between you and E-xact. With an E-xact Test Account, you can simulate the interaction between your software and/or server and E-xact’s servers. The E-xact Production ID is only set after the merchant customer has completed their registration with E-xact. When you are ready to move from Test mode to Production mode (which means you are ready to send live transactions through to the banks), you will have to replace the Test Account ID with the E-xact Production ID. E-xact Production ID (for production environment).Individual Test Account IDs (optional, for test environment).The IDs you will receive consist of:Īs a developer there are a series of Payment Gateway IDs you will encounter: The codes also establish the interaction between the E-xact software you integrated into your solution and our payment servers. The Domain Names and their IP addresses are stored on the local computer in a configuration file.Į-xact’s system uses a Payment Gateway ID and Gateway Password, to identify an individual’s E-xact payment gateway. If the component is unable to connect to the primary Domain, a connection to the Secondary domain is attempted. Each component has two domain names (Primary, Secondary). The components connectivity point is managed through a Domain Name. All data passing through that connection is encrypted using a 448 bit private key. The E-xact remote component connects to the transaction-processing network via a standard IP socket connection. Installation Instructions - For installation instructions for the various E-xact’s APIs please refer to the Read Me file and various help files found in the API version package you are implementing. The E-xact Developer Implementation Guide is intended to outline the basic services and functionality of E-xact’s transactional processing services gateway and software. Click and scroll to view topics regarding Developer Implementation:
0 Comments
Leave a Reply. |