Card Decline Codes Explained: Issuer Responses, AVS/CVV Mismatches, and Next Steps

Use this guide to identify whether the decline is issuer decision, data mismatch, or network issue, then apply the safest next step to complete the payment.

TL;DR

  • Issuer responses are category signals, not always a single diagnosis.
  • AVS/CVV mismatches commonly mean address/ZIP or security code mismatch.
  • Avoid repeated retries; try chip/tap or another payment method after one clean retry.
  • If decline follows the card across merchants, the issuer is the next stop.
ADVERTISEMENT

Advertisement

Ad slot: guide-banking-card-decline-codes-explained-issuer-responses-avs-cvv-mismatches-next-steps-1

Quick Navigation

Symptoms / When you see this

  • Declines like 05/51/54/57/91/96.
  • Online payments fail due to AVS/CVV mismatch.
  • Terminal shows “call issuer/do not honor/invalid transaction”.

Root causes (grouped)

  • Issuer decision (risk, limits, account state).
  • Data mismatch (AVS/CVV, expiration, card number).
  • Merchant/terminal rules (not permitted, invalid transaction).
  • Network/processor outages (timeouts, switch inoperative).

Step-by-step fixes (safe, prioritized)

  • Confirm amount, entry method, expiration, and billing address/ZIP.
  • Retry once after confirming connectivity and avoiding duplicate submission.
  • Try chip/tap rather than manual entry when possible.
  • If mismatch persists, use another payment method or have customer contact issuer.
  • If many cards fail, escalate as a processor/network incident.
ADVERTISEMENT

Advertisement

Ad slot: guide-banking-card-decline-codes-explained-issuer-responses-avs-cvv-mismatches-next-steps-2

What NOT to do

  • Do not run repeated retries; it can trigger issuer risk controls.
  • Do not request sensitive data beyond what is needed to process.
  • Do not attempt “overrides” without authorization.

If it persists (escalation checklist)

  • Capture: code, timestamp, amount, entry method, response fields.
  • Check if declines spike across cards (possible outage).
  • Use processor support when many transactions fail similarly.

Code directory within this guide

  • Issuer response mappings can vary slightly by processor. Use the code and the response text together.
Code Meaning Next step

Tip: If your exact code isn’t listed, use the closest hub link above and browse related prefixes or message patterns.

ADVERTISEMENT

Advertisement

Ad slot: guide-banking-card-decline-codes-explained-issuer-responses-avs-cvv-mismatches-next-steps-3

FAQ

Is 05 “Do not honor” always fraud?

No. It is a generic issuer decline category that can reflect risk, limits, or issuer rules.

What does AVS mismatch mean?

Billing address/ZIP did not match issuer records.

What does CVV mismatch mean?

Security code did not match issuer records.

Should merchants auto-retry?

Usually no. Retry once after correcting input, then change method or have customer contact issuer.

How do I tell if processor is down?

Many cards failing with network/timeouts suggests a processor outage, not issuer declines.

Why does card work elsewhere but not here?

Merchant category, risk scoring, and routing differences can change issuer decisions.

If decline follows the card everywhere, what next?

Issuer account state is likely; the issuer can clarify blocks and next steps.

Is a decline the same as a chargeback?

No. Declines happen at authorization; chargebacks happen after transactions settle.

References / Notes

  • Processor response mappings
  • Issuer guidance for cardholders
  • Merchant acquirer support resources
ErrorCodesIndex logo