Skip to main content

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.

TL;DR
  • 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​

MetricDefinitionBenchmark
Authorization RateApproved transactions / Total attemptsCompare matched segments with your own baseline
Soft Decline RateRetriable declines / Total declinesClassify your codes; compare the mix over time
Hard Decline RateNon-retriable declines / Total declinesInvestigate changes by code, issuer and transaction type
CNP Auth Rate Baselines

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.

MetricDefinitionBenchmark
Authorization to Payout TimeAuthorization to funds in your bank accountTrack your actual days against your processor's payout schedule. Settlement and payout are separate steps
Reconciliation RateMatched transactions / TotalCompare with your baseline; investigate unmatched value and age
Exception RateUnmatched items / TotalExplain exceptions and track unresolved items to closure

Cost Metrics​

Your effective rate is the one to watch. It nets out everything else.

MetricDefinitionNotes
Effective RateTotal fees / Transaction volumeVaries by MCC
Interchange %Interchange / Total fees~60% on interchange-plus, ~40% on flat rate at a $50 card-present ticket. Why
Assessment FeesNetwork fees / VolumeUse 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​

MetricHow to MeasureWhat to Look For
Token auth rateAuth rate on network token transactionsCompare with raw PAN on matched issuers and transaction types; see Visa's published context
Token coverage% of stored cards using network tokensTrack eligible cards, tokenization failures and coverage over time
Credential updatesSuccessful updates / eligible stored cards, over a fixed periodMeasure failed-renewal recovery and involuntary churn separately, on matched subscriptions. More updates alone doesn't prove you lost fewer customers

3DS Impact Measurement​

MetricFormulaBenchmark
3DS challenge rateChallenged / Total 3DSCompare by issuer, country and device
3DS conversionCompleted / ChallengedCompare completed challenges on matched segments
3DS auth lift3DS auth rate - Non-3DS rateMatch issuer, risk and transaction type before comparing
Frictionless rateFrictionless / Total 3DSCompare with your baseline alongside fraud and completed purchases
MetricWhat It Tells You
Soft decline %Opportunity for retry recovery
Soft decline recovery rateHow effective is your retry logic
Hard decline by codeAttempts 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​

MetricCalculationAction
First attempt successSuccess / Total first attemptsBaseline health
Retry success rateSuccess / Total retriesMeasure retry value
Optimal retry timingCompare success by retry delayTune retry windows
Max retry effectivenessRecovery rate by attempt numberWhen 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:

IssuerAuth Rate% of VolumeTrend
Issuer A94%22%↑
Issuer B91%15%→
Issuer C89%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:

MetricProcessor AProcessor BDelta
Auth rate92.1%90.3%+1.8 percentage points
Average latency245ms312ms-67ms
3DS success87%82%+5 percentage points
Decline code clarityHighMediumN/A

Weekly Auth Optimization Review​

  1. Pull auth rate by day → spot anomalies
  2. Review top 5 decline codes → identify new patterns
  3. Check retry recovery rate → validate retry logic
  4. Compare issuer performance → flag outliers
  5. Track token migration progress → measure modernization

Scale Callout​

VolumeAnalytics Focus
Under $50K/moTrack auth rate monthly. That's enough.
$50K-$250K/moTrack auth rate + decline code breakdown monthly. Watch for "do not honor" spikes.
$250K-$1M/moAdd issuer-level performance tracking. Some issuers decline you more than others.
Over $1M/moFull issuer analysis, retry logic optimization, network token evaluation. Real-time monitoring. A/B test auth strategies.

Next Steps​

Setting up basic monitoring?

  1. Track authorization rate: Count approvals and attempts before and after a change
  2. Monitor settlement metrics: Reconciliation rate
  3. Calculate effective rate: Total fees / volume

Optimizing auth performance?

  1. Measure token vs PAN: Compare the same issuers and transaction types
  2. Track 3DS impact: Challenge and conversion rates
  3. Analyze issuer-level performance: Top 10 issuers

Building weekly review process?

  1. Follow optimization review: 5-step process
  2. Compare processors: If multi-processor
  3. Scale appropriately: By volume tier

Other Metrics Pages

Payments is just one piece of what you should be watching. See also: Fraud Metrics · Chargeback Metrics · Compliance Metrics · Operations Metrics

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.