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 hard kills are not NMI hard kills

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

Pull one Authorize.net gateway export. Count issuer codes tagged terminal. Divide that count by every decline row in the file. The quotient × 100 is AN hard-decline %.

Pair: Hard-decline share on Payments. Processor twin: NMI hard. Soft twin: Authorize.net soft.

Export math

Terminal issuer codes — Authorize.net rows the gateway flags as hard / do-not-retry in that export.

Full decline file — Every Authorize.net decline row in the same export (soft plus terminal).

AN hard-decline % = terminal issuer codes ÷ full decline file × 100. A high AN hard-decline % means that gateway is burning cards that will not retry — move volume or fix the offer; leave blank chips alone.

Guardrails

Do not invent AN hard-decline %. Do not park soft-only rows in the terminal count. Do not paste an NMI processor decline file into Authorize.net fields. Do not merge gateways when one Authorize.net MID owns the terminal mix.

Related: Payments, NMI hard, Authorize.net soft, settlement reject.

Procedure

  1. Type hard declines and all declines.
  2. Read AN hard-decline %.
  3. Cut hard burns when AN hard-decline % is material.

Failure modes

  • Inventing AN hard-decline %.
  • Loading soft-only counts into the hard pile.
  • Folding NMI decline rows into Authorize.net boxes.

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 hard-decline %
Hard declines ÷ all declines × 100 on one Authorize.net decline export.

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

FAQ

Is this NMI hard-decline share?
Gateway book vs NMI processor book. [Hard-decline share](/manuals/nmi-hard-decline-share) stays on NMI. Terminal / file totals never leave Authorize.net here.
Is this Authorize.net soft-decline share?
Terminal pile vs retryable pile. [Soft-decline share](/manuals/authorize-net-soft-decline-share) stays on soft codes. This page only scores terminal codes over the full Authorize.net decline file.
What AN hard-decline % should I invent?
None. Source terminal issuer codes and the full decline file from the same Authorize.net gateway export.