Testing Amounts
Overview
To test various transaction scenarios without using different card numbers, you can use specific transaction amounts in your test requests. When you submit a payment with these designated amounts, we will return specific response codes and decline reasons, allowing you to validate your integration's handling of different outcomes.
This testing method is particularly useful for simulating specific decline scenarios and testing your error handling without needing multiple test card numbers.
Test amounts
Submit the following amounts in your test transactions to receive the corresponding response:
| Amount | Status | Reason | Description |
|---|---|---|---|
| 101 | declined | generic_decline | Issuer returned a generic decline. |
| 204 | declined | expired_card | The card has expired. |
| 216 | declined | invalid_avs | The Address Verification System (AVS) check failed. |
| 217 | declined | invalid_pin | The PIN entered is invalid. |
| 218 | declined | closed_account | Issuer could not locate the bank account associated with the card number. |
| 251 | declined | suspected_fraud | Issuer classified the transaction as fraudulent. |
| 301 | declined | insufficient_funds | The cardholder has insufficient funds to complete the transaction. |
| 321 | declined | cardholder_cancellation | The cardholder has requested the transaction be cancelled. |
| 323 | declined | restricted_card | The card has restrictions that prevent this transaction. |
| 324 | declined | invalid_cvv | The CVV provided is invalid. |
| 325 | declined | expired_card | The card has expired. |
| 401 | declined | suspected_fraud | Issuer classified the transaction as fraudulent. |
| 402 | declined | lost_or_stolen | The card has been reported as lost or stolen. |
| 10.99 | declined | generic_decline | Issuer returned a generic decline. |
| 565 | declined | soft_decline | A soft decline was received; the transaction may be retried. |
Refunds
Test refund functionality by submitting a refund request against a successful transaction. Use any amount for refund testing—the refund will be processed regardless of the original transaction amount.
When testing refunds:
- The original transaction must have a
successstatus - Submit the refund amount you wish to refund (full or partial)
- The refund will be processed and return a successful response
Voids
Test void functionality by submitting a void request against a pending or recently authorized transaction. Voids must be submitted before the transaction has been settled.
When testing voids:
- The original transaction must be in a
pendingorauthorizedstate - Submit a void request using the transaction ID
- The void will be processed and return a successful response
- Voided transactions will have a status of
voided
Updated about 8 hours ago