Getting More Payments Approved (Auth Optimization)
- Baseline first: Compare approval rates by channel, issuer and country. Know yours before optimizing; see Benchmarks for published context
- Network tokens: Replace stored card numbers; compare approvals with raw PANs on matched payments. See published Visa context
- Retry logic: Read the decline and advice codes before another attempt. Stolen-card responses mean stop; an expired card needs corrected details or another card
- 3DS exemptions: Request TRA, low-value, recurring exemptions where you qualify
- Flag correctly: MIT vs. CIT matters. Wrong flags = higher declines
If customers are actively telling you their cards won't go through, don't start here - start with the Fix Declining Auth Rates playbook, an hour-by-hour diagnostic for a sudden decline spike. If the problem is customers abandoning checkout (not card declines), see Checkout Conversion. Come back to this page for the longer-term optimization work.
If only subscription renewals are failing, use failed-renewal recovery setup; for an account-wide spike, use Fix Declining Auth Rates.
Under $100K/month? Check your auth rate in your processor dashboard against your own baseline. If it drops, or customers complain, run the Fix Declining Auth Rates playbook to find out why. Start with that before the heavier optimizations below.
$100K-$500K/month? Start with retry logic and 3DS exemptions. Network tokens are worth a look.
Over $500K/month? All of it applies. Recovered payments are real revenue; measure what gets captured.
Your auth rate is the share of attempted card payments that the customer's bank approves, and auth optimization is the work of pushing that share up. More approvals can mean more money. Check what gets captured, at what value and cost.
Popular in This Section
- Fix Declining Auth Rates Playbook - Emergency diagnostic when declines suddenly spike
- Optimization Tactics - Network tokens, retry logic, 3DS exemptions, and transaction flags
- Increase Auth Rates Playbook - Step-by-step guide to improving approval rates
- Decline Codes Reference - Understanding why transactions fail and what to do
Most SMBs don't know theirs, and when you ask, they guess high.
Compare your own segments. A drop in approvals is money you're not collecting. Benchmarks has published context, with its scope.
What Matters
- Know your auth rate. Can't fix what you don't measure.
- Test network tokens against raw PANs. Visa publishes a comparison. Measure yours by issuer and transaction type.
- Retry logic matters. Wrong retries burn issuer trust. Right retries recover revenue.
- 3DS is a lever, not just compliance. Used well it improves auth. Used badly it kills conversion.
- Issuer declines have patterns. Learn your top decline reasons and fix the fixable ones.
Auth Optimization Topics
Know Your Auth Rate
Baseline before you touch anything.
How to Calculate
Auth Rate = Approved Transactions / Total Attempted Transactions × 100
What's Normal
| Segment | What to Compare |
|---|---|
| E-commerce (US domestic) | Your baseline by issuer, device and card brand |
| Subscription (initial) | First-payment approvals, separately from renewals |
| Subscription (recurring) | Renewals and retries by billing cycle |
| Card-present (CP) | Chip, tap and keyed entry separately |
| International CNP | Country and issuer within the same channel |
There's no universal channel target in the public sources checked for Benchmarks. Investigate drops from your own baseline; ask your processor for comparable merchants.
Where to Find It
Check your processor dashboard. Look for:
- "Authorization rate" or "Approval rate"
- Filter by: card brand, card type, geography, transaction type
"Where can I see our overall auth rate? Can I filter by card brand and geography?"
Quick Reference: Decline Types
| Type | Examples | Action |
|---|---|---|
| Soft decline | Insufficient funds (51), Issuer unavailable (91) | Check the specific response and advice; 51 may need customer action, while 91 may be temporary |
| Hard decline | Lost card (41), Stolen (43), Expired (54) | Stop on lost/stolen responses; get updated expiry details or another card for 54 |
| Ambiguous | Do not honor (05) | Follow network and processor advice; don't retry a stop instruction. Ask the customer to contact their issuer or use another card |
How to handle each one's in optimization tactics.
Scale Callout
| Volume | Focus |
|---|---|
| Under $100k/mo | Know your auth rate. Ensure basic retry logic is sane. Enable 3DS for high-risk only. |
| $100k-$1M/mo | Monthly decline code analysis. 3DS exemption strategy. Network token migration. |
| Over $1M/mo | Issuer-level optimization. Dedicated auth rate monitoring. A/B test 3DS strategies. Multiple processor routing for auth lift. |
Where This Breaks
-
International transactions. Cross-border declines are structurally higher. Local acquiring helps, but it's more moving parts.
-
High-risk MCCs. Some industries have elevated decline rates regardless of optimization. Issuers are more conservative.
-
New merchants without history. Issuers trust a track record. Until you've got one, you'll see higher declines.
Analyst Layer: Metrics to Track
| Metric | What It Tells You | Target |
|---|---|---|
| Overall auth rate | Baseline health | Compare matched segments with your own baseline |
| Auth rate by card brand | Network-specific issues | Compare each brand with its own matched issuer and customer baseline |
| Auth rate by geography | Cross-border friction | Compare countries within the same channel, route and customer mix |
| Soft vs. hard decline ratio | Retry opportunity | Classify your decline codes; compare the mix over time |
| Retry success rate | Retry logic effectiveness | Compare recovered payments on matched retry-eligible segments |
| 3DS challenge rate | Friction level | Compare by issuer, country and device |
| 3DS conversion rate | Challenge completion | Compare completed challenges on matched segments |
Trend Over Snapshot
Auth rate fluctuates. Track weekly trend, not daily snapshot.
Compare weekly trends on matched segments. Set alerts from your own transaction counts and normal variation; a small daily sample can swing sharply.
Next Steps
Just starting auth optimization?
- Pull your current auth rate from your processor dashboard → Baseline before optimizing
- Identify your top 5 decline codes → Focus fixes on highest-impact issues
- Check if you're using network tokens → If not, migrate stored cards to tokens
Ready to improve?
- Review optimization tactics → Network tokens, retry logic, 3DS
- Follow the increase auth rates playbook → Step-by-step optimization
- Implement smart retry logic → Recover soft declines without burning issuer trust
Already optimizing?
- Set up weekly auth rate monitoring → Track trends, not snapshots
- Segment by card brand and geography → Find specific weak spots
- Consider multi-processor routing → Route to best-performing processor by issuer
See Also
- Fix Declining Auth Rates - Emergency diagnostic for sudden decline spikes
- Optimization Tactics - Detailed optimization techniques
- 3DS Deep Dive - Authentication optimization
- Increase Auth Rates Playbook - Step-by-step guide
- Subscriptions and Recurring - Recurring billing
- Checkout Conversion - Reducing abandonment
- Decline Codes Reference - Understanding failures
- Payments Metrics - Performance tracking