If a transaction fails, we provide response text to explain why. Transactions can fail at the processor level (response=2) or gateway level (response=3). Here’s a list of common failure response texts and what they mean.
response=2
The card issuer is rejecting the charge. Common response texts are below, though a more complete list is listed in the Response section of the API you are using.
| Auth Decline | Most common decline message. Issuer does not specify the reason for refusing the transaction. |
| Do Not Honor | Issuer does not specify the reason for refusing the transaction. |
| Credit Floor | The cardholder has reached their credit limit. |
| Fraudulent Card | The card has been reported stolen. |
| Call Voice Oper | The issuer is requiring that you obtain an authorization on the phone before they will approve the transaction. |
response=3
The gateway is making the transaction fail due to a formatting issue with the data or a permission or option setting. Here are some common response texts
| Authentication Failed | IP Restrictions or user permissions are causing the failure. |
| Expired Hash | The hash must be created within 15 minutes of the current UTC time. |
| Invalid card number | The card number is not formatted correctly, such as the wrong number of digits or includes characters other than numbers. |
| Invalid Transaction Id | The referenced Transaction ID does not exist. |
| Invalid Customer Vault Id | The referenced Customer Vault ID does not exist. |
| Duplicate transaction | You have the option to reject duplicate transactions, matching card number, expiration date, and amount. Please contact us to determine what your duplicate transaction checking is currently set at or to adjust this timeframe. |
| You do not have permission to use the customer vault | You need to sign up for the vault if you haven’t done so, or we need to enable it for you. |
| Credits are not enabled | We need to enable your account to issue the credit transaction type. |