Test Cards and Conventions
Find the test cards for testing your Cards Connect integration and get info on testing conventions we use
Card Present Gateway
If you want to access information about our in-store offering, you may check the API specifications here: In-store Transactions Overview
Cards Connect enables to you to simulate various scenarios during the integration phase. You can use the following test cards with to simulate basic transaction responses. You may also check the testing conventions section to learn how to simulate various other cases such as a timeout or a specific decline code for a specific type of operation.
Conventions override the test cards table
When testing, if the data you use falls into any of the conventions, the behaviour of the Cards Connect will follow the convention even if you use a test card from the list below.
Test Cards
| Scheme | Number | MM/YY | CVV | Behaviour |
|---|---|---|---|---|
| MasterCard | 5200000000001021 | 05/26 | 123 | Succeeded |
| MasterCard | 5128998784151707 | 09/26 | 884 | Succeeded |
| MasterCard | 5128998785153405 | 09/26 | 611 | Succeeded |
| MasterCard | 5128998786159203 | 09/26 | 964 | Succeeded |
| MasterCard | 5128998787153908 | 09/26 | 816 | Succeeded |
| MasterCard | 5128998789150407 | 09/26 | 386 | Succeeded |
| MasterCard | 5468272429106106 | 09/26 | 345 | Succeeded |
| MasterCard | 5353181800226466 | 09/26 | 488 | Succeeded |
| MasterCard | 5217291800071493 | 09/26 | 523 | Succeeded |
| MasterCard | 5313575350116622 | 09/26 | 123 | Succeeded |
| MasterCard | 5163202033964952 | 09/26 | 123 | Succeeded |
| Visa | 4265581110647303 | 09/26 | 143 | Succeeded |
| Visa | 4265581210649704 | 09/26 | 090 | Succeeded |
| Visa | 4265581600645908 | 09/26 | 755 | Succeeded |
| Visa | 4265581900642308 | 09/26 | 608 | Succeeded |
| Visa | 4560049630210608 | 09/26 | 249 | Succeeded |
| Visa | 4619760000001226 | 09/26 | 123 | Succeeded |
| Visa | 4940521800534554 | 09/26 | 234 | Succeeded |
| Visa | 4532241800007444 | 09/26 | 123 | Succeeded |
| Visa | 4530303102263620 | 09/26 | 123 | Succeeded |
| Visa | 4530303000000819 | 09/26 | 123 | Succeeded |
| Visa | 4564712075088849 | 09/26 | 123 | Succeeded |
| AMEX | 374245455400001 | 09/26 | 4455 | Succeeded |
| AMEX | 376345698745234 | 09/26 | 5566 | Succeeded |
| AMEX | 376245698745236 | 09/26 | 6677 | Succeeded |
| AMEX | 376045698745230 | 09/26 | 7788 | Succeeded |
| AMEX | 376055698745239 | 09/26 | 8899 | Succeeded |
| AMEX | 376445698745232 | 09/26 | 1234 | Succeeded |
| JCB | 3569990010025723 | 09/26 | 1234 | Succeeded |
| QCard | 6015310153858082 | 09/26 | 123 | Succeeded |
| MasterCard | 5200000000001005 | 05/26 | 123 | Accepts authorization Delays capture by 2 seconds - simulates async capture |
| MasterCard | 5200000000001013 | 05/26 | 123 | Successful auth with a delay of 2 seconds |
| MasterCard | 5146199376518886 | 05/26 | 123 | Response code = 16 Approved; update track 3 |
| MasterCard | 5200000000001047 | 05/26 | 123 | Times out the authorization |
| MasterCard | 5200000000001054 | 05/26 | 123 | Capture times out |
| Visa | 4520896015320538 | 05/26 | 123 | Response code = 11 Approved; VIP |
Testing Based on Conventions
Aside from the cards above, there are certain conventions which may vary the behavior/outcome of transaction operations. These conventions react based on the following values, regardless of PAN / Expiry combinations.
- Transaction value
- CVV inputs
The conventions below are processed in the following order.
Convention 1: Simulating Switch Failure
All transactions with a value between 95 and 99 cents will automatically time out the initial request. Cards Connect will undertake the necessary compensating actions, ensuring that the resolution is dynamic.
As a result, this convention will influence the behaviour of Cards Connect for integrators to experience the API responses and webhook notifications.
The severity of the failure and compensation is controlled by the higher cents value as tabled below. Duration columns represent the probability for time to resolution.
| Cents Value | Chance of Resolving Failure | 5 mins | 45 mins | 2h 11mins | 19h 12mins |
|---|---|---|---|---|---|
| 95 | 35% | 95.7% | 99.47% | 99.81% | 99.9975% |
| 96 | 45% | 90.88% | 98.15% | 99.16% | 99.830% |
| 97 | 55% | 83.86% | 94.96% | 97.23% | 99.160% |
| 98 | 65% | 72.53% | 88.39% | 92.45% | 96.813% |
| 99 | 75% | 57.81% | 76.23% | 82.20% | 89.980% |
Possible examples:
- A transaction may time out and automatically reverse if the transaction value is $77.99.
- A transaction receives approval during the authorization phase (utilising test cards or convention 2). When a capture of $1.99 is processed, the API will respond with "accepted"; however, there may be a delay in the webhook for the successful acknowledgement of the capture.
- A transaction is approved and captured using either test cards or convention 2. If a refund of $2.96 is initiated, it will timeout, resulting in an automatic reversal of the refund. Additionally, the webhook notification regarding the failed outcome will be delayed.
Convention 2: Custom Response Codes with Transaction Value
The motivation behind this behaviour is to manipulate the response codes issued by the schemes, in accordance with the ISO 8583:1987 publication of response codes.
This convention is divided into two components, which break down the transaction value (XXXyy) into dollars (XXX) and cents (yy):
- The dollar value (XXX) serves as the pre-qualifier that indicates the stage of the transaction at which the response code will be manipulated.
- The cents value (yy) is then utilised to return the transaction response code.
| Dollar Value | Cards Connect API Equivalency | Notes |
|---|---|---|
| $100 | Authorization | Useful for simulating the various kinds of approval modes, fraud, card restrictions, and similar. |
| $420 | Voids | Useful to illustrating async behavior and Cards Connect business resolution as an acquirer |
| $220 | Captures | Useful to illustrating async behavior and Cards Connect business resolution as an acquirer |
| $200 | Refunds | Simulating cards which were marked as stolen subsequent to an authorization |
Example:
- PAN: Any variation
- Expiry: Current or future dated (Cards Connect validation rule)
- Transaction amounts
- $100.11 - Transaction is approved as a VIP
- $100.31 - Transaction decline as bank not supported by switch
- $100.41 - Declined as card is marked stolen
- $200.41 - Transaction is approved, capture will also be successful; but upon refund the response code marks the card as stolen
Convention 3: CVV Match Type
Any cards entered with the following CVV will return the following CVV match type represented as cvvResponseCode in the API response
| CVV | Outcome |
|---|---|
| 000 0000 | Not Matched |
| 111 1111 | Not Matched |
| 222 2222 | Not Processed |
| 333 3333 | Suspicious |
| 999 9999 | Unknown |
Updated about 1 month ago