What Is an Authorization Rate? Measure It and Fix Declines
Payments Glossary

What Is an Authorization Rate? How to Measure and Raise It

What is an authorization rate? See three ways to calculate it, which declines Visa and Mastercard let you retry, and how to cut false declines.

Woman working on a laptop on a bench in a cobblestone shopping street with mountains behind

Photo: Pixabay

On this page 6 sections
  1. What an Authorization Rate Measures and What It Leaves Out
  2. Three Ways to Calculate Your Authorization Rate
  3. What a Good Authorization Rate Looks Like Depends on the Channel
  4. Read the Decline Code Before You Retry
  5. What False Declines Cost You
  6. Fixes That Raise Approvals Without Inviting Fraud

Key takeaways

  • Ask which authorization rate a provider is quoting (first-attempt, raw attempt or order-level), because one day of traffic can produce three different numbers.
  • Visa code 05, "do not honor," is a generic Category 4 decline that you may retry within limits. Category 1 codes and Mastercard MAC 03 mean stop.
  • To estimate what false declines cost, calculate a low case and a high case for the share of declines that were real buyers, then compare that range with the cost of fixing them.

An authorization rate is the share of your card payment attempts that the cardholder's bank, called the issuer, approves. If issuers approve 920 of 1,000 attempts, for example, your authorization rate is 92%. The rate tracks revenue you lose after a customer has already decided to buy, so it is one of the few payment numbers tied directly to sales. Ask a processor what your authorization rate is and you'll usually get one blended percentage, which hides where the declines come from and which ones you can fix.

What an Authorization Rate Measures and What It Leaves Out

Every card payment starts with an authorization request. Your gateway sends the card number and amount through your processor and the card network to the issuer, along with whatever supporting data your checkout collected, such as the billing ZIP code and security code. Within a second or two the issuer approves or declines, based on the account's standing and its own fraud model.

Your authorization rate measures that issuer decision and nothing else. Three other failures look like declines on a dashboard but belong in separate buckets:

  • Gateway and processor errors, such as timeouts or malformed requests, never reached the issuer. You fix them with your provider.
  • Your own fraud filter's rejections also stop before the issuer sees anything. When the blocked shopper was legitimate, that is a false decline, and it will never show up in issuer approval data.
  • Abandoned checkouts, where someone left before submitting a card, are a conversion problem rather than an approval problem.

Keep these counts apart. Once they're blended, you can't tell whether to call your provider, loosen your own rules or redesign your checkout.

Three Ways to Calculate Your Authorization Rate

The basic formula is approved authorizations divided by authorization requests sent to issuers. Retries make the result slippery. A declined shopper retypes the card or tries again a minute later, and a subscription platform retries on its own schedule. Every attempt lands in the denominator.

Take an illustrative day. One hundred customers reach checkout, and issuers approve 88 of them on the first try. The 12 who were declined make 10 more attempts between them, and 4 of those go through. Your logs now show 110 attempts and 92 approvals, with 92 customers who paid. That one day produces three different rates:

MeasureCalculationResult
First-attempt approval rate88 ÷ 10088.0%
Raw attempt approval rate92 ÷ 11083.6%
Order-level (final) approval rate92 ÷ 10092.0%

Each answers a different question. First-attempt approval shows how issuers treat your transactions before any recovery. Order-level approval tells you how many buyers you actually converted. Raw attempt approval drops fast when retries pile up, which makes it the one to watch for card-testing attacks and runaway retry logic. When a provider quotes you a single rate, ask which of the three it is.

Then split every rate by segment, because a healthy blended number can hide one broken slice of your traffic: one-time checkout versus recurring renewals, first-time versus stored cards, domestic versus international cards, card brand, and debit versus credit. If your reporting can group declines by issuer, use that view too. The bank identification number (BIN) at the front of the card number identifies the issuer; Visa and Mastercard moved from six-digit to eight-digit BINs in April 2022, and our explainer on how BIN numbers identify the card issuer covers the details. A spike concentrated at one bank usually points to that issuer's fraud model, not your checkout.

What a Good Authorization Rate Looks Like Depends on the Channel

Processors and fraud vendors publish "average" approval rates, but the figures rarely agree. Some count raw attempts while others count final orders, and each vendor's merchant mix is different. An average drawn mostly from large retailers says little about a two-person supplement shop. Treat any single published number as loose context, not a target.

The gaps between channels do run in a consistent direction. In-person chip and tap sales approve at the highest rates, because the card's chip gives the issuer strong evidence that the real card is present. Online one-time sales run lower: the issuer can't see the card, so it leans on the data you send and its history with your business. Recurring renewals fail for their own reasons. Nobody is at the keyboard, stored cards go stale as they expire or get reissued, and insufficient funds turns up more often because a renewal date rarely lines up with a customer's payday. Cross-border transactions decline more often in both directions, since issuers tend to treat a foreign merchant as higher risk.

Your most useful benchmark is your own history, by segment. If first-time online approvals held steady for a year and then dropped several points in a month, something changed, and the segment breakdown will show where. Ask your processor what ranges it sees for merchants in your category and channel, and how it calculates them, before you compare.

Read the Decline Code Before You Retry

The usual advice says to retry "soft" declines and never retry "hard" ones. The networks are more specific than that, and their rules decide what a retry costs you.

Visa's Core Rules sort every decline response code into four categories, as summarized from Table 7-2 by PaymentBrief:

Visa categoryMeaningExample codesRetry allowed?
1Issuer will never approve04, 07, 12, 14, 15, 41, 43, 46, 57, R0, R1, R3Never, for the same card
2Issuer can't approve at this time51 (insufficient funds), 59, 61, 62, 65, 91, 96Yes, within the limit
3Data quality problem54 (expired card), 55, 82, N7 (CVV2 failure)Yes, after correcting the data
4Generic05 and codes not listed elsewhereYes, within the limit

The limit for Categories 2 through 4 is currently 20 attempts per card in 30 days. Plenty of processor help pages still say 15; PayKings notes that 15 was the original limit when Visa set up the categories in 2020 and 2021. Ask your processor which figure its systems enforce.

The misunderstood one is code 05, "do not honor." Merchants often treat it as a hard decline. Under Visa's rules it's a generic Category 4 code, so a few spaced retries are allowed, followed by contacting the customer if they fail.

Mastercard works differently. Alongside the decline, it can send a Merchant Advice Code (MAC). Per Paysight's summary of the codes, MAC 01 means updated card details are available, 02 means try again later, 03 means do not try again, 21 means the cardholder cancelled the recurring payment, and 24 through 30 tell you how long to wait before retrying an insufficient-funds decline.

The same source reports that Mastercard charges fees once declines on the same card at the same merchant pass 10 in 24 hours or 35 in 30 days. Our coverage of Mastercard's higher decline fee and retry costs explains how those charges show up. Whether and how your processor passes these network fees through is set by your processing agreement, so check it.

The practical decision: build retry logic around the network category or MAC your processor returns, not around a homemade list of "soft" and "hard" codes.

What False Declines Cost You

A false decline is a legitimate customer turned away, either by the issuer or by your own fraud rules. Nothing on your statement labels it, so you have to estimate the cost. For one-time sales, multiply checkout attempts by the share never approved, then by the share of those who were real buyers and didn't come back, then by your average order.

Here's an illustrative month. Assume 1,000 customers reach checkout and your order-level approval rate is 92%, which leaves 80 orders unapproved. Suppose half were legitimate buyers who gave up rather than try another card, and your average order is $60. That's 40 lost orders: $2,400 a month, or $28,800 a year, before counting anything those customers would have bought later.

The weakest input is the share of declines that were legitimate, so run a range. At 25%, the same month loses 20 orders, or $1,200. At 75%, it loses 60 orders, or $3,600. Plug in your own volume and average ticket and see whether even the low end justifies the work.

Subscriptions compound the loss, because a subscriber lost to a failed card takes every future payment with them. Illustrative again: 15 renewals a month fail and aren't recovered, the plan costs $30, and a typical subscriber would have stayed 8 more months. One month's failures cost 15 × $30 × 8 = $3,600 in future revenue. That's why dunning management for failed subscription payments belongs in the same conversation as approval rates.

Fixes That Raise Approvals Without Inviting Fraud

Raising approvals means saying yes to more real customers while your fraud controls stay intact. Our guide on how to improve authorization rates and reduce false declines has the full playbook. These moves usually matter most.

Send complete billing data. Collect the billing address, including ZIP code, and the security code on every online sale, and confirm your checkout maps billing details to the billing fields rather than the shipping address. It's the cheapest fix available.

Keep stored cards current. A network token replaces the raw card number with a token issued by the card network that stays valid when the issuer reissues the card. Visa reports an authorization lift of more than three percent with tokens on card-not-present transactions. Our explainer on network tokens and higher approvals for stored cards covers how they work. For cards that aren't tokenized, Visa Account Updater lets merchants or acquirers request the latest card details before charging a stored credential. Ask whether your gateway supports either.

Retry on a schedule. Space Category 2 and generic declines out instead of firing them back to back, time insufficient-funds retries around common paydays (or follow Mastercard's MAC timing), and stop entirely on Category 1 codes and MAC 03.

Use 3-D Secure selectively. 3-D Secure authentication lets the issuer verify the cardholder directly, which can turn a likely decline into an approval on a riskier order. On every order, it adds friction for customers who would have been approved anyway, so test it first where your first-attempt rate is weakest.

Audit the orders your own filter blocks. Pull a sample of rejected orders and look at who placed them. If repeat customers with clean histories keep appearing, your rules are too tight.

Stop card testing early. Velocity limits and bot protection keep stolen-card runs off your checkout. Those runs drag down your raw rate and generate the repeated declines that network retry fees target.

Check cross-border routing. When a large share of customers are abroad, compare local acquiring vs. cross-border processing before writing off foreign declines as unavoidable.

Several of these depend on what your gateway and processor support, especially tokens, account updater and decline-reason reporting. When you compare providers for online payment processing, ask to see a sample decline report broken out by network category and MAC before you sign.

Start with a 90-day decline report from your processor, split by channel and decline code. Calculate the three rates above for each segment, check how many retries landed on Category 1 or MAC 03 declines, and go after the segment with the worst first-attempt rate. If you're comparing providers, request a free quote from MannyPay and ask what decline reporting comes with the account. A specialist responds within one business day.

Sources

  1. Visa's Four Decline Categories: Which Codes You May Never Retry, and the 20-in-30 Limit (PaymentBrief)
  2. Card Retry Rules: How Often Visa and Mastercard Let You Retry a Declined Payment (PayKings)
  3. Soft vs Hard Declines: Which Decline Codes to Retry and When (Paysight)
  4. A Deep Dive into Tokenized Transactions (Visa)
  5. Protect Recurring Revenue with Visa Account Updater (Visa)
  6. Preparing for 8-Digit BINs (Deloitte)

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading