Skip to content

Why card payments get declined: payment authorization, decline codes, causes, and fixes

Why payment authorization fails: soft vs hard declines, what codes 05, 51 and 54 mean, and eight fixes that raise your card approval rate.

An issuer declines a card payment at payment authorization when the card is invalid, the funds or credit are not there, the transaction looks risky, or authentication fails. A soft decline is temporary and can often succeed on a retry. A hard decline is final for that card and should not be retried.

This guide explains what happens during authorization, what the most common decline codes mean, why issuers and merchants cause declines, and eight fixes that raise approval rates. It reflects card network and processor documentation as of October 2026. Codes and wording vary by processor and network, so check your own processor's reference before you act on a code.

Key takeaways

  • A decline is an answer from the card issuer. It travels back through the card network in seconds and carries a response code.
  • Soft declines can be retried later. Hard declines cannot. Insufficient funds is soft. An invalid card number is hard.
  • "Do not honor" (code 05) is a generic refusal. The issuer does not say why.
  • Stale card details are a preventable cause. Network tokens and account updater services replace expired and reissued cards. Visa reported a 3% increase in approval rates for tokenized payments in 2022.
  • Measure authorization rate by segment. Issuer, card type, and response code tell you where the problem is.

What is a card decline?

A card decline is a "no" from the cardholder's bank, called the issuer, in response to an authorization request. The merchant asks whether the card can pay a given amount. The issuer answers through the card network within seconds, with a two-character response code.

A decline is different from a payment that fails for technical reasons. If the request never reaches the issuer, for example because a connection times out, there is no issuer decision at all. Some processors also block payments with their own risk rules before the issuer sees them. All three look the same to the shopper, but each has a different fix.

For the full path a payment takes after approval, see how card payments work.

What happens during payment authorization?

Payment authorization is the step where the issuer checks the card and reserves the amount. The issuer checks that the card is valid, that funds or credit are available, and whether the payment looks like fraud. If every check passes, it approves and places a hold.

The hold is not a transfer of money. As one payments reference puts it, "An approval is a hold: it reduces the cardholder's available credit and moves no money" (Syntaqx). Money moves later, when the transaction clears and settles.

Holds expire. Visa's 2024 merchant guidance on estimated authorizations lists 5 days for card-present transactions and 10 days for cardholder-initiated card-absent transactions, with longer windows for lodging, vehicle rental, and cruise lines. The guide is listed in Visa's Merchant Resource Library. Capture inside the window, or authorize again.

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

A soft decline is a temporary refusal. The card is real and usable, but this attempt did not pass, and a later attempt can succeed. A hard decline is a permanent refusal for that card or that type of purchase. Sending the same request again will fail again.

The table uses the codes listed in Stripe's network decline codes reference (2026). Most networks share these meanings, but a few assign a different meaning to the same number.

Decline typeTypical codesRetry?Fix
Soft: funds or limit51 insufficient fundsYes, laterRetry on a spaced schedule, or ask for another payment method
Soft: issuer or network unavailable91 issuer or switch inoperativeYes, after a short waitRetry once the issuer is reachable
Generic refusal05 do not honorSometimes, with careCheck your data and authentication first; ask the customer to call the bank if it repeats
Hard: wrong card details14 invalid card numberNoAsk the customer to re-enter the card
Hard: expired card54 expired cardNot with the same detailsGet new details from an account updater, a network token, or the customer
Hard: card not allowed for this purchase57 transaction not permitted to cardholderNoAsk for a different card or payment method
Authentication failedVaries by processorNot without a new authenticationSend the customer through 3-D Secure again

What do the most common decline codes mean?

Each code is the issuer's short answer to the authorization request. These six appear in most processor references.

  • 05, do not honor. A generic refusal. The issuer gives no reason, which often means a risk rule or an account restriction. Only the cardholder's bank can explain it.
  • 51, insufficient funds. The account balance or the available credit does not cover the amount. Pending holds count against the available amount.
  • 54, expired card. The expiry date has passed, or the date sent does not match the issuer's records. Reissued cards often trigger this on stored credentials.
  • 14, invalid card number. The number does not exist at the issuer. A typing error is the usual cause.
  • 57, transaction not permitted to cardholder. The card exists but is not allowed to make this kind of purchase, for example online or international payments on a restricted card.
  • 91, issuer or switch inoperative. The issuer or the network link could not be reached. Nothing is wrong with the card.

Your processor may map these network codes to its own names and add codes of its own. Build your retry logic on your processor's documented codes, not on a generic list.

Why do issuers decline card payments?

Issuer declines fall into four groups. Knowing the group tells you who can fix the problem.

  1. Card status. The card is expired, closed, reported lost or stolen, or not yet activated.
  2. Funds and limits. The balance, the credit line, or a daily spending limit does not cover the amount.
  3. Risk. The issuer's fraud model flags the payment. Unusual merchants, countries, amounts, and bursts of attempts all raise the score.
  4. Authentication. The issuer wanted the cardholder to authenticate and that did not happen, or the cardholder failed the check. See 3D Secure 2 explained.

This is why a customer with money in the account can still be declined. The issuer may have blocked the merchant type, hit a daily limit, or treated a first purchase abroad as suspicious. Cross-border purchases see this more often, as cross-border checkout abandonment explains.

Which declines start on the merchant side?

Many declines trace back to what the merchant sent, not to the cardholder's account. These causes are within your control.

  • Missing or wrong data. A missing billing postal code or security code, or an expiry date in the wrong format, gives the issuer less to verify.
  • Wrong transaction flags. A recurring charge sent without the stored credential indicators looks like a customer payment with no customer present. Recurring card payments covers the flags.
  • Stale stored cards. Cards expire and get reissued. A stored number that was valid last month can fail this month.
  • Late captures. Capturing after the authorization hold has expired can fail.
  • Retry storms. Repeating a declined request several times in a row looks like an attack on the card, and issuers respond by declining more.
  • Processor risk rules. Your gateway or processor may reject a payment before it reaches the issuer. Check its logs before you blame the bank.

How do you fix card declines?

Work through these eight fixes in order. The first four deal with retries and stored cards, where the same decline tends to repeat.

  1. Read the response code before you do anything. Split soft declines from hard declines and route each to a different path.
  2. Retry soft declines on a schedule. Space retries over hours or days, for example after a typical payday, and stay inside your network's and processor's retry limits.
  3. Use network tokens for stored cards. A network token is updated by the card network when the card behind it changes. Visa's analysis across more than 8,600 issuers and 800,000 merchants found a 3% increase in approval rates and a 28% reduction in fraud rates for tokenized payments (Visa, August 2022). Card tokenization explained covers how tokens work.
  4. Turn on account updater. Visa Account Updater and Mastercard's Automatic Billing Updater supply new card numbers and expiry dates for stored credentials.
  5. Send complete and consistent data. Include the billing address and security code on customer-initiated payments, and flag merchant-initiated payments correctly.
  6. Authenticate when the issuer expects it. Run 3-D Secure on payments where authentication is required or the risk is high, and send the customer back through it after a failed check.
  7. Capture inside the authorization window. If fulfillment takes longer than the hold lasts, authorize again before you capture.
  8. Offer another way to pay. A second card, a bank transfer, or a local payment method recovers sales that no retry will.

How do you measure and improve your authorization rate?

Authorization rate is approved authorizations divided by attempted authorizations. It is the main health metric for card acceptance, and one blended number hides most of what you need to see.

Break the rate down by:

  • issuer and issuing country
  • card type, such as credit, debit, or prepaid
  • customer-initiated versus merchant-initiated payments
  • tokenized versus raw card numbers
  • first attempts versus retries
  • response code

Then look for change, not for a universal target. A drop at one issuer points to a rule change at that bank. A rise in code 54 points to stale stored cards. A rise in code 05 on recurring charges often points to missing flags or too many retries. Fix the largest segment first and measure again after a week.

What should you tell the customer?

Tell the customer what to do next, not what the code said. Most shoppers cannot act on "do not honor," and showing fraud-related reasons helps people who are testing stolen cards.

SituationWhat to show
Wrong details (14, 54)Ask the customer to check the card number and expiry date and try again
Funds or limits (51)Suggest another card or payment method, without mentioning the balance
Generic or risk decline (05, 57)Say the bank did not approve the payment and suggest calling the bank or using another card
Issuer unavailable (91)Say the bank could not be reached and invite a retry in a few minutes
Failed authenticationAsk the customer to complete the bank's verification step again

Keep the cart intact and make the second attempt one click away. For subscriptions, send a secure link to update the card instead of asking for card details by email.

Sources

What to do next

Pull last month's declines, group them by response code, and apply the fix that matches the largest group. Then read how card payments work for the stages after approval and recurring card payments for stored cards. BlindPay does not issue cards. It accepts card payments as one payin method, where each payin allows up to three declined attempts, per the card payins docs.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.