Authorization Response CodesCredit Card Decline Codes
Credit Card Decline Codes — Definition & Guide
Credit card decline codes are short numeric or alphanumeric responses returned by the issuing bank when a card transaction cannot be authorized. They are standardized across the major US payment networks — Visa, Mastercard, American Express, and Discover all use overlapping code sets defined by the ISO 8583 message standard. Each code identifies a specific reason for the decline, and the codes fall into four operational categories that determine what the merchant should do next: issuer declines, fraud-suspect declines, network or velocity declines, and format or input errors.
When a customer’s card is declined, the issuing bank doesn’t just say “no” — it returns a specific reason code that tells the merchant exactly what went wrong. Code 05 means the bank refused without explanation. Code 51 means insufficient funds. Code 14 means the card number was entered incorrectly. The codes themselves are short, usually two characters, because they were designed in an era when transaction data traveled over slow connections and every byte cost time.
Knowing what each code means is the difference between a five-second customer recovery and a lost sale. The same “your card didn’t work” outcome could mean the customer needs to call their bank, retry in a few minutes, use a different card, or stop trying because the issuer flagged the transaction as potentially fraudulent. The right merchant response depends entirely on which code came back. According to the Visa Merchant Data Standards, the canonical code set is shared across the major US networks, with processor-specific extensions layered on top by companies like Stripe and Square.
The process follows a standard authorization request flow:
The codes themselves come from the issuing bank, not from the merchant’s processor. The processor passes the code through unchanged, which is why a decline message from Stripe and a decline message from Square will show the same underlying ISO code even if the surrounding text differs. The CFPB’s credit card consumer protections guidance provides additional context on the cardholder-facing rights surrounding declined transactions.
This reference covers the codes a US merchant encounters in roughly 95% of declined transactions, grouped by category. The category determines the right merchant action — a code 51 (issuer) and a code 91 (network) both look like “decline” to a cashier but call for completely different responses.
Issuer Declines
Bank refused. Customer action usually required before retry will work.
Fraud-Suspect Declines
Do not retry. Repeated attempts can increase chargeback exposure and trigger processor risk review.
Network & Velocity Declines
Usually temporary. Retry possible after a brief wait.
Format & Input Errors
Usually a keyed-entry typo or terminal configuration mismatch. Fix the data and retry.
Decline codes aggregate into operational patterns that affect a merchant in three ways:
- Customer recovery rate — knowing the difference between code 51 (try a different card) and code 91 (retry in a few minutes) lets staff handle the moment correctly. Recovery rates on declined transactions vary by 20-30 percentage points depending on whether the merchant interprets the code or treats every decline identically.
- Chargeback exposure — retrying transactions on fraud-suspect codes when the issuer has flagged the card as compromised can lead to chargeback liability that would not exist if the merchant had stopped on the first signal. Card networks examine decline history when adjudicating disputes.
- Processor relationship — sustained high decline rates, especially elevated fraud-suspect codes, trigger processor risk-review processes. A merchant whose decline mix shifts toward 41, 43, 57, and 59 over time will get attention from their processor’s risk team before it becomes a reserve-hold conversation.
Most merchants never look at their credit card decline codes at all. The ones who do find recoverable revenue and avoid risk-review escalations that would otherwise blindside them.
Code 05 (Do Not Honor) is the most common of all credit card decline codes. The issuing bank has refused to authorize the transaction without specifying a reason. The cause could be fraud suspicion, an account flag, available credit issues, or something else the bank chose not to disclose. The right next step is asking the customer to call their bank or try a different card.
The core codes derived from the ISO 8583 standard are largely consistent across networks. Visa and Mastercard share the closest alignment. American Express and Discover each maintain their own variations and add extension codes for network-specific scenarios. Processor-level decline reasons may include additional vendor-specific codes layered on top of the network response.
It depends entirely on the code category. Network and format codes (19, 91, 96, 14, 15) often succeed on retry. Issuer codes (05, 51, 54) usually require customer action before retry will work. Fraud-suspect codes (41, 43, 57, 59) should never be retried — repeated attempts on a flagged card can increase chargeback exposure and trigger processor risk review.
A decline happens at authorization — the transaction never completes and no funds move. A chargeback happens after a successful authorization when the cardholder disputes the charge through their bank. Decline codes appear in real time at the moment of the failed transaction; chargeback reason codes appear days or weeks later through the dispute process.
Most Merchants Never Look at Their Decline Codes. The Ones Who Do Recover 20-30% More Revenue.
Send us your last processing statement. We will pull your decline mix, identify the codes that are recoverable versus the ones costing you chargeback exposure, and walk you through what your processor’s risk team is seeing in your account.
Request a Free Statement ReviewNo obligation • No pressure • Response within one business day