Payments Metrics
This page is the money coming in: how many payments get approved, when they settle, and what they cost you. Looking for chargeback ratios, fraud rates or normal ranges?
An approval rate counts approved payment attempts. Chargeback and fraud ratios count different events. Check the metric and denominator before comparing them.
- Auth rate: Know your approval rate before changing anything. Compare the same countries, card types and new or returning customers afterward. Investigate sudden drops
- Settlement: Track the days on your processor's payout schedule. Investigate unmatched transactions and their value
- Cost: Effective rate varies by MCC. In the cost model at a $50 card-present ticket, interchange is roughly 60% of fees on interchange-plus and closer to 40% on a flat rate. Not the 70-80% some sources quote
- Advanced: Compare approvals on network tokens (stand-in numbers the networks issue in place of the card number) with approvals on the card number itself (the PAN). Track 3DS challenge completion and issuer-level performance against your own baselines
- Scale: Under $50K/mo, review your approval rate monthly, and check the dashboard any day sales dip rather than waiting for that review. Real-time monitoring sits in the over-$1M/mo tier below
Revenue is easy to watch. The middle isn't. These numbers tell you whether the stretch between tap and deposit is healthy. Start with auth rate. It's the one that moves money today.
Authorization Metrics
| Metric | Definition | Benchmark |
|---|---|---|
| Authorization Rate | Approved transactions / Total attempts | Compare matched segments with your own baseline |
| Soft Decline Rate | Retriable declines / Total declines | Classify your codes; compare the mix over time |
| Hard Decline Rate | Non-retriable declines / Total declines | Investigate changes by code, issuer and transaction type |
Compare your US domestic card-not-present rate with its own history. Compare matched segments too. Benchmarks has published context. It doesn't set a channel target. When approvals drop, pull a breakdown of decline codes first. A spike in code 05 points at issuer declines. Check fraud-tool blocks, 3DS failures and processor configuration too. See Auth Optimization for the next steps.
Settlement Metrics
Unmatched transactions need an explanation. Track their count, value and age; a high match rate can still hide a costly exception.
| Metric | Definition | Benchmark |
|---|---|---|
| Authorization to Payout Time | Authorization to funds in your bank account | Track your actual days against your processor's payout schedule. Settlement and payout are separate steps |
| Reconciliation Rate | Matched transactions / Total | Compare with your baseline; investigate unmatched value and age |
| Exception Rate | Unmatched items / Total | Explain exceptions and track unresolved items to closure |
Cost Metrics
Your effective rate is the one to watch. It nets out everything else.
| Metric | Definition | Notes |
|---|---|---|
| Effective Rate | Total fees / Transaction volume | Varies by MCC |
| Interchange % | Interchange / Total fees | ~60% on interchange-plus, ~40% on flat rate at a $50 card-present ticket. Why |
| Assessment Fees | Network fees / Volume | Use your actual charges. This site's US model assumes 0.14% + $0.02 per transaction, and that figure is unverified. Visa, Mastercard and Amex publish Canadian schedules, which don't verify it |
Monitoring Recommendations
An auth rate drop costs you money every hour it goes unnoticed, so don't wait for a monthly report to catch it.
- Track authorization rates by BIN, issuer, and card type
- Set auth-rate alerts from your own baseline, transaction counts and normal variation
- Review decline reason codes weekly
Auth Optimization Analytics
Once you've got the basics running, these are the numbers that move auth rate.
Token vs. Non-Token Performance
| Metric | How to Measure | What to Look For |
|---|---|---|
| Token auth rate | Auth rate on network token transactions | Compare with raw PAN on matched issuers and transaction types; see Visa's published context |
| Token coverage | % of stored cards using network tokens | Track eligible cards, tokenization failures and coverage over time |
| Credential updates | Successful updates / eligible stored cards, over a fixed period | Measure failed-renewal recovery and involuntary churn separately, on matched subscriptions. More updates alone doesn't prove you lost fewer customers |
3DS Impact Measurement
| Metric | Formula | Benchmark |
|---|---|---|
| 3DS challenge rate | Challenged / Total 3DS | Compare by issuer, country and device |
| 3DS conversion | Completed / Challenged | Compare completed challenges on matched segments |
| 3DS auth lift | 3DS auth rate - Non-3DS rate | Match issuer, risk and transaction type before comparing |
| Frictionless rate | Frictionless / Total 3DS | Compare with your baseline alongside fraud and completed purchases |
Soft vs. Hard Decline Trends
| Metric | What It Tells You |
|---|---|
| Soft decline % | Opportunity for retry recovery |
| Soft decline recovery rate | How effective is your retry logic |
| Hard decline by code | Attempts you shouldn't resubmit unchanged. Where it's allowed, invite a corrected card or another payment method. The customer isn't necessarily lost |
Recurring Retry Analytics
| Metric | Calculation | Action |
|---|---|---|
| First attempt success | Success / Total first attempts | Baseline health |
| Retry success rate | Success / Total retries | Measure retry value |
| Optimal retry timing | Compare success by retry delay | Tune retry windows |
| Max retry effectiveness | Recovery rate by attempt number | When to stop retrying |
Issuer-Level Performance
Track auth rates for the 10 card-issuing banks you see most, because they won't all behave the same. Illustrative report, invented figures:
| Issuer | Auth Rate | % of Volume | Trend |
|---|---|---|---|
| Issuer A | 94% | 22% | ↑ |
| Issuer B | 91% | 15% | → |
| Issuer C | 89% | 12% | ↓ |
| ... | ... | ... | ... |
Action triggers:
- Single issuer drops from its usual range → investigate specific decline codes
- Overall auth drops outside normal variation → check for system issues
- New decline code pattern → research and adapt
Processor Performance Comparison
If you're running more than one processor, compare them head to head on matched payments. Illustrative report, invented figures:
| Metric | Processor A | Processor B | Delta |
|---|---|---|---|
| Auth rate | 92.1% | 90.3% | +1.8 percentage points |
| Average latency | 245ms | 312ms | -67ms |
| 3DS success | 87% | 82% | +5 percentage points |
| Decline code clarity | High | Medium | N/A |
Weekly Auth Optimization Review
- Pull auth rate by day → spot anomalies
- Review top 5 decline codes → identify new patterns
- Check retry recovery rate → validate retry logic
- Compare issuer performance → flag outliers
- Track token migration progress → measure modernization
Scale Callout
| Volume | Analytics Focus |
|---|---|
| Under $50K/mo | Track auth rate monthly. That's enough. |
| $50K-$250K/mo | Track auth rate + decline code breakdown monthly. Watch for "do not honor" spikes. |
| $250K-$1M/mo | Add issuer-level performance tracking. Some issuers decline you more than others. |
| Over $1M/mo | Full issuer analysis, retry logic optimization, network token evaluation. Real-time monitoring. A/B test auth strategies. |
Next Steps
Setting up basic monitoring?
- Track authorization rate: Count approvals and attempts before and after a change
- Monitor settlement metrics: Reconciliation rate
- Calculate effective rate: Total fees / volume
Optimizing auth performance?
- Measure token vs PAN: Compare the same issuers and transaction types
- Track 3DS impact: Challenge and conversion rates
- Analyze issuer-level performance: Top 10 issuers
Building weekly review process?
- Follow optimization review: 5-step process
- Compare processors: If multi-processor
- Scale appropriately: By volume tier
Payments is just one piece of what you should be watching. See also: Fraud Metrics · Chargeback Metrics · Compliance Metrics · Operations Metrics
Related Topics
- Accept Payments: The payments hub
- Auth Optimization: Improving approval rates
- Decline Codes: Understanding decline reasons
- 3D Secure: Authentication impact on auth rates
- Subscriptions & Recurring: Retry and dunning metrics
- Chargeback Metrics: Related dispute measurement
- Fraud Metrics: Related fraud measurement
- Settlement & Reconciliation: Post-capture metrics
- Processor Management: Comparing processor performance
- Network Programs: Threshold monitoring
- Buying Payments: Cost metrics
- Reading Statements: Fee analysis
- Operations Metrics: Operational KPIs