At a glance
The percentage of Authorize.Net transactions that resulted in a chargeback. Buyer-initiated reversal through the issuing bank. The most expensive type of payment loss: scheme fees plus the funds plus the time-cost of dispute response.
Calculation
Calculated automatically from your Authorize.net data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
“Heartland Hardware Co.”, 30 days ending 02 May 26.
Chargeback reasons (top 6 in this window):
What the merchant should notice:
- Blended 0.20% is healthy. Below 0.5% threshold. B2B portal at 0.00% is structural (procurement-managed, no consumer-dispute pathway).
- ARB at 0.54% is the alert. Subscription chargebacks usually mean the customer cancelled but kept getting billed; the customer dispute the unrecognised charge. Operational fix: aggressive ARB-cancellation UX, clear billing-descriptor (the line on the bank statement).
- Reason 4837 (no authorisation) at 2 is normal. This is the “friendly fraud” pattern: customer denies a real purchase. Defend with signed proof-of-delivery, AVS match, IP and device fingerprint.
- Win rate matters. Authorize.Net with strong Cardinal Cardinal Commerce 3DS data and AVS match has a 35 to 50% win rate on disputes. Heartland should always defend; cost is low (USD 25 to 50 in time) vs USD 4,200 in lost funds.
- Visa CE 3.0 / Mastercard Compelling Evidence 3.0 allow merchants to push back on “card-not-recognised” reason 4837 with proof of prior similar transactions. Authorize.Net supports this via the dispute-management interface.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Authorize.Net Dashboard: account.authorize.net → Reports → Chargebacks, with date filter. The acquirer’s monthly statement also shows chargeback count and fees. Why our number may differ:
Cross-connector reconciliation: