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

NMI gateway AU miss is not Solidgate PAN-refresh

How to run thisPayments3 steps
CalculatorNMI account-updater fail share · Calculator lives in the articleOpen

Export one NMI gateway AU cut. Count account-updater calls that hard-failed to refresh the stored card. Divide by AU attempts in that window. The chip is NM AU-miss % — leave Solidgate settle-rail PAN-refresh pages alone.

Pair: Account-updater fail share on Payments. Solidgate twin: SG PAN-refresh. CIT twin: NM CIT fail.

Gateway AU fields

Updater fails — NMI gateway account-updater calls that hard-failed to refresh the stored card.

Updater tries — NMI gateway account-updater calls attempted in that same cut window.

NM AU-miss % = updater fails ÷ updater tries × 100. A fat NM AU-miss % chip means repair NMI AU enrollment on that MID — blank chips stay blank.

Hard stops

Do not invent NM AU-miss %. Do not fold CIT or MIT declines into AU fields. Do not load vault-token fails into AU attempts. Do not dump Solidgate settle-rail or Primer workflow CSVs into NMI boxes. Do not blend MIDs when one NMI gateway cut owns the miss pile.

Related: Payments, SG PAN-refresh, NM CIT fail, NM vault-token.

Procedure

  1. Type updater fails and updater tries.
  2. Read NM AU-miss %.
  3. Repair NMI AU enrollment when NM AU-miss % is material.

Failure modes

  • Inventing NM AU-miss %.
  • Folding CIT or MIT declines into AU fields.
  • Dumping Solidgate settle-rail or Primer workflow CSVs into NMI 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

NM AU-miss %
AU hard-fails ÷ AU attempts × 100 on one NMI gateway AU cut.

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

FAQ

Is this Solidgate account-updater fail share?
NMI gateway AU cut vs Solidgate settle-rail PAN refresh. [Account-updater fail share](/manuals/solidgate-account-updater-fail-share) stays on Solidgate. AU hard-fails / attempts belong on this NMI gateway cut.
Is this NMI CIT fail share?
Account-updater hard-fails vs customer-initiated charge declines. [CIT fail share](/manuals/nmi-cit-fail-share) ratios CIT declines. Here you only ratio AU hard-fails against AU attempts.
What NM AU-miss % should I invent?
None. Pull AU hard-fails and AU attempts from the same NMI gateway cut.