Credit card decline and error codes
Objective
Understand what credit card decline and error codes mean on the transaction page and what steps to take based on the code series.
Solution
When a credit card transaction is declined, Jackrabbit displays the response received from the payment gateway or processor. Some decline messages provide a clear reason, while others are more general.
Decline codes are not created by Jackrabbit and may vary by payment partner or issuing bank. If the decline was issued by the cardholder’s bank, the cardholder may need to contact their bank for the exact reason.
Â
Understand the code series
Decline and error codes are generally grouped by series. The series can help determine the next step.
Â
| Code series | What it usually means | Recommended action |
|---|---|---|
| 200 series | The transaction reached the processor or issuing bank and was declined. | Have the cardholder contact the issuing bank for more information. |
| 300 series | The transaction was rejected before it reached the processor. This may happen if the transaction type is not supported, the account is not configured for that payment method, or the transaction appears to be a duplicate. | Review the decline message. If the message is unclear, contact Support so the transaction response can be reviewed. |
| 400 series | The decline may be related to a setup, configuration, or processor communication issue. | Contact Support so the payment setup and transaction response can be reviewed. |
Â
Additional decline code references
Decline and error code wording can vary by payment partner. Support may use payment partner resources when researching a specific transaction.
- Legacy ePayment Partner decline codes – Use for legacy gateway or processor responses.
- Jackrabbit Pay refusal reasons – Use for Jackrabbit Pay transaction responses.
For help with a specific decline code, contact Support so the decline can be reviewed.
Â