Sandbox Testing
Test Cards
PCI requires us and you to use test card numbers when testing. You should never use a real Card Number in the Sandbox Environment. We provide various test cards Test Cards for various scenarios for your use.
How to specify an Amount Value?
In order to handle international currencies, an Amount is a String.
International currencies:
- use either a point or a comma as their decimal mark and might have a maximum of 0, 1, 2, 3, or 4 decimal places.
For example, when using currency number 840, USD, an Amount must have a decimal point (.) with 2 decimal digits and no commas (,) nor currency sign ($). Examples:
| 1000.20 | Valid |
| 1.20 | Valid |
| 0.20 | Valid |
| .20 | Valid |
| .4 | Invalid, 2 decimal digits are required |
| 1.4 | Invalid, 2 decimal digits are required |
| 1,000.21 | Invalid, comma not needed |
| $10.21 | Invalid, dollar sign not needed |
How to generate an error in the Sandbox Environment? (Create Transaction)
For Create Transaction, the Amount is used to trigger various errors while processing the Create Transaction request in the Sandbox Environment (Accel uses a 3-digit Network Response Code):
| Amount | Response | Actual Response | Error Description | |||
|---|---|---|---|---|---|---|
| Status Code | Network Response Code | Resource Status | Network Response Code | Resource Status | ||
| 0.01 | 200 | ZZ (or 999) | ERROR | ZZ (or 999) | ERROR | Transaction Error |
| 0.02 | 207 | UNKNOWN | UNKNOWN | Transaction Processing Failed | ||
| 0.03 | 200 | 00 (or 000) | COMPLETED | 00 (or 000) | COMPLETED | Transaction Successful, but upstream processing was delayed for 30 seconds |
| 0.04 | 207 | UNKNOWN | 00 (or 000) | COMPLETED | Transaction Successful, but upstream processing was delayed for 40 seconds | |
How to generate an error in the Sandbox Environment? (Delete Transaction)
For Delete Transaction, the Create Transaction Amount is used to trigger various errors while processing the Delete Transaction request in the Sandbox Environment (Accel uses a 3-digit Network Response Code):
| Amount | Create Transaction Response | Delete Transaction Response | Error Description | ||||
|---|---|---|---|---|---|---|---|
| Status Code | Network Response Code | Resource Status | Status Code | Reversal Network Response Code | Resource Status | ||
| 0.07 | 200 | 00 (or 000) | COMPLETED | 200 | ZZ (or 999) | UNKNOWN | Reversal Request failed |
| 0.08 | 200 | 00 (or 000) | COMPLETED | 200 | 21 | UNKNOWN | Reversal Request failed, the Reversal was too late.
Not available when routed to any Regional Network: Currently only STAR and Accel. |
How to generate an error in the Sandbox Environment? (AVS, CVV2)
For AVS, Query Card, the Zip Code, Address, and Security Code are used to trigger various conditions while processing an AVS request in the Sandbox Environment:
| Request | Response | Comments | |||||
|---|---|---|---|---|---|---|---|
| Zip Code | Address | Security Code | Response Text | Network Response Code | Code | AVS Results | Security Code Results |
| *Any* | *Any* | None | NOT DECLINED | 85 | Y | Zip Code and Address were matched | |
| *Any* | None | None | NOT DECLINED | 85 | Z | Zip Code was matched | |
| *Any* | Any or None | *Any* | DEPENDS | DEPENDS | DEPENDS | M | Depends upon if Zip Code and Address matches or not, but Security Code was matched |
| *Any* | Any or None | 999 | DECLINE | 05 | DEPENDS | N | Depends upon if Zip Code and Address matches or not, but Security Code was not matched |
| 99990 | Any or None | Any or None | DECLINE | 05 | U | Information not available | |
| 99991 | Any or None | Any or None | DECLINE | 05 | R | AVS unavailable, retry | |
| 99992 | *Any* | None | DECLINE | 05 | A | Zip Code was not matched, but Address was matched | |
| 99992 | None or 999 Bad | None | DECLINE | 05 | N | Zip Code and Address were not matched | |
| 99993 | Any or None | Any or None | DEPENDS | DEPENDS | DEPENDS | DEPENDS | AVS Request delayed for 30 seconds |
| 99994 | Any or None | Any or None | UNKNOWN | UNKNOWN | UNKNOWN | UNKNOWN | AVS Request timed out |
- Any* - Any Zip Code that is not explicitly used to trigger a condition (99990-99994)
- Any* - Any Address that is not explicitly used to trigger a condition (999...) - Address only checks the
Street Number - Any* - Any Security Code that is not explicitly used to trigger a condition (999)
How to generate a RTP error in the Sandbox Environment?
For Create Transaction, the Account Number for RTP is used to trigger various errors while processing the Create Transaction request in the Sandbox Environment (RTP uses a 3-character Network Response Code):
| Account Number | Create Transaction Response | Error Description | ||
|---|---|---|---|---|
| Status Code | Network Response Code | Resource Status | ||
| 100000000...111111111 | 200 | 000 | COMPLETED | N/A |
| 111111112 | 200 | P04 | ERROR | Invalid Account |
| 111111113 | 200 | P11 | ERROR | Sender not authorized |
| 111111114 | 200 | P07 | ERROR | Participant blocked |
| 111111115 | 200 | P02 | ERROR | Invalid Account |
| 111111116 | 200 | P11 | ERROR | Transaction forbidden on this account |
| 111111117 | 200 | P23 | ERROR | Amount received is not the amount agreed or expected |
| 111111118 | 200 | P23 | ERROR | Amount exceeds limits |
| 111111120 | 200 | P21 | ERROR | Incorrect routing number |
| 111111121 | 200 | P14 | ERROR | Participant deceased |
Updated over 1 year ago