Card Decline Code Lookup

Look up any card decline code — Stripe codes, numeric issuer responses (05, 51…), AVS results, and Visa/Mastercard chargeback reasons — with who declined it, whether it is retryable, and what to do next.

133 codes

Stripe decline codes

  • authentication_requiredThe transaction requires 3D Secure authentication.
    Fix, then retryCard issuer

    Run the 3DS flow and retry. Stripe front ends usually trigger this automatically; off-session payments may need the customer brought back on-session.

  • approve_with_idThe payment could not be authorized.
    Retry OKCard issuer

    Retry once. If it fails again, the customer must contact their issuer.

  • call_issuerDeclined for an unknown reason.
    Do not retryCard issuer

    The customer must contact their card issuer.

  • card_not_supportedThe card does not support this type of purchase.
    Do not retryCard issuer

    Customer should use a different card or confirm purchase type support with the issuer.

  • card_velocity_exceededBalance, credit limit, or transaction-count limit exceeded.
    Do not retryCard issuer

    Customer must contact their issuer or use another card.

    Reproduce in test mode: 4000 0000 0000 6975

  • currency_not_supportedThe card does not support the specified currency.
    Do not retryCard issuer

    Use another card, or charge in a supported currency.

  • do_not_honorThe issuer declined with no reason given — the most common opaque decline.
    Do not retryCard issuer

    Do not hammer retries. The customer must contact their issuer; a different card or payment method usually resolves it faster.

  • duplicate_transactionAn identical amount + card transaction was submitted moments ago.
    InfoStripe

    Check whether the earlier payment already succeeded before retrying.

  • expired_cardThe card has expired.
    Fix, then retryCard issuer

    Collect an updated card. If you use saved cards, consider a card-updater flow before renewals.

    Reproduce in test mode: 4000 0000 0000 0069

  • fraudulentStripe suspects the payment is fraudulent and blocked it.
    Do not retryStripe

    Show the customer a generic decline message. Never surface fraud suspicion to the payer.

  • generic_declineDeclined with no specific reason, or blocked by Radar/Adaptive Acceptance.
    Do not retryCard issuer

    Customer contacts their issuer or pays another way. Watch your rate of these — a spike often means a risk or routing problem.

    Reproduce in test mode: 4000 0000 0000 0002

  • incorrect_addressThe billing address entered is wrong.
    Fix, then retryCard issuer

    Ask the customer to re-enter the correct billing address and retry.

  • incorrect_cvcThe CVC is wrong.
    Fix, then retryCard issuer

    Ask the customer to re-enter the CVC and retry.

    Reproduce in test mode: 4000 0000 0000 0127

  • incorrect_numberThe card number is wrong (fails validation).
    Fix, then retryStripe

    Ask the customer to re-enter the number.

    Reproduce in test mode: 4242 4242 4242 4241

  • incorrect_pinWrong PIN (card-reader payments only).
    Fix, then retryCard issuer

    Customer retries with the correct PIN.

  • incorrect_zipThe billing postal code is wrong.
    Fix, then retryCard issuer

    Ask the customer to re-enter the correct postal code and retry.

  • insufficient_fundsNot enough balance or available credit.
    Retry OKCard issuer

    A classic soft decline — a later retry (e.g. after payday) or another payment method often succeeds. Smart retry schedules recover a meaningful share of these.

    Reproduce in test mode: 4000 0000 0000 9995

  • invalid_accountThe card or its underlying account is invalid.
    Do not retryCard issuer

    Customer must contact the issuer or use another card.

  • invalid_amountThe amount is invalid or above what the card allows.
    Fix, then retryCard issuer

    If the amount is correct, the customer should check card limits with their issuer.

  • invalid_cvcThe CVC is invalid.
    Fix, then retryCard issuer

    Ask the customer to re-enter the CVC.

  • invalid_expiry_monthThe expiry month is invalid.
    Fix, then retryStripe

    Ask the customer to correct the expiry date.

  • invalid_expiry_yearThe expiry year is invalid.
    Fix, then retryStripe

    Ask the customer to correct the expiry date.

  • invalid_numberThe card number is invalid.
    Fix, then retryStripe

    Ask the customer to re-enter the number.

  • invalid_pinThe PIN is invalid.
    Fix, then retryCard issuer

    Customer retries with the correct PIN.

  • issuer_not_availableThe issuer could not be reached to authorize.
    Retry OKCard issuer

    Retry — this is usually transient issuer downtime. Persistent failures: customer contacts issuer.

  • lost_cardThe card is reported lost.
    Do not retryCard issuer

    Show a generic decline to the payer — never reveal the card is flagged lost.

    Reproduce in test mode: 4000 0000 0000 9987

  • merchant_blacklistThe payment matches an entry on your own Stripe block list.
    Do not retryStripe

    Present as a generic decline. Review your block list if this is unexpected.

  • new_account_information_availableThe card/account has new information (often reissued cards).
    Fix, then retryCard issuer

    Ask the customer for updated card details, or use an account-updater service.

  • no_action_takenDeclined for an unknown reason.
    Do not retryCard issuer

    Customer contacts their issuer.

  • not_permittedThe payment is not permitted for this card.
    Do not retryCard issuer

    Customer contacts their issuer or uses another card.

  • offline_pin_requiredCard requires an inserted-card PIN entry.
    Fix, then retryCard issuer

    Customer retries by inserting the card and entering a PIN.

  • online_or_offline_pin_requiredThe card requires PIN entry.
    Fix, then retryCard issuer

    Prompt for Online PIN if the reader supports it; otherwise insert card and enter PIN.

  • pickup_cardThe issuer wants the card taken out of circulation — often lost/stolen.
    Do not retryCard issuer

    Never retry. Customer must contact their issuer.

  • pin_try_exceededToo many wrong PIN attempts.
    Do not retryCard issuer

    Customer must use another card or payment method.

  • processing_errorA transient error occurred while processing.
    Retry OKProcessing

    Retry immediately once, then with backoff. This is a textbook candidate for failover to a second processor.

    Reproduce in test mode: 4000 0000 0000 0119

  • reenter_transactionThe issuer could not process it this time.
    Retry OKCard issuer

    Retry; if it persists, the customer contacts the issuer.

  • restricted_cardThe card cannot be used for this payment — possibly flagged lost/stolen.
    Do not retryCard issuer

    Customer contacts their issuer. Show a generic message.

  • revocation_of_all_authorizationsThe cardholder revoked all authorizations (common for subscriptions).
    Do not retryCard issuer

    Stop retrying this card. Reach out to the customer for a new payment method.

  • revocation_of_authorizationThe cardholder revoked this specific authorization.
    Do not retryCard issuer

    Stop charges under this authorization; get fresh consent or a new method.

  • security_violationDeclined for an unspecified security reason.
    Do not retryCard issuer

    Customer contacts their issuer.

  • service_not_allowedDeclined for an unknown reason.
    Do not retryCard issuer

    Customer contacts their issuer.

  • stolen_cardThe card is reported stolen.
    Do not retryCard issuer

    Show a generic decline — never reveal the flag to the payer.

    Reproduce in test mode: 4000 0000 0000 9979

  • stop_payment_orderThe cardholder placed a stop on this payment.
    Do not retryCard issuer

    Do not retry. Contact the customer directly.

  • testmode_declineA test card number was used with live-mode keys.
    Fix, then retryStripe

    Use a real card in live mode, or switch to test-mode API keys while developing.

  • transaction_not_allowedDeclined for an unknown reason.
    Do not retryCard issuer

    Customer contacts their issuer or pays another way.

  • withdrawal_count_limit_exceededBalance or credit limit exceeded.
    Retry OKCard issuer

    Retry later or collect an alternative payment method.

  • mobile_device_authentication_requiredThe transaction requires device authentication.
    Fix, then retryCard issuer

    Customer re-taps or re-authenticates with their mobile device.

Issuer response codes (numeric)

  • 00Approved.
    InfoCard issuer

    Nothing to do — the transaction succeeded.

  • 01Refer to issuer.
    Do not retryCard issuer

    Customer must call their issuer; the issuer wants to speak before approving.

  • 02Refer to issuer, special condition.
    Do not retryCard issuer

    Same as 01 — the customer contacts the issuer.

  • 03Invalid merchant number.
    Do not retryAcquirer

    A configuration problem on your side — check your merchant account setup with your acquirer.

  • 04Pick up card — the issuer wants it withheld.
    Do not retryCard issuer

    Never retry. Customer must contact the issuer.

  • 05Do not honor — the generic catch-all issuer decline.
    Do not retryCard issuer

    The most common decline code in card processing. Ask for another payment method; the customer can ask their bank why.

  • 06General error.
    Retry OKCard issuer

    Retry once; if persistent, treat as a hard decline.

  • 07Pick up card, special condition (possible fraud).
    Do not retryCard issuer

    Never retry. Treat as a fraud signal.

  • 12Invalid transaction for this card or terminal.
    Fix, then retryCard issuer

    Verify transaction type and details; use another card if it persists.

  • 13Invalid amount.
    Fix, then retryCard issuer

    Check the amount format and value, then retry.

  • 14Invalid card number.
    Fix, then retryCard issuer

    Re-enter the card number.

  • 15No such issuer — the BIN does not exist.
    Do not retryNetwork

    The number is wrong or fabricated. Ask for a valid card.

  • 19Re-enter transaction.
    Retry OKProcessing

    Retry the transaction.

  • 25Unable to locate record — account not found.
    Do not retryCard issuer

    Verify card details; use another card.

  • 28File temporarily unavailable at the issuer.
    Retry OKCard issuer

    Retry after a short delay.

  • 30Format error in the transaction message.
    Fix, then retryProcessing

    Usually an integration/gateway issue — check field formats or contact your processor.

  • 41Lost card.
    Do not retryCard issuer

    Never retry. Present a generic decline to the payer.

  • 43Stolen card.
    Do not retryCard issuer

    Never retry. Present a generic decline to the payer.

  • 46Closed account.
    Do not retryCard issuer

    Collect a different payment method.

  • 51Insufficient funds.
    Retry OKCard issuer

    The classic soft decline — retry later or offer another method.

  • 54Expired card.
    Fix, then retryCard issuer

    Collect updated card details.

  • 55Incorrect PIN.
    Fix, then retryCard issuer

    Customer re-enters the PIN.

  • 57Transaction not permitted to cardholder.
    Do not retryCard issuer

    The card cannot make this kind of purchase — use another card.

  • 58Transaction not permitted on terminal.
    Do not retryAcquirer

    Your merchant account is not configured for this transaction type — contact your acquirer.

  • 59Suspected fraud.
    Do not retryCard issuer

    Do not retry. Present a generic decline.

  • 61Exceeds withdrawal amount limit.
    Retry OKCard issuer

    Retry later, split the amount, or use another method.

  • 62Restricted card — often region or sanction restrictions.
    Do not retryCard issuer

    Use another card.

  • 63Security violation.
    Do not retryCard issuer

    Customer contacts their issuer.

  • 65Exceeds withdrawal count limit.
    Retry OKCard issuer

    Retry another day or use another method.

  • 75PIN tries exceeded.
    Do not retryCard issuer

    The card is PIN-locked — customer contacts their issuer.

  • 78No account / card not activated.
    Fix, then retryCard issuer

    New cards often need activation — ask the customer to activate, then retry.

  • 82CVV/CAM verification failed.
    Fix, then retryCard issuer

    Re-enter the security code.

  • 85No reason to decline (used for verification requests).
    InfoCard issuer

    Nothing — this is a positive response to an account verification.

  • 91Issuer or switch unavailable.
    Retry OKCard issuer

    Transient — retry with backoff, or route to another processor if you can.

  • 93Transaction violates law — cannot complete.
    Do not retryCard issuer

    Do not retry.

  • 96System malfunction.
    Retry OKNetwork

    Transient network/processor issue — retry with backoff.

AVS codes

  • YAddress and 5-digit ZIP both match.
    InfoCard issuer

    Best possible AVS result.

  • AStreet address matches; ZIP does not.
    InfoCard issuer

    Partial match — decide via your fraud rules.

  • Z5-digit ZIP matches; street address does not.
    InfoCard issuer

    Partial match — common with typos; judge with other signals.

  • NNeither address nor ZIP matches.
    InfoCard issuer

    Strong mismatch signal — many merchants decline or review these.

  • UAddress information unavailable from the issuer.
    InfoCard issuer

    Common for non-US issuers — do not treat as a mismatch.

  • RRetry — issuer AVS system unavailable.
    Retry OKCard issuer

    Retry the verification later.

  • SAVS not supported by the issuer.
    InfoCard issuer

    Treat as no-data, not as a mismatch.

  • GGlobal card — issuer does not participate in AVS.
    InfoCard issuer

    Typical for international cards; rely on other checks (CVC, 3DS).

  • W9-digit ZIP matches; address does not.
    InfoCard issuer

    Partial match.

  • XAddress and 9-digit ZIP both match.
    InfoCard issuer

    Exact match.

  • BAddress matches; ZIP not verified (international).
    InfoCard issuer

    Partial international match.

  • CAddress and ZIP not verified (international).
    InfoCard issuer

    No-data result for international cards.

  • DAddress and ZIP match (international).
    InfoCard issuer

    Full international match.

  • IAddress not verified (international).
    InfoCard issuer

    Treat as no-data.

  • MAddress and ZIP match (international).
    InfoCard issuer

    Full international match.

  • PZIP matches; address not verified (international).
    InfoCard issuer

    Partial international match.

Visa chargeback reasons

  • 10.1EMV liability shift — counterfeit fraud.
    InfoVisa (fraud)

    Card-present issue: usually means a chip card was swiped. Hard to win without chip data.

  • 10.2EMV liability shift — non-counterfeit fraud.
    InfoVisa (fraud)

    Lost/stolen card used at a non-EMV terminal. Upgrade terminals to shift liability back.

  • 10.3Fraud — card-present environment.
    InfoVisa (fraud)

    Provide proof of card presence and imprint/chip data.

  • 10.4Fraud — card-absent (online) environment. The most common ecommerce fraud chargeback.
    InfoVisa (fraud)

    Respond with AVS/CVC matches, 3DS evidence, delivery proof, and customer history. Prevent with 3DS — it shifts liability to the issuer.

  • 10.5Visa Fraud Monitoring Program chargeback.
    InfoVisa (fraud)

    Issued when Visa flags the transaction under VFMP — dispute rights are limited. Fix the underlying fraud problem.

  • 11.1Card recovery bulletin — authorization issue.
    InfoVisa (authorization)

    Rare today. Ensure every transaction gets a valid authorization.

  • 11.2Declined authorization — transaction forced after a decline.
    InfoVisa (authorization)

    Never force-capture declined auths. Nearly indefensible.

  • 11.3No authorization obtained.
    InfoVisa (authorization)

    Always authorize before capture; respond with auth records if you have them.

  • 12.1Late presentment — captured too long after authorization.
    InfoVisa (processing)

    Capture within the allowed window (generally a few days). Automate capture timing.

  • 12.2Incorrect transaction code.
    InfoVisa (processing)

    Processing error — verify with your processor and provide correction evidence.

  • 12.3Incorrect currency.
    InfoVisa (processing)

    Charge in the currency presented at checkout; document what was shown.

  • 12.4Incorrect account number.
    InfoVisa (processing)

    Provide proof the correct account was charged.

  • 12.5Incorrect amount.
    InfoVisa (processing)

    Provide the receipt/order record showing the agreed amount.

  • 12.6Duplicate processing or paid by other means.
    InfoVisa (processing)

    Show the transactions are distinct, or refund the true duplicate quickly.

  • 12.7Invalid data in the transaction.
    InfoVisa (processing)

    Correct the data issue with your processor.

  • 13.1Merchandise/services not received.
    InfoVisa (dispute)

    Respond with delivery confirmation or proof of service. Prevent with tracked shipping and clear delivery timelines.

  • 13.2Cancelled recurring transaction.
    InfoVisa (dispute)

    Honor cancellations immediately and keep logs — respond with the cancellation/usage record.

  • 13.3Not as described or defective.
    InfoVisa (dispute)

    Provide product description, communications, and return-policy evidence.

  • 13.4Counterfeit merchandise claim.
    InfoVisa (dispute)

    Provide authenticity documentation.

  • 13.5Misrepresentation of the purchase.
    InfoVisa (dispute)

    Show your product page/terms as presented at purchase time.

  • 13.6Credit not processed.
    InfoVisa (dispute)

    If a refund was promised, prove it was issued — or issue it now.

  • 13.7Cancelled merchandise/services.
    InfoVisa (dispute)

    Provide your cancellation policy as shown to the customer and any usage evidence.

  • 13.8Original credit transaction not accepted.
    InfoVisa (dispute)

    Rare — work with your processor.

  • 13.9Non-receipt of cash at ATM.
    InfoVisa (dispute)

    ATM-only code; not relevant to merchants.

Mastercard chargeback reasons

  • 4837No cardholder authorization — the classic fraud chargeback.
    InfoMastercard (fraud)

    Respond with AVS/CVC/3DS evidence, IP and device data, and delivery proof.

  • 4840Fraudulent processing of transactions.
    InfoMastercard (fraud)

    Multiple charges after a legitimate one — show each transaction was authorized.

  • 4849Questionable merchant activity.
    InfoMastercard (fraud)

    Tied to Mastercard fraud programs — address the underlying flag with your acquirer.

  • 4853Cardholder dispute — umbrella code for goods/services issues (not received, not as described, cancelled recurring, refund not processed).
    InfoMastercard (dispute)

    Mastercard consolidated most consumer disputes here. Respond with evidence matching the specific claim in the dispute message.

  • 4863Cardholder does not recognize the transaction.
    InfoMastercard (fraud)

    Use a clear billing descriptor. Respond with order details linking the cardholder to the purchase.

  • 4870Chip liability shift — counterfeit at non-EMV terminal.
    InfoMastercard (fraud)

    Card-present: upgrade to EMV terminals.

  • 4871Chip/PIN liability shift — lost/stolen card at non-PIN terminal.
    InfoMastercard (fraud)

    Card-present: support chip-and-PIN.

  • 4834Point-of-interaction error — duplicates, wrong amounts, late presentment.
    InfoMastercard (processing)

    Provide processing records; refund genuine errors quickly.

  • 4807Warning bulletin file — authorization issue.
    InfoMastercard (authorization)

    Legacy authorization code; ensure valid auths on every transaction.

  • 4808Authorization-related chargeback — missing/declined authorization.
    InfoMastercard (authorization)

    Never capture without a valid authorization; respond with auth logs.

Soft declines (Retry OK) are worth retrying — smart retry timing and routing to a second processor recover a real share of them. Hard declines (Do not retry) will not succeed and retrying them damages your issuer reputation.

Stripe codes verified against docs.stripe.com/declines/codes: 2026-08-02. Numeric, AVS, and chargeback codes follow the published ISO 8583 / Visa / Mastercard standards.

Frequently asked questions

What does decline code 05 "do not honor" mean?

It is the issuer’s catch-all refusal: the cardholder’s bank declined without giving a reason. It maps to Stripe’s do_not_honor. Repeated retries rarely help — the fastest resolution is a different payment method, or the customer calling their bank.

What is the difference between a soft decline and a hard decline?

A soft decline is temporary — insufficient funds (51), issuer unavailable (91), processing errors — and a well-timed retry can succeed. A hard decline is final — stolen card (43), pickup card (04), do not honor (05) — and retrying it hurts your standing with the issuer. This lookup labels every code as retryable, fix-then-retry, or do-not-retry.

Who actually declines a payment — Stripe, the network, or the bank?

Usually the issuing bank: roughly nine in ten declines are issuer decisions, returned as a response code your gateway translates. The rest come from the gateway or fraud tooling (like Radar) blocking before the issuer is ever asked, or from network/processing errors in between.

How can I reduce card declines?

Send complete data (CVC, AVS, and where relevant Level 2/3 fields), use 3D Secure when the issuer requires authentication, retry soft declines on a smart schedule, keep saved cards fresh with an account updater, and at volume route transactions to the acquirer most likely to get an approval — local acquiring measurably improves auth rates on international cards.

What is a chargeback reason code?

When a cardholder disputes a settled payment, the issuer files it under a network-defined reason code — for example Visa 10.4 (card-absent fraud) or Mastercard 4853 (cardholder dispute). The code determines what evidence can win the dispute, so identifying it correctly is the first step of any response.

Embed this calculator

Free to embed on your site. The attribution link back to this page is required — please keep it visible. 

<iframe
  src="https://stopbyte.com/embed/card-decline-codes"
  title="Card Decline Code Lookup by StopByte"
  width="100%" height="640" style="border:1px solid #d9dde3;border-radius:12px"
  allow="clipboard-write" loading="lazy"></iframe>
<p>Calculator by <a href="https://stopbyte.com/tools/card-decline-codes">StopByte Card Decline Code Lookup</a></p>