Credit Card Declines

When a card is declined by the issuing bank or the card network, the gateway returns code 0205 with a specific decline reason in the TEXT field. All card declines share the same code — inspect TEXT to distinguish between reasons.

This is distinct from gateway-level errors:

  • 0205 — the transaction reached the card network and was declined by the issuer.
  • 9xxx — the gateway rejected the request before it reached the card network (usually validation). See Hosted Payment Errors.
  • 1xxx — setup, request format, or network transport issues. See Direct Payment Errors.

Decline Reasons

Grouped by how you should handle them and what (if anything) to show the customer.

Retryable — Tell the Customer to Try Again

The transaction failed for a reason that might not repeat. Safe to let the customer retry with the same card or try a different one.

TEXTDescription
NSFInsufficient funds.
EXCEEDS AMT LIMITThe transaction exceeds the card's per-transaction or daily limit.
REQ EXCEEDS BALANCERequest exceeds the card's available balance.
DECLINEGeneric decline with no specific reason from the issuer.

Customer-facing message: "Your card was declined. Please check with your bank or try a different card."

Card Can't Be Used — Customer Needs a New Card

The card on file isn't usable. Don't retry — the customer needs different card details.

TEXTDescription
EXPIRED CARDThe card has expired.
INVALID CARDThe card number is invalid.
CLOSEDThe card account is closed.

Customer-facing message: "This card can't be used. Please update your card details."

Verification Failed — Check CVV

The card was otherwise valid but the CVV or CAM check failed.

TEXTDescription
DECLINE: CVV2The CVV didn't match the issuer's records.
INVALID CAM/CVVCard authentication method or CVV validation failed.

Customer-facing message: "The security code on your card doesn't match. Please check the CVV and try again."

Security — Do Not Reveal Details

The issuer has flagged the card for security reasons. Never tell the customer why — direct them to their bank instead.

TEXTDescription
SUSPECTED FRAUDThe issuer flagged the transaction as potential fraud.
BLOCKEDThe card has been blocked — often seen on the first use of a newly issued card.
CALL AUTH CENTERThe issuer is requiring you to call the number on the back of the card.
PICK UP CARDThe issuer has instructed not to accept this card. Do not keep trying.

Customer-facing message: "Your card was declined. Please contact your bank for more information."

Important: Do not display the specific decline reason to the customer for any code in this group. Exposing the reason (especially SUSPECTED FRAUD or PICK UP CARD) can tip off fraudsters.

Merchant Setup — Contact SportsPay

These declines indicate a problem with your merchant account rather than the card. They come back as 0205 because the card network returns them the same way as a card decline, but the fix is on our side.

TEXTDescription
INVALID MERCHANTThe card network does not recognize the merchant. Contact [email protected].
INVALID TERM IDThe card network does not recognize the terminal. Contact [email protected].
SERV NOT ALLOWEDThe card brand is not supported on this merchant account (e.g., the merchant isn't enabled for Amex).
TRAN NOT ALLOWEDThis transaction type is restricted for this merchant.

Customer-facing message: None — retrying won't help. Flag to your support team to contact SportsPay.

Retrying a Declined Transaction

You can retry a declined payment with a new REF. Reusing the original REF will trigger 1035 DUPLICATE REFERENCE — the gateway's duplicate protection — and you'll get the original declined result back, not a new attempt.

  • Treat each retry as a new transaction with a fresh REF.
  • Use INV (invoice number) to group related attempts — the original decline and the retry will share the same INV in reporting for reconciliation.

CustomerPay Note

When a CustomerPay transaction declines, the USERFEE is not charged. AMT + USERFEE is submitted as a single charge — if the card declines, nothing moves.