How to test card transaction flows.
You should test your card transaction flows without submitting real authorizations to the card networks. To do set, add the POST field below as part of any card transaction API call.
| Field Name | Format | Description |
|---|---|---|
| test | Integer | Set to 1 to test transactions. |
Testing Transaction Declines
Card transaction declines are simulated by sending a CVV2 value of 200 or larger. The table below shows the various decline codes that you can generate.
| CVV Input | Response | Message |
|---|---|---|
| 200 | 0 | DECLINED - Do not honor due to CVV2 mismatch\failure |
| 201 | 0 | PICK UP CARD - Pick up card |
| 202 | 0 | AMOUNT ERROR - Tran Amount Error |
| 203 | 0 | AMT OVER SVC LMT - Amount is more than established service limit |
| 204 | 0 | APPL TYPE ERROR - Call support for help with this error |
| 205 | 0 | CANNOT CONVERT - Check is ok, but cannot convert. Do Not Honor |
Testing Address Verification Service (AVS) Responses
Card networks provide an address verification service (AVS) as part of card authorizations. You can also test various responses by sending a specific CVV.
| CVV Input | Response | Message | AVS Response | CVV Response |
|---|---|---|---|---|
| 100 | 1 | APPROVED | X | M |
| 101 | 1 | APPROVED | X | P |
| 102 | 1 | APPROVED | X | S |
| 103 | 1 | APPROVED | X | U |
| 104 | 1 | APPROVED | X | N |