Skip to content

How to improve card authorization rates: why payments decline and what fixes them

What authorization rate means, why issuers decline cards, soft vs hard declines, retry rules, 3-D Secure, network tokens and local acquiring (Nov 2026).

Authorization rate is the share of card payment attempts that issuers approve. You improve it by cleaning transaction data, using network tokens and card updates, tuning retries and 3-D Secure, using local acquiring for international cards, and separating soft declines, which you can retry, from hard declines, which you must not.

This guide covers how to measure the rate, why issuers decline, and the fixes that follow, as of November 2026. BlindPay publishes this guide. There is no benchmark rate here on purpose: no named, dated source supports a number that fits every merchant.

Key takeaways

  • Measure the rate two ways, per attempt and per order, because retries change the denominator.
  • Visa groups decline codes into categories: Category 1 declines should never be retried, while temporary declines such as insufficient funds can be retried up to 20 times in 30 days in the US, according to TabaPay's guidance dated 22 October 2026.
  • Mastercard's merchant advice codes tell you whether to retry: code 03 means do not try again, and codes 24 to 30 give a wait of 1 hour to 10 days for insufficient funds.
  • Issuers decline most often with a generic code, so the decline code alone rarely explains the loss. Segment by issuer, country, brand and reason.
  • Cards issued abroad decline more often on average, but no current independent benchmark exists, so test local acquiring before you commit.

What is an authorization rate and how is it measured?

The authorization rate is approved authorization attempts divided by total authorization attempts in a period. An authorization is the request your acquirer sends to the cardholder's issuer, the bank that issued the card, asking whether the payment can go ahead.

The denominator is where teams disagree, so define it before you trend it. A retry is a second attempt on the same order, so counting every attempt can make your rate look worse than what customers experience, and counting orders can hide friction.

MetricFormulaDenominator
Attempt-level authorization rateApproved attempts / all attemptsEvery authorization request, including retries
Order-level success rateOrders with at least one approval / unique orders attemptedOne count per order
Issuer-only approval rateApproved / (approved + issuer declines)Excludes your own fraud blocks and failed 3-D Secure
Recovery rateOrders approved after an earlier decline / orders with an earlier declineOnly orders that were declined at least once

Here is a worked example. It is illustrative and every input is stated: in a month, a merchant sends 10,000 authorization attempts for 9,200 unique orders, and 7,900 orders end approved, one approval per order. The attempt-level rate is 7,900 / 10,000 = 79.0%. The order-level rate is 7,900 / 9,200 = 85.9%. The gap comes from the 800 retries, so quote which one you mean when you compare yourself with a provider's figure.

Stripe's documentation suggests using card fingerprints instead of charge IDs when you analyze declines, so repeat attempts on the same card do not inflate the numbers.

Why do issuers decline payments?

Issuers decline because their automated systems judge the payment as unaffordable, risky, invalid or not allowed. The issuer sees signals such as spending habits, account balance and card data, including expiry date, address and security code, according to Stripe's documentation.

Most declines reach you as a generic code. Stripe's documentation says card issuers categorize most declines as generic, and that for privacy and security reasons issuers discuss the specifics only with their cardholders. Network response codes still help, and the table below lists common Visa codes. The meanings come from Stripe's network decline code reference, and the categories come from TabaPay's guidance on Visa decline categories, updated 22 October 2026.

Visa codeMeaningTypical causeHandlingVisa category
51Insufficient fundsBalance or credit limitSoft: retry later or ask for another card2
61Exceeds approval amount limitAmount above the card's limitSoft: retry later or a smaller amount2
65Exceeds withdrawal frequency limitToo many uses in a periodSoft: retry later2
59Suspected fraudIssuer risk modelSoft but sensitive: ask for authentication or another card2
54Expired card or missing expiry dateOld card on fileFix data: get new details or a network token update3
82Negative CAM, dCVV, iCVV or CVV resultsSecurity code check failedFix data: ask for the correct code3
N7Decline for CVV2 failureWrong security codeFix data: ask for the correct code3
14Invalid account numberTypo or closed numberHard: do not retry; get a new card1
41Lost cardReported lostHard: do not retry1
43Stolen cardReported stolenHard: do not retry1
46Account closedClosed accountHard: do not retry1
57Transaction not permitted to cardholderCard does not allow this useHard: do not retry1
05Do not honorIssuer declines without a reasonTreat as generic: retry only within rules4, generic
91Issuer or switch inoperativeIssuer system downSoft: retry soon4, generic
1AAdditional customer authentication requiredNeeds 3-D SecureAuthenticate, then resubmitn/a

Categories 2 and 3 follow TabaPay's list of codes, and codes outside Categories 1 to 3 default to Category 4. The soft or hard label in the Handling column is a working convention built on those categories, not a network term. Always check the code with your acquirer's documentation, because the same code can be handled differently by brand and processor.

What is the difference between soft and hard declines?

A soft decline is temporary: the same card may be approved on a later attempt or after a fix. A hard decline is permanent: the issuer will not approve this card for this payment, and retrying does nothing but risk fees.

Visa makes this concrete. According to TabaPay's guidance, Category 1 declines mean the issuer will never re-approve, and clients must not reattempt them. Category 2 covers temporary declines such as insufficient funds. Category 3 covers data quality issues, such as an expired card or wrong CVV2, where you should revalidate the data before reattempting. Category 4 is the catch-all.

Stripe's documentation uses simpler advice codes: do_not_try_again, try_again_later and confirm_card_data. Mastercard's equivalent is the merchant advice code, which Stripe says Mastercard calls MAC. The table summarizes how to route each one.

SignalWhat it meansAction
Visa Category 1, or MAC 03Do not try againStop; ask for another payment method
Visa Category 2, or MAC 02Temporary, try again laterRetry with spacing
Visa Category 3, or MAC 01Data or account info needs updatingFix data, then retry
confirm_card_dataProvided details look wrongAsk the customer to check them
Generic declineNo reason givenRetry carefully, or offer another method

How do network tokens and account updater help?

They keep the card details you store current, so payments do not fail because a card expired or was replaced. A network token is a placeholder for the card number issued by the card scheme, and its underlying card details are updated by the scheme when the card changes.

According to Checkout.com's documentation, network tokens are provisioned for Visa and Mastercard through VTS and MDES, the schemes' token services. The page says they reduce declines due to expired or replaced cards, and that the scheme automatically updates the underlying card details with no action by the customer. The page gives no coverage figures, so ask your provider what share of your cards it can tokenize and how often updates arrive.

An account updater service does a similar job without tokens: it checks stored card details against issuer updates before you bill. Either way, the fix helps most for recurring billing and saved cards, and least for first-time guest checkouts. Compare options with the card payment authorization, clearing and settlement guide, which explains where the authorization sits in the flow.

How should I design retries?

Retry only soft declines, space the attempts, cap the number and stop on hard signals. Retries also cost you: networks limit reattempts, and extra attempts can raise declines for legitimate charges.

Here are the limits that apply. They are sourced and dated, but they change, so confirm them with your acquirer.

  1. Stripe's documentation says card networks limit how many times you can reattempt a charge, recommends at most eight retries where retries are allowed, and warns that issuers may see more retries as potential fraud.
  2. For Visa, TabaPay's guidance says reattempts in Categories 2 to 4 are permitted up to 20 times in 30 days, that any reattempt after a Category 1 decline is assessed a fee, and that the fee applies from the 21st reattempt in 30 days. It limits this to US transactions where both the merchant and the card are in the US, and lists no dollar amounts. Some older guides give 15 instead of 20, so check the figure for your region.
  3. For Mastercard, TabaPay's guidance says not to retry a transaction when the same card, merchant and amount was declined with MAC 03 in the past 30 days, and gives retry-after times for insufficient-funds declines: MAC 24 is 1 hour, 25 is 24 hours, 26 is 2 days, 27 is 4 days, 28 is 6 days, 29 is 8 days and 30 is 10 days. It also says excessive authorizations are assessed after 35 issuer declines on the same account within 30 days.

A practical design for recurring billing is to retry insufficient-funds declines on the schedule the issuer's advice code gives, stop on any hard decline, and send the customer a link to update the card after the first soft decline. For one-time checkout, let the customer fix the data immediately and offer another method, rather than retrying silently.

When does 3D Secure help or hurt?

3-D Secure (3DS) is an authentication step, such as a one-time code or biometric check, that asks the cardholder to prove it is them. It helps when issuers would otherwise decline for suspected fraud and where regulation requires it. It hurts when the challenge makes customers abandon.

Stripe's documentation says 3DS can lower decline rates in countries that support it. It also says strong customer authentication rules in the EEA, the UK, India, Japan and Australia may require 3DS for card payments, while it is optional elsewhere. For fraud-related disputes, a successful 3DS authentication can shift liability for some fraudulent chargebacks from the merchant to the issuer, which also matters for the ratios in chargebacks explained.

The code to watch is Visa 1A, additional authentication required, and Stripe's authentication_required. When it appears, run the 3DS flow and resubmit rather than treating it as a lost sale. Use exemptions and data-only flows, where your provider supports them, to cut friction on qualifying transactions.

How does local acquiring affect approvals?

Cards issued in one country often decline more when the payment is processed in another. Stripe's documentation says customers using cards issued in a different country than your account's registration may see an increased rate of declines, and suggests setting up accounts in larger markets to process charges locally.

One dated data point exists. A conference deck from PSE Consulting, presented on 6 December 2022, said domestic approval rates ranged from 94% for Germany down to 85% for France, with corresponding cross-border rates of 74% and 78%. That is 2022 data from one deck, so use it to understand the size of the question, not as a current forecast.

No independent, current benchmark was found for the uplift from local acquiring, and vendor claims vary widely. Test it: route a slice of one market through a local acquirer, compare order-level rates and recovery rates against a control, and include fees and settlement currency in the decision. Local acquiring vs cross-border acquiring walks through that trade-off, and BlindPay does not process card acquiring itself.

How do I monitor declines by issuer, country and reason?

Log every attempt with the decline code, the network advice code, the card brand, the issuer BIN, the card country, the amount and the payment type, then trend them weekly. A BIN is the first digits of a card number, which identify the issuer.

Stripe's documentation says the network decline code and the network advice code are 2 to 4 digit values from the card network, that their meaning differs by network, and that you should take the brand into account when you read them. Keep decline reason as a first-class field in your warehouse.

Use this lever table to prioritize. Effort is a rough guide, and evidence is what the cited sources say, not a measured uplift.

LeverHow it worksEffortEvidence
Clean data (CVC, postal code, address)Fewer declines from failed checksLowStripe's documentation advises collecting CVC and postal code
Soft/hard routing of retriesStops useless retries and feesMediumVisa categories and fees per TabaPay, 22 Oct 2026
Network tokensCard details stay current after expiry or replacementMediumCheckout.com documentation; no coverage figure
3-D Secure on risky paymentsAuthenticates, cutting fraud declinesMediumStripe's documentation: can lower decline rates where supported
Local acquiring for key marketsProcesses cards in the issuer's countryHighStripe's documentation; PSE deck from 2022
Fallback payment methodsGives the customer another way to payLow to mediumStripe's documentation mentions adding BNPL for insufficient funds
Issuer and reason dashboardsFinds where the loss concentratesMediumStripe's documentation on analyzing declines

An illustrative breakdown shows how to read it. Take the 2,100 declined attempts from the earlier example: 900 insufficient funds (51), 400 do not honor (05), 300 authentication required (1A), 250 expired card (54), 150 invalid account number (14) and 100 suspected fraud (59). Measured against all 10,000 attempts, that is 9.0, 4.0, 3.0, 2.5, 1.5 and 1.0 points of lost approvals, 21.0 in all. The 3DS and expired-card fixes (5.5 points) are directly actionable, while the 1.5 points of invalid numbers are not.

For the full set of related decisions, start from what merchant acquiring is. If you route across several acquirers, see payment orchestration with multiple acquirers.

For decline codes and their causes, read why card payments get declined.

Methodology and sources

Visa decline categories, reattempt limits and Mastercard merchant advice code retry rules come from TabaPay's network authorization best practices, updated 22 October 2026. Visa code meanings come from Stripe's network decline codes, and issuer behavior, advice codes and the retry recommendation from Stripe's card declines guide; both pages are undated and were read in November 2026. 3-D Secure comes from Stripe's 3D Secure page, and network tokens from Checkout.com's network token documentation, also undated.

The domestic and cross-border approval figures come from the PSE Consulting localisation deck, December 2022. Rules and codes change, and a few sources disagree on the exact reattempt count, so confirm with your acquirer. This guide cites no benchmark authorization rate.

Next, read local acquiring vs cross-border acquiring to decide whether to process cards in your customers' countries, or chargebacks explained to see how declines and disputes connect.

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.