At a glance
The total dollar amount refunded to customers in the period. Absolute view (not ratio). The number to subtract from gross volume for a net-of-refunds figure.
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.
What the merchant should notice:
- Total USD 18,900 against USD 1.87M revenue is 1.0%. See
aut_refund_ratefor the rate view. - B2B average refund USD 1,600 is 5x web average. Reflects B2B AOV; a single B2B return is materially worse for revenue than a web return. Investigate the 3 B2B returns individually; each is a strategic loss.
- Web channel 38 refunds is volume-noisy. Top 1 to 3 SKUs typically drive 50 to 70% of count. Drilldown by SKU.
- MOTO single-event USD 1,700 is suspicious. A high-value phone-keyed-in MOTO refund warrants review for fraud (a sales-rep collusion pattern), legitimate large customer return, or refund-keyed-in error.
- ARB at zero is correct. Subscription cancellations stop future rebills; refunding past rebills is rare and typically only for billing errors.
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 → Transaction Statistics withtransactionType = refundTransaction filter. Sum the amount column.
Why our number may differ:
Cross-connector reconciliation:
Known limitations / merchant FAQs
A single large refund event spiked my volume, normal? Possible causes: (1) batch refund of a defective-product recall, (2) accidental double-charge corrected, (3) wholesale-customer return, (4) sales-rep error on a B2B order. Drill down byreferenceTransactionId to identify the original sale.
Refund volume is higher than gross sale, possible?
In a single day yes (refunds of older sales exceed today’s new sales). Over a 30-day window it shouldn’t happen and indicates a data sync issue or aggressive product-recall cycle.
Are unlinked refunds (credits) counted?
Yes. Authorize.Net allows “unlinked refunds” via transactionType = refundTransaction without a refTransId; these go through if the acquirer permits. Counted here. Most acquirers restrict unlinked refunds to chargeback-prevention scenarios.
Refund window expiration?
Authorize.Net allows 120 days from the original transaction. Beyond that, only unlinked credits work.
Refund vs void, financial difference?
A void cancels a captured-but-not-yet-batched transaction; the customer was never billed. A refund returns funds to a customer who was already billed (post-batch). This card counts only refunds.
ACH refunds, special handling?
Same refundTransaction type. Settlement takes 3 to 5 business days, same as the original.
Visa ownership of Authorize.Net, refund processing change?
No. Refund mechanics unchanged.