Approval rate is one of the most closely watched metrics in payment operations. It measures the percentage of authorization requests that issuing banks approve out of all attempts, making it a direct proxy for how much revenue a merchant captures versus loses at the point of payment.
How Approval Rate Works
When a customer completes checkout, a multi-step authorization flow determines whether the transaction succeeds. Understanding each step helps identify exactly where approvals break down and which interventions have the highest impact on recovery.
Customer Submits Payment
The customer enters card details or authenticates via a saved payment method. The merchant's checkout layer collects the card number, expiry date, CVV, and billing address, then passes them to the payment gateway for processing.
Gateway Forwards the Authorization Request
The gateway formats and transmits the authorization request to the relevant card network — Visa, Mastercard, Amex, or UnionPay. The request includes the transaction amount, merchant category code, and card data elements.
Network Routes to the Issuing Bank
The card network applies smart routing logic to direct the request to the bank that issued the customer's card. Network-level checks for card validity and basic fraud signals occur at this stage before the request reaches the issuer.
Issuer Evaluates the Transaction
The issuing bank runs its own risk models — checking available balance, fraud velocity rules, CVV and AVS match quality, and the merchant's historical reputation with that bank. This is where the vast majority of declines originate, and where approval rate optimization is most impactful.
Response Returned to Merchant
The issuer returns an approval or a decline code within milliseconds. An approved response completes the authorization hold; a decline triggers either an automated retry path or an error message surfaced to the customer at checkout.
Why Approval Rate Matters
Approval rate is not merely an operational metric — it is a revenue metric with a direct, measurable relationship to the top line. Every declined transaction that goes unrecovered represents lost GMV, wasted customer acquisition cost, and a higher probability of permanent churn.
Industry data underscores how much is at stake. Visa's benchmarking data shows that merchants who optimize authorization practices — through better card data, network tokens, and routing — see approval rate gains of 2 to 5 percentage points, which translates to an equivalent percentage of recovered revenue with no incremental marketing spend. Research by McKinsey found that payment failure is the second most common reason users abandon a purchase after reaching checkout, trailing only price dissatisfaction. CMSPI estimates that up to 25% of all declines are false positives — legitimate transactions blocked by overly conservative issuer fraud models — meaning a significant share of lost revenue is structurally recoverable.
The compounding cost of declines
A customer who experiences a payment decline is statistically less likely to retry immediately and significantly less likely to return for a future purchase. Optimizing payment conversion rate starts at the authorization layer — not the checkout UI.
The downstream effects compound the direct revenue loss. Declined customers who do not retry become churned customers. For subscription businesses, a single failed renewal can trigger an involuntary churn event that costs far more than the value of the missed payment itself.
Approval Rate vs. Authorization Rate
Merchants frequently encounter both terms across payment dashboards and PSP reporting, and use them interchangeably — but they can carry meaningfully different implications depending on where in the payment stack failures are being measured.
| Dimension | Approval Rate | Authorization Rate |
|---|---|---|
| What it measures | Issuer-approved transactions ÷ total attempts | Transactions reaching the issuer ÷ total attempts |
| Where failures occur | Issuer risk models, fraud rules, balance checks | Network routing errors, gateway timeouts, technical failures |
| Primary controller | Issuing bank, influenced by merchant data quality | Acquirer, gateway, and card network infrastructure |
| Typical range | 85–97% depending on vertical and geography | 97–99.9%; technical failures are relatively rare |
| Key improvement levers | Card data quality, network tokens, retry strategy | Redundant gateway routing, failover configuration |
| Revenue relevance | High — directly tied to completed sales volume | Medium — technical declines are usually auto-retried |
In practice, most payment teams use "approval rate" to describe the full end-to-end outcome: the transaction was sent, routed, and approved by the issuer. Where the distinction matters most is in root cause analysis — separating infrastructure failures from issuer-side rejections requires tracking both metrics independently.
Types of Approval Rate
Not all approval rates are created equal, and a blended figure often masks the segments where performance is weakest. Segmenting by type reveals which channels and card cohorts are underperforming and enables targeted optimization.
First-Attempt Approval Rate measures how often a transaction is approved on its initial authorization request without any retry. This is the cleanest signal of underlying data quality and issuer trust, and the most comparable metric across merchants.
Gross Approval Rate counts all approved transactions divided by all attempts, including retries. It produces a higher headline number but is useful for understanding total revenue capture across the full authorization lifecycle.
Net Approval Rate strips retries and counts unique customers or orders approved, giving a truer picture of how many customers successfully completed a purchase on a given session or day.
Issuer-Level Approval Rate segments performance by the customer's bank. Large issuers like Chase, Bank of America, or Barclays may have very different approval profiles for the same merchant, revealing issuer-specific relationship gaps or data mismatches that a blended rate conceals entirely.
Geographic Approval Rate compares domestic versus cross-border performance. Cross-border card-not-present transactions structurally face lower approval rates due to geographic distance signals and currency conversion flags in issuer fraud models.
Best Practices
Improving approval rate requires coordinated effort across commercial and technical functions. The strategies that matter most differ depending on whether you own the merchant relationship, the engineering stack, or both.
For Merchants
Enroll in account updater programs. Card-on-file credentials degrade rapidly — Visa estimates that roughly 30% of stored card numbers become outdated within 12 months due to card replacements, expirations, and issuer-driven reissuances. Account updater services from Visa and Mastercard automatically refresh stale credentials before they trigger avoidable declines.
Migrate to network tokens. Network tokens are issuer-managed identifiers that remain valid even when the underlying card number changes. They carry an elevated trust signal with issuers, which measurably improves approval rates. Visa reports a 2 to 3 percentage point lift for merchants who migrate from raw PANs to network tokens across their stored credential base.
Monitor chargeback rate proactively. High chargeback rates lower a merchant's reputation score with specific issuers, which suppresses future approval rates on that bank's cards. Keeping chargebacks below 0.5% is a prerequisite for maintaining healthy issuer relationships and preventing issuer-level blocks.
Use recognizable billing descriptors. Vague or generic billing descriptors increase friendly fraud declines, where customers do not recognize a charge and dispute it rather than contacting the merchant. A clear, brand-aligned descriptor reduces issuer-initiated declines and cardholder confusion simultaneously.
For Developers
Implement intelligent retry logic for soft declines. Soft declines — temporary issuer rejections due to insufficient funds, velocity limits, or risk flags — are often recoverable within hours. A well-designed retry logic strategy spaces retries at issuer-appropriate intervals, avoids triggering further velocity blocks, and selectively retries only the decline codes statistically likely to convert on a second attempt.
Send Level 2 and Level 3 transaction data where supported. For B2B transactions especially, transmitting enhanced data such as purchase order numbers, line-item details, and tax amounts signals legitimacy to corporate card issuers and can materially improve approval rates on purchasing and corporate cards.
Instrument raw decline code logging. Many payment platforms normalize or bucket decline codes before surfacing them in dashboards. Preserving the raw issuer response code enables granular root cause analysis — distinguishing a "do not honor" (05) from a "restricted card" (62) decline informs completely different remediation paths and is impossible to reconstruct from normalized data after the fact.
Common Mistakes
Even experienced payment teams make systematic errors that suppress approval rates without identifying the root cause. Awareness of these failure modes is a prerequisite for meaningful optimization.
Treating all declines as hard declines. Soft declines — temporary issuer rejections — account for a substantial share of all declined transactions and are recoverable with the right retry strategy. Merchants who surface an immediate error to the customer on any decline lose recoverable revenue that an automated retry loop would have captured without customer intervention.
Relying on blended approval rates without segmentation. A headline approval rate of 88% may hide the fact that Amex transactions are approving at 94% while a specific Mastercard BIN range sits at 71%. Without segmentation by card network, BIN range, issuer, and geography, optimization efforts are misdirected toward the wrong levers.
Ignoring 3DS friction as a pre-authorization abandonment driver. When Strong Customer Authentication flows are triggered unnecessarily on low-risk transactions, customers abandon before the authorization even reaches the issuer. This depresses apparent approval rate because fewer high-intent transactions are submitted to completion, making the issuer-side picture look better than the revenue picture actually is.
Failing to reconcile attempted versus settled transactions. Merchants sometimes report approval rate from gateway-side data rather than end-to-end authorization responses. This approach masks acquirer-level or network-level failures that are invisible within any single reporting tool and leads to systematically overestimated approval rates.
Overlooking the authorization-to-capture gap. A transaction can be authorized but never captured due to fulfillment failures or system errors. Conflating authorization approvals with successful captures overstates true approval rate and masks operational pipeline issues that sit entirely outside the payment authorization flow.
Approval Rate and Tagada
Tagada is a payment orchestration platform that gives merchants direct, configurable levers to improve approval rate across multiple acquirers, gateways, and card networks simultaneously — without requiring a processor switch or lengthy integration project.
How Tagada improves approval rate
Tagada's smart routing engine dynamically selects the acquirer path most likely to result in an approval for each individual transaction, based on real-time performance data, card BIN, merchant category, and geography. Combined with built-in retry orchestration for soft declines and native network token support, merchants on Tagada typically see approval rate improvements of 2 to 4 percentage points within the first 90 days — without changes to their existing checkout or card data infrastructure.