Payments Metrics
Prerequisites
Before tracking payments metrics, understand:
- Auth optimization fundamentals
- Settlement and reconciliation basics
- Buying payments and fee structures
- Decline codes for troubleshooting
TL;DR
- Auth rate: 85-95% benchmark; alert on 5%+ drops within 1 hour
- Settlement: 1-3 days typical; reconciliation rate should be over 99.5%
- Cost: Effective rate varies by MCC; interchange ~70-80% of total fees
- Advanced: Track token vs. PAN auth lift (+2-5%), 3DS conversion (over 80%), issuer-level performance
- Scale: Under $100K/mo just track basic auth rate; over $2M/mo needs real-time monitoring
Key performance indicators for measuring payment operations health.
Authorization Metrics
| Metric | Definition | Benchmark |
|---|---|---|
| Authorization Rate | Approved transactions / Total attempts | 85-95% |
| Soft Decline Rate | Retriable declines / Total declines | 20-40% |
| Hard Decline Rate | Non-retriable declines / Total declines | 60-80% |
Settlement Metrics
| Metric | Definition | Benchmark |
|---|---|---|
| Settlement Time | Authorization to funds received | 1-3 days |
| Reconciliation Rate | Matched transactions / Total | >99.5% |
| Exception Rate | Unmatched items / Total | Under 0.5% |
Cost Metrics
| Metric | Definition | Notes |
|---|---|---|
| Effective Rate | Total fees / Transaction volume | Varies by MCC |
| Interchange % | Interchange / Total fees | ~70-80% of fees |
| Assessment Fees | Network fees / Volume | ~0.13-0.15% |
Monitoring Recommendations
- Track authorization rates by BIN, issuer, and card type
- Alert on >5% auth rate drops within 1 hour
- Review decline reason codes weekly
Auth Optimization Analytics
Beyond basic monitoring, measure these to optimize authorization performance.
Token vs. Non-Token Performance
| Metric | How to Measure | What to Look For |
|---|---|---|
| Token auth rate | Auth rate on network token transactions | Should be 2-5% higher than raw PAN |
| Token coverage | % of stored cards using network tokens | Target >80% of recurring |
| Token update rate | % of tokens auto-updated vs. expired | Higher = less involuntary churn |
3DS Impact Measurement
| Metric | Formula | Benchmark |
|---|---|---|
| 3DS challenge rate | Challenged / Total 3DS | 5-15% is typical |
| 3DS conversion | Completed / Challenged | >80% is healthy |
| 3DS auth lift | 3DS auth rate - Non-3DS rate | +3-10% typical |
| Frictionless rate | Frictionless / Total 3DS | >85% is good |
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 | Where you're losing customers permanently |
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 by top 10 issuing banks:
| Issuer | Auth Rate | % of Volume | Trend |
|---|---|---|---|
| Chase | 94% | 22% | ↑ |
| Bank of America | 91% | 15% | → |
| Wells Fargo | 89% | 12% | ↓ |
| ... | ... | ... | ... |
Action triggers:
- Single issuer drops 5%+ → investigate specific decline codes
- Overall auth drops 2%+ → check for system issues
- New decline code pattern → research and adapt
Processor Performance Comparison
If you use multiple processors:
| Metric | Processor A | Processor B | Delta |
|---|---|---|---|
| Auth rate | 92.1% | 90.3% | +1.8% |
| Average latency | 245ms | 312ms | -67ms |
| 3DS success | 87% | 82% | +5% |
| Decline code clarity | High | Medium | — |
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 $100k/mo | Basic auth rate tracking only. Don't overcomplicate. |
| $100k-$500k/mo | Add soft/hard decline tracking. Review weekly. |
| $500k-$2M/mo | Full issuer-level analysis. Tune retry logic. |
| Over $2M/mo | Real-time monitoring. A/B test auth strategies. |
Next Steps
Setting up basic monitoring?
- Track authorization rate - 85-95% benchmark
- Monitor settlement metrics - Reconciliation rate
- Calculate effective rate - Total fees / volume
Optimizing auth performance?
- Measure token vs PAN - 2-5% lift expected
- 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
Related Topics
- 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