Skip to main content

Decline Codes

Authorization decline reason codes and recommended handling.

Overview​

When a transaction is declined, the issuing bank returns a response code indicating the reason. Understanding these codes helps optimize authorization rates and customer experience.

Common Decline Codes​

Card Issues​

CodeDescriptionRetry?Customer Action
14Invalid card numberNoVerify card number
54Expired cardNoUse different card
41Lost cardNoContact issuer
43Stolen cardNoContact issuer
62Restricted cardNoContact issuer

Funds/Limit Issues​

CodeDescriptionRetry?Customer Action
51Insufficient fundsYes*Add funds, retry later
61Exceeds withdrawal limitYes*Try smaller amount, retry later
65Exceeds activity limitYes*Retry next day

*Retry only after customer action or time passage

Security/Fraud​

CodeDescriptionRetry?Customer Action
57Transaction not permittedMaybeContact issuer
59Suspected fraudNoContact issuer
63Security violationNoContact issuer
93Transaction violates lawNoCannot proceed

Technical Issues​

CodeDescriptionRetry?Customer Action
05Do not honor (generic)MaybeContact issuer, try again
12Invalid transactionNoCheck transaction details
91Issuer unavailableYesRetry shortly
96System malfunctionYesRetry shortly

Soft vs. Hard Declines​

Soft Declines (Retriable)​

Temporary issues that may resolve:

  • Network connectivity (91, 96)
  • Temporary limits (61, 65)
  • Authentication needed (some 05)

Strategy: Auto-retry with backoff

Hard Declines (Not Retriable)​

Permanent issues requiring customer action:

  • Invalid card (14, 54)
  • Lost/stolen (41, 43)
  • Fraud blocks (57, 59)

Strategy: Notify customer, request different payment method

Optimization Tips​

  1. Categorize declines – Track by type to identify patterns
  2. Smart retry logic – Auto-retry soft declines with delays
  3. Customer communication – Clear messaging by decline type
  4. Updater services – Keep card data current
  5. Network tokenization – Reduce credential-on-file declines

Next Steps​

Handling a decline?

  1. Check if soft or hard - Determines if you can retry
  2. Review common codes - Card, funds, security, technical
  3. Take customer action - Clear messaging by type

Improving auth rates?

  1. Implement smart retry logic - Auto-retry soft declines
  2. Use network tokenization - Reduce credential declines
  3. Follow auth optimization playbook - Full guide

Building decline handling?

  1. Categorize by type - Soft vs hard
  2. Map processor codes - Your processor → network codes
  3. Set up customer communication - Clear messaging