Benchmarks (Operator Field Manual)
- Auth rate: CNP 85-90% typical, CP 98-99%; Apple/Google Pay 92-97%
- Fraud rate: CNP e-commerce 0.05-0.2%, digital goods 0.2-0.5%, travel 0.5-1.5%
- Chargeback ratio: Under 0.5% healthy, 0.75-0.9% danger, over 0.9% crisis (Visa threshold)
- Refund rate: 2-5% typical; refund-to-CB ratio should be 3-5:1
- Segment everything (CP vs. CNP, BIN, geo); trend over 4-8 weeks beats snapshots
Key Fact: Processors flag merchants around 0.9% chargeback ratio (internal threshold). Visa's VAMP Merchant Excessive level is 1.5% (2.2% in CEMEA only) with $8/dispute fines, and the non-compliant level is 0.5%. Mastercard ECM triggers at 100-299 chargebacks AND a 1.50-2.99% ratio, with fines up to $25,000/month at months 7-11. Above 300 and 3.00% you're in HECM instead. Stay under 0.5% to maintain a healthy buffer.
Use anchors, not absolutes. Compare to yourself over time and by segment (CP vs CNP, method, BIN, geo). Your baseline matters more than industry averages.
Last verified: Dec 2025. Benchmarks shift with market conditions; recalibrate annually.
What Matters (5 bullets)
- Segment everything. CP vs CNP, card brand, BIN/issuer, country, device. Aggregate numbers hide problems.
- Trend beats snapshot. Direction over 4-8 weeks matters more than any single week.
- Read metrics together. Auth, fraud, chargebacks, refunds, and alerts are interconnected.
- These ranges assume US domestic, mainstream MCCs. High-risk verticals run hotter.
- Date your thresholds. "Last verified" on any number you publish or operationalize.
Authorization Rate Benchmarks
Card-Not-Present (CNP)
| Performance | Auth Rate | Notes |
|---|---|---|
| Poor | Under 80% | Major issues: fix fraud rules, 3DS, or issuer relations |
| Below average | 80-85% | Room for improvement |
| Typical | 85-90% | Standard for US e-commerce |
| Good | 90-93% | Well-optimized stack |
| Excellent | 93-95% | Top of the range. Network tokens, retry logic, issuer work |
Card-Present (CP)
| Performance | Auth Rate | Notes |
|---|---|---|
| Poor | Under 95% | Investigate terminal issues, connectivity |
| Typical | 98-99% | Expected for retail |
| Excellent | 99%+ | Fully optimized |
By Payment Method
| Method | Typical Auth Rate | Notes |
|---|---|---|
| Cards (CNP) | 85-90% | Varies heavily by BIN/issuer |
| Cards (CP) | 98-99% | Chip/PIN highest |
| Apple Pay/Google Pay | 92-97% | Tokenized, higher than raw cards |
| PayPal | 95-98% | Account-to-account |
| ACH | 99%+ | But watch returns |
By Issuer Geography
| Region | Typical Auth Rate | Notes |
|---|---|---|
| US domestic | 88-93% | Baseline |
| UK/EU | 85-90% | SCA friction may impact |
| LATAM | 70-85% | Higher decline rates common |
| APAC | 75-88% | Varies widely by country |
| Cross-border | 5-15% lower | vs domestic acquiring |
That's below typical for US e-commerce. Three things to check first:
- Pull your decline codes. Decline code reference shows what each code means and whether you can retry.
- Segment CP vs CNP. If you're mixing them, your CNP number is worse than it looks.
- Check your 3DS configuration. Over-triggering challenges tanks auth rates. See 3D Secure optimization.
Already above 90%? You're doing well. Focus on fraud rates and chargeback ratios instead.
Key Fact: Typical CNP (online) authorization rates for US e-commerce are 85-90%. Apple Pay and Google Pay tokenized transactions achieve 92-97% because network tokens provide stronger issuer trust signals. If your auth rate is below 85%, check your decline codes, CP/CNP segmentation, and 3DS configuration first.
Fraud Rate Benchmarks
By Transaction Type
| Type | Typical Fraud Rate | Alert Level |
|---|---|---|
| CNP e-commerce | 0.05-0.2% | Over 0.3% = tighten rules |
| CP retail | 0.01-0.05% | Over 0.1% = investigate |
| Digital goods | 0.2-0.5% | Higher baseline expected |
| Subscriptions | 0.1-0.3% | Monitor initial vs recurring |
By Industry (CNP)
| Industry | Typical Fraud Rate | Notes |
|---|---|---|
| General retail | 0.1-0.2% | Baseline |
| Luxury/high-ticket | 0.3-0.8% | Attractive target |
| Digital goods | 0.3-0.6% | No physical verification |
| Travel | 0.5-1.5% | High-risk category |
| Gaming/gambling | 0.5-2%+ | Varies with regulation |
| Crypto/forex | 1-3%+ | Extreme high-risk |
Fraud Detection Metrics
| Metric | Good | Concerning |
|---|---|---|
| False positive rate | Under 1% | Over 2% hurts conversion |
| Catch rate (true positive) | 60-80% | Under 50% = rules too weak |
| Manual review rate | Under 5% | Over 10% = automation gaps |
| Review-to-block rate | 20-40% | Too high = rules too loose |
You're above the typical range for e-commerce. Start here:
- Identify the fraud type. First-party vs third-party vs ATO require different responses.
- Check if you have risk scoring. If not, that's your first investment. See risk scoring.
- Under $1M/year? Your processor's built-in fraud tools are probably enough. Don't buy vendor tools yet. See vendor landscape.
Fraud rate under 0.1%? Make sure your false positive rate isn't too high. Blocking good customers costs more than fraud at low rates.
Chargeback Benchmarks
Chargeback Ratio Thresholds
| Ratio | Status | Action |
|---|---|---|
| Under 0.5% | Healthy | Monitor normally |
| 0.5-0.75% | Caution | Increase monitoring |
| 0.75-0.9% | Danger | Active remediation needed |
| 0.9-1.5% | Crisis | Processor action likely: reserves, pass-through fees, termination |
| Over 1.5% | Network threshold breach | VAMP or ECM enrollment, once you also clear the count minimum |
Network Program Thresholds
| Network | Standard Threshold | Enhanced Threshold |
|---|---|---|
| Visa (VAMP) | ~0.9% (processor-enforced) | 1.5% merchant excessive (2.2% in CEMEA) + 1,500 combined fraud reports + disputes |
| Mastercard (ECM) | 100-299 disputes AND 1.50-2.99% | 300+ disputes AND 3.00%+ (HECM) |
| American Express | No published number | - |
| Discover | No published number | - |
Amex and Discover both run closed loops, and neither prints a ratio. Amex says only that it acts when your chargeback count is "considered disproportionate" (Merchant Reference Guide - U.S., section 11.10). Discover's Merchant Operating Regulations say it can terminate you for "excessive returns or Disputes, as determined by us in our sole discretion". That's the whole standard. The 1.0% you'll see quoted for Discover across the web traces to no Discover document. We used to print it. It's gone.
Chargeback Composition
| Reason Type | Typical Share | Red Flag |
|---|---|---|
| Fraud disputes | 50-70% | - |
| Friendly fraud (explicitly classified) | 20-40% | Over 50% = evidence problem |
| "Unrecognized" | 5-10% | Over 20% = descriptor issue |
| Service/quality | 10-20% | Over 30% = product/CX problem |
| Recurring billing | 5-15% | Over 25% = cancellation issue |
Note: These are reason-code-based categories. True friendly fraud (cardholder made the purchase but disputes) cuts across all categories and may represent 60-80% of total chargebacks for e-commerce merchants. That range is an industry estimate, not a measured figure.
You're in the danger zone. Here's what to do based on where you are:
- 0.75-0.9%: Active remediation. Reduce chargebacks fast covers the highest-impact actions.
- Above 0.9%: Program enrollment risk. 0.9% Panic Guide is the emergency playbook.
- Got your first chargeback? Don't panic. Your First Chargeback explains what it actually costs and when to worry.
Check your chargeback composition first. "Unrecognized" chargebacks above 20% means your billing descriptor is wrong. That's a 10-minute fix that can cut your ratio in half.
Refund Benchmarks
Refund Rate
| Rate | Interpretation |
|---|---|
| Under 2% | May be too restrictive; could increase disputes |
| 2-5% | Typical for most merchants |
| 5-10% | Higher but may be appropriate for some models |
| Over 10% | Investigate product/CX issues |
Refund-to-Chargeback Ratio
| Ratio | Interpretation |
|---|---|
| Under 2:1 | Refunding too little; disputes filling the gap |
| 3-5:1 | Healthy balance |
| 5-10:1 | Acceptable; strong refund policy |
| Over 10:1 | May be over-refunding; investigate |
Alert Performance Benchmarks
Ethoca/CDRN/Verifi Metrics
| Metric | Good | Target |
|---|---|---|
| Alert match rate | 30-50% | As high as possible |
| Response time | Under 2 hours | Ideally automated |
| Refund vs ignore | 80%+ refund | Depends on ticket size |
| Prevented disputes | 20-40% reduction | Track before/after |
Real-Time Alert Response
| Response Time | Performance |
|---|---|
| Under 1 hour | Excellent |
| 1-4 hours | Good |
| 4-24 hours | Acceptable |
| Over 24 hours | Missing value |
By Business Model
Subscriptions
| Metric | Benchmark |
|---|---|
| Initial auth rate | 80-85% |
| Recurring auth rate | 90-95% |
| Involuntary churn | Under 3% monthly |
| Dunning recovery | 10-30% of failed |
| Subscription fraud | 0.1-0.3% |
Digital Goods
| Metric | Benchmark |
|---|---|
| Auth rate | 80-88% (more 3DS step-up) |
| Fraud rate | 0.3-0.6% (higher baseline) |
| Dispute win rate | 30-50% (harder to prove) |
Physical Goods
| Metric | Benchmark |
|---|---|
| Auth rate | 85-92% |
| Fraud rate | 0.1-0.2% |
| Dispute win rate | 50-70% (delivery proof helps) |
| "Not received" share | 20-40% of disputes |
B2B
| Metric | Benchmark |
|---|---|
| Auth rate | 90-95% |
| Fraud rate | Under 0.1% |
| ACH return rate | Under 1% |
| Invoice payment | Net-30 to Net-60 typical |
Keyed Transaction Benchmarks (CP)
| Keyed % of CP Volume | Status |
|---|---|
| Under 2% | Normal |
| 2-5% | Investigate |
| 5-10% | Problem |
| Over 10% | Major red flag |
High keyed rates may indicate:
- Terminal issues
- Card-not-present masquerading as CP
- Employee fraud
- Training gaps
Benchmarks by Revenue Tier ($50K-$5M)
Industry averages hide the reality that a $100K/year Etsy seller and a $3M/year DTC brand face completely different numbers. Here's what to expect at your size.
| Metric | $50K-$250K/yr | $250K-$1M/yr | $1M-$5M/yr |
|---|---|---|---|
| Auth rate (CNP) | 82-87% | 85-90% | 88-93% |
| Fraud rate | 0.1-0.4% | 0.08-0.25% | 0.05-0.15% |
| Chargeback ratio | 0.3-0.8% | 0.2-0.6% | 0.15-0.4% |
| Refund rate | 3-8% | 2-5% | 2-4% |
| Processing cost | 2.7-3.9% | 2.3-2.9% | 2.1-2.6% |
| Manual review rate | 0% (no tools) | 2-5% | 5-10% |
| Reconciliation method | Eyeball bank deposits | Spreadsheet | Semi-automated |
Why smaller merchants have worse numbers:
- Auth rates are lower because smaller merchants often lack network tokens, retry logic, and issuer relationships
- Fraud rates are higher per transaction because fraudsters target merchants with weaker controls
- Chargeback ratios are higher because a single dispute hits harder (10 chargebacks on 2,000 transactions = 0.5%)
- Processing costs are higher mostly because of small tickets and flat-rate pricing, not because of weak negotiating leverage
The fixed per-transaction cents are what punish small merchants, and they don't shrink with volume. Square's Free plan is 2.6% + 15c card present and 3.3% + 30c online (squareup.com/us/en/payments/our-fees, verified 2026-08-02). Work through the effective rate:
| Average ticket | Card present, 2.6% + 15c | Online, 3.3% + 30c |
|---|---|---|
| $25 | 3.20% | 4.50% |
| $50 | 2.90% | 3.90% |
| $100 | 2.75% | 3.60% |
A small online seller with a $50 average ticket is at 3.90%, well above the benchmark range in the table above. That isn't a negotiating failure, it's arithmetic.
At the top of the table, the range describes what merchants that size typically pay. It is not the floor. Helcim publishes interchange + 0.25% + 7c card present for $100K-500K a month with no monthly fee (helcim.com/pricing, verified 2026-08-02). On this site's published pass-through assumption of 1.03% + $0.178 card present, that's an all-in 1.28% + $0.248 - and what it works out to depends entirely on your average ticket:
| Average card-present ticket | Helcim $100K-500K band, effective |
|---|---|
| $25 | 2.27% |
| $50 | 1.78% |
| $100 | 1.53% |
A single "2.28% effective" for that band can't be reproduced. It doesn't say which average ticket it assumes, and it runs on an interchange figure of 1.80% + $0.10, which isn't a blended card mix at all - it's roughly the rate for one card type, a consumer rewards credit card. The table above states the ticket, and the interchange assumption is published and sourced.
If those figures look far below the 2.1-2.6% row in the table, that's the point. The benchmark row tells you what merchants pay. The Helcim column tells you what a published rate card costs at a stated ticket. The gap between the two is the size of the prize for anyone still on flat rate above $1M a year.
The volume trap: At low volume, a handful of chargebacks can spike your ratio above network thresholds. A merchant doing 500 transactions/month only needs 5 chargebacks to hit 1.0%. See chargeback thresholds for the exact numbers.
How to Use These Benchmarks
Step 1: Establish Your Baseline
Before comparing to industry, know your own numbers:
- Calculate each metric for last 90 days
- Segment by CP/CNP, geography, method
- Document as your baseline
Step 2: Compare to Benchmarks
- Are you above/below industry norms?
- Which segments are problems?
- Where are quick wins?
Step 3: Track Trends
- Weekly: Auth rate, fraud rate, chargeback ratio
- Monthly: All metrics, segmented
- Quarterly: Deep dive, re-baseline
Step 4: Set Alerts
| Metric | Alert When |
|---|---|
| Auth rate | Drops over 0.5pp from baseline |
| Fraud rate | Rises over 0.05pp |
| Chargeback ratio | Approaches 0.75% |
| Refund rate | Changes over 1pp |
Where This Breaks
- Mixing CP and CNP. Never combine in single number.
- Seasonality. Holiday, promo weeks skew baselines. Compare like periods.
- High-risk MCCs. Travel, gaming, crypto run above these ranges. Set your own bands.
- International traffic. Expect lower auth, higher fraud. Get local acquiring before judging.
- Low volume. Small sample sizes create noise. Need 1000+ transactions for reliable rates.
Next Steps
Establishing your baseline?
- Follow the 4-step process - Baseline, compare, track, alert
- Segment by CP vs CNP - Never combine in one number
- Set internal alert thresholds - Catch problems early
Comparing to industry?
- Check auth rate benchmarks - CNP 85-90%, CP 98-99%
- Review fraud rate by industry - Know your vertical
- Understand chargeback thresholds - Under 0.5% healthy
Improving metrics?
- Optimize auth rate - Network tokens, retry logic
- Reduce fraud rate - Risk scoring, 3DS
- Lower chargeback ratio - Alerts, descriptors
Related
- Auth Optimization - Improving approval rates
- Payments Metrics - Tracking payment health
- Fraud Metrics - Measuring fraud rates
- Chargeback Metrics - Dispute measurement
- Chargeback Alerts - Prevention tools
- Processor Reporting Checklist - Data requirements
- Network Programs - VAMP, ECM thresholds
- Dispute Monitoring - Compliance programs
- 3D Secure - Auth rate impact
- Decline Codes - Understanding declines
- Risk Scoring - Fraud detection performance
- Subscriptions & Recurring - Recurring billing metrics