What Is a Good Authorization Rate? Benchmarks by Business Type
What is a good authorization rate? Learn to calculate yours without retries or fraud blocks, then compare it fairly against merchants on the same channel.

Photo: Pixabay
On this page 6 sections
- What an Authorization Rate Measures, and What It Leaves Out
- How to Calculate Authorization Rate Without Skewing the Number
- What Is a Good Authorization Rate by Channel
- Why Your Industry and Card Mix Move the Benchmark
- Reading Your Processor's Decline Reports
- When a Low Authorization Rate Means It's Time to Act
Key takeaways
- Clean the raw number first: remove card verifications and test traffic, and move your own fraud blocks and gateway errors into separate metrics.
- Benchmark on first-attempt authorization rate. Judge your retries and dunning by eventual approval rate.
- Track payment acceptance rate next to the issuer numbers. A wide gap means your own fraud rules are turning customers away.
- The mix of decline reasons tells you more than the rate. Insufficient funds is normal, but a growing share of generic or fraud-suspect declines is something you can fix.
A good authorization rate is one that holds up against merchants who sell through the same channel to similar customers, measured the same way you measure yours. In-store chip and tap sales should be approved almost every time, and their declines should mostly come from real problems such as an empty account. Online and recurring sales are approved less often, and cross-border sales less often still. So the useful answer to what is a good authorization rate is a method: calculate your number cleanly, then compare each channel against the right peer group.
Merchants who think their rate is bad are often looking at one blended figure. That figure counts their own fraud blocks and retries as if issuers had declined them. Clean those out before you compare anything.
What an Authorization Rate Measures, and What It Leaves Out
An authorization is the real-time request your processor sends through the card network to the bank that issued your customer's card. The issuer answers yes or no, usually with a response code that gives a reason. Your authorization rate is the share of those requests the issuer approved.
Merchant account approval is a separate matter. Underwriting is a decision your processor and its sponsor bank make about your business, and it has no bearing on how often issuers approve your customers' cards.
The rate also says nothing about whether a sale stuck. An approved authorization can still be reversed or charged back. If your rate climbs while disputes climb with it, treat that as a warning and read it alongside your chargeback ratio thresholds.
The biggest gap is payments that never reached an issuer. If your fraud tool or a gateway timeout stopped the payment, the bank never said no. A checkout with aggressive fraud rules can post a high issuer approval rate while turning away good customers before any bank sees them. The number your revenue actually feels is the payment acceptance rate: orders paid divided by orders attempted. Track it next to the issuer rate, because a gap between the two often points to false declines that reject good customers inside your own stack.
How to Calculate Authorization Rate Without Skewing the Number
Start with a raw export of authorization attempts from your gateway or processor. Use at least a full month so weekly swings even out. Then take out, or set aside, the following:
- Account verifications. Card checks that carry no purchase amount, run when a customer saves a card or starts a free trial, are approved at high rates and flatter your result.
- Your own blocks. Attempts stopped by your fraud rules or gateway filters go into a separate block rate.
- Technical failures. Timeouts and system-unavailable responses go into an error rate. When that rate rises, look first at your integration or your processor.
- Test transactions and duplicates. Remove test cards, plus the second submission created when a customer double-clicks "Pay."
- Retries. Decide how you'll count them before you calculate anything.
Retries decide which of two issuer-facing numbers you get. The first-attempt authorization rate is approvals on the first try divided by first attempts sent to issuers. Your retry strategy can't distort it, so it's the right number for benchmarking. The eventual approval rate is orders approved at some point divided by unique orders sent to issuers. It shows how well your retries and dunning recover failed payments.
Count every retry as a new attempt and a merchant that retries heavily looks worse than one that gives up. Retrying hard declines also costs money, and both card networks have changed how they treat repeat attempts. Our coverage of Mastercard's fee on declined transactions and Visa's decline code changes explains what changed.
Two channels need their own counting rules. Hotels and travel sellers should count per booking or folio, not per authorization message, because one stay can generate a pre-authorization followed by several incremental authorizations. In-store merchants who accept partial approvals on prepaid and debit cards should count those as approvals but track them separately, since the customer still had to cover the rest another way.
A Worked Example: One Month Measured Five Ways
The figures below are illustrative, not real merchant data. Assumptions:
- An online store's gateway log for one month shows 10,000 attempts, 7,600 of them marked "approved."
- Of those attempts, 400 are zero-amount card verifications, and every one was approved.
- Another 600 were blocked by the store's own fraud rules before reaching an issuer. Each blocked attempt is a separate order that was never tried again.
- A further 200 were gateway timeouts. The gateway resubmitted them automatically, and the resubmissions sit among the purchase attempts.
- That leaves 8,800 purchase authorizations sent to issuers: 7,500 first attempts and 1,300 retries. Each retry belongs to an order whose first attempt was declined. Issuers approved 6,800 first attempts and 400 retries.
| Metric | Calculation | Result |
|---|---|---|
| Naive dashboard rate | 7,600 ÷ 10,000 | 76.0% |
| Issuer rate, all attempts | 7,200 ÷ 8,800 | 81.8% |
| First-attempt authorization rate | 6,800 ÷ 7,500 | 90.7% |
| Eventual approval rate | 7,200 ÷ 7,500 | 96.0% |
| Payment acceptance rate | 7,200 ÷ (7,500 + 600 blocked) | 88.9% |
The same month produces numbers 20 points apart, from 76.0% to 96.0%. The naive figure is low because it treats blocks and timeouts as declines and counts every retry as a fresh attempt. The more telling comparison sits at the bottom of the table. Issuers finally declined 300 orders (7,500 minus 7,200), while the store's own fraud rules stopped 600. This merchant's first job is reviewing its fraud rules, not chasing issuers.
What Is a Good Authorization Rate by Channel
You'll find plenty of published figures for an "average card approval rate," and they don't agree. Each one applies its own calculation to its own mix of merchants, and many come from vendors selling optimization tools. A figure quoted without its method can't be compared with yours. A more reliable authorization rate benchmark starts from how the channels rank against each other, because that ranking is consistent.
| Channel | How it usually compares | Main decline drivers | Compare against |
|---|---|---|---|
| Card-present (chip, tap, PIN) | Highest of any channel | Insufficient funds; expired or blocked cards | In-store merchants with a similar ticket size and debit share |
| Keyed sales in store | Closer to online than to chip | Missing chip data; typing errors | Your own keyed history |
| Card-not-present, domestic | Lower than in person | Issuer fraud scoring; AVS and CVV mismatches | Online merchants in your category |
| Recurring renewals | High with updated card data, drops fast without it | Expired or reissued cards; empty accounts on billing day | Your own renewal cohorts |
| Cross-border card-not-present | Lowest of the mainstream channels | Issuer caution toward foreign merchants | Merchants selling into the same countries |
Your rate is in good shape when it holds steady month to month and sits near the peer comparison your processor can give you for your category. The decline mix is the second test. Most declines should be customer-side, such as insufficient funds, rather than generic or suspected-fraud responses.
Why Your Industry and Card Mix Move the Benchmark
Card mix comes first. Debit and prepaid cards decline more often for insufficient funds, and that has nothing to do with your setup. The leading digits of a card number identify the issuer and card type (how BIN numbers identify cards), so you can split declines by card type and see whether one segment drags your average down.
Category matters too. Issuers score risk partly on the merchant category code, so high-risk categories see more suspected-fraud declines on the same cards. The fix is cleaner authorization data and the right acquiring setup, such as a high-risk merchant account built for your category. Changing your MCC to look like a different business is never the fix. Miscoding violates network rules and can end your processing.
Subscriptions and Memberships
Split customer-initiated signups from merchant-initiated renewals. Free-trial conversions are often the weakest point, because some trial users sign up with prepaid or nearly empty cards. Renewal failures cluster around card expirations and reissues, which is where network tokens for fewer failed renewals and well-timed retries earn their keep.
Digital Products and Services
Cheap items with instant delivery attract card testing, where fraudsters run stolen card numbers through small purchases to see which ones work. A single attack can add thousands of declines in an hour. Look at your rate with and without the attack window to diagnose it, but don't simply exclude it from your records. Issuers saw those attempts, so put the effort into stopping them.
E-Commerce Stores
Physical-goods stores collect address data that digital sellers often lack. Sending the full billing address and CVV with each authorization gives issuers more to approve on. Expect more declines around holiday peaks, when issuer fraud models tighten and gift buyers ship to addresses other than their own.
Travel and Tourism
Large tickets, bookings made far in advance, foreign cardholders and multi-message authorizations all push travel rates below domestic retail. Compare by booking, and compare cross-border traffic only with cross-border traffic. If foreign issuers decline you often, read when local acquiring pays off. For the fees and approval issues that come with foreign cards, see our guide to accepting international cards.
Reading Your Processor's Decline Reports
Sort decline responses into buckets before you study individual codes:
- Customer-side (insufficient funds, over limit): normal, and mostly outside your control.
- Card data (expired card, wrong CVV): stale stored cards or checkout errors.
- Issuer risk (suspected fraud, generic "do not honor"): where better data and authentication help.
- Technical: belongs in your error rate, not your decline rate.
Hard declines such as closed accounts or lost and stolen cards should never be retried. For individual codes, see what each credit card decline code means.
Then cut the report by issuer, country, card type, hour of day and checkout version. A burst of CVV mismatches across many cards in a short window usually means card testing. Generic declines from one large issuer are worth raising with your processor. Declines concentrated in one country point to a cross-border setup problem. A rise right after a checkout redesign or gateway switch suggests the new integration is dropping data fields.
When a Low Authorization Rate Means It's Time to Act
Act when a drop has no explanation, or when generic and fraud-suspect declines grow as a share of the total. A wide gap between your acceptance rate and your eventual approval rate is also a signal, because it means your own rules are costing sales. The usual fixes are complete authorization data, tokenized stored cards, smarter retry timing, authentication where it reduces issuer doubt, and a better acquiring path for foreign cardholders. Our guide to fixes for false declines works through each one.
MannyPay offers 3-D Secure authentication and international payment processing with cross-border acquiring paths. If your decline reports point to your setup rather than your customers, request a free quote and a MannyPay specialist will respond within one business day.
This week, pull the last quarter of authorization data and calculate the clean metrics from the worked example for each channel. Then ask your processor for a peer comparison within your merchant category. That tells you whether the problem sits with issuers or with your own fraud rules.
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.


