Skip to article
ecomservices.io
Payments · How to run this
LedgerReconNot on this page yetFeesCalculatorSettlementCalculatorReservesCalculatorStatementsEntitiesNot on this page yetCommerce reconNot on this page yet

Library · Payments · How to run this

Authorize.net refund miss is not NMI gateway refund miss

How to run thisPayments3 steps
CalculatorAuthorize.net refund-fail share · Calculator lives in the articleOpen

Pull one Authorize.net Transaction Detail refund desk. Count failed refunds. Divide by submitted refunds. The quotient is AN refund-fail %.

Pair: Refund-fail share on Payments. NMI twin: NMI refund-fail. Mix twin: void vs refund.

Desk counts

Failed refunds — Authorize.net refund requests that errored, declined, or bounced in the desk window.

Submitted refunds — Refund requests pushed through Authorize.net in that same desk window.

AN refund-fail % = failed refunds ÷ submitted refunds × 100. When AN refund-fail % fattens, chase card token / settle state on that Authorize.net MID before you invent a chip.

Hard stops

Do not invent AN refund-fail %. Do not paste an NMI gateway refund CSV into Authorize.net boxes. Do not treat voids as failed refunds. Do not merge MIDs when one Authorize.net seat owns the fail pile.

Related: Payments, NMI refund-fail, void vs refund, retry-success.

Procedure

  1. Type refund fails and refund attempts.
  2. Read AN refund-fail %.
  3. Chase token / settle state when AN refund-fail % is fat.

Failure modes

  • Inventing AN refund-fail %.
  • Loading NMI refund rows into Authorize.net boxes.
  • Folding void/refund mix into refund fails.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

AN refund-fail %
Refund fails ÷ refund attempts × 100 on one Authorize.net refund window.

Work with us — We run this job on your accounts. Services

FAQ

Is this NMI refund-fail share?
Authorize.net Transaction Detail refund desk vs NMI gateway refund window. [Refund-fail share](/manuals/nmi-refund-fail-share) stays on NMI. Failed / submitted refunds never leave Authorize.net here.
Is this Authorize.net void vs refund mix?
Fail share vs void/refund mix. [Void vs refund mix](/manuals/authorize-net-void-vs-refund-mix) ratios voids against refunds. This page ratios failed refunds ÷ submitted refunds.
What AN refund-fail % should I invent?
None. Pull failed refunds and submitted refunds from the same Authorize.net Transaction Detail refund desk.