Whilst integrating or otherwise testing, transactions can be performed in test mode for all payment types. Test transactions are visible and searchable in the backoffice but do not impact actual settlement, and can be differentiated by inspecting the IsTestTxn flag in the TxnResp object returned by the payment call (2-party), ResultKey or WebHook call (3-party).
Specific responses can be obtained for test mode transactions to test the various scenarios likely to be encountered whilst processing payments.
Card Type: | Card Number: |
---|---|
MasterCard | 5123456789012346 |
MasterCard 2 Series | 2720010040360012 |
Visa | 4987654321098769 |
American Express | 345678901234564 |
Diners | 30123456789019 |
JCB | 3530111333300000 |
While performing test mode transactions, specific parameters can be provided to obtain specific simulated bank response codes (see section TxnResp Responses).
Response codes between 00 and 99 can be obtained in one of two ways:
A normally formatted, future-dated expiry date can be provided, in which case the response code will be the same as the last two digits of the provided transaction amount. For example, with an expiry date of 1121 (11/21) and an amount of 12011 ($120.11), a bank response code of 11 will be returned.
Specifying a CVN of 987 will result in the bank response code of 05 being returned for all amounts and standard expiry dates.
The following CVN values can be submitted to obtain the listed simulated CVN responses responses:
CVN: | CVN Response: | Bank Response Code: |
---|---|---|
987 | N | 05, regardless of amount or expiry date |
876 | P | Determined by amount or expiry date (see section Simulating bank response codes) |
765 | U | Determined by amount or expiry date (see section Simulating bank response codes) |
All others | M | Determined by amount or expiry date (see section Simulating bank response codes) |
CVN responses:
To simulate a timeout, an amount of 11199 ($111.99) can be specified. This will result in a 50 second delay before a PT_G5 response code is returned.