Library · Payments · How to run this
Authorize.net soft-decline mix is not NMI soft-decline mix
Weight soft decline codes by all decline codes on one Authorize.net decline export. That weight is AN soft-decline %.
Pair: Soft-decline share on Payments. NMI twin: NMI soft. Solidgate twin: Solidgate soft.
What you type
Soft declines — Authorize.net codes marked soft / retryable in the export.
All declines — Every Authorize.net decline code in that same export.
AN soft-decline % = soft ÷ all × 100. A fat AN soft-decline % usually means retry / updater seating matters on that MID — chase that path; never invent an AN soft-decline chip.
What not to do
Never invent AN soft-decline %. Never load NMI or Solidgate decline rows into Authorize.net inputs. Never fold settle-reject counts into soft. Never blend MIDs when one Auth.net seat owns the soft pile.
Related: Payments, NMI soft, Solidgate soft, settlement-reject.
Procedure
- Type soft declines and all declines.
- Read AN soft-decline %.
- Seat retry / updater when AN soft-decline % is material.
Failure modes
- Inventing AN soft-decline %.
- Dumping an NMI or Solidgate decline file into Authorize.net fields.
- Folding settle-reject counts into soft counts.
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 soft-decline %
- Soft 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 soft-decline share?
- Gateway book vs NMI. [Soft-decline share](/manuals/nmi-soft-decline-share) stays on NMI. Soft / all counts never leave Authorize.net here.
- Is this Solidgate soft-decline share?
- Separate stack. [Soft-decline share](/manuals/solidgate-soft-decline-share) stays on Solidgate. Authorize.net owns every count here.
- What AN soft-decline % should I invent?
- None. Export soft declines and all declines from the same Authorize.net decline file.