Library · Payments · How to run this
NMI settlement delay is not Braintree settlement delay
From one NMI settle cut, subtract capture day from settle day. That difference is delay days. Count settled txs so the cut stays real.
Pair: Settlement-delay days on Payments. Other gateway: Braintree settlement-delay. Auth twin: auth-expire share.
What you type
Capture day — Day index when NMI captured the settled txs.
Settle day — Day index when those txs settled.
Settled txs — Transactions that settled in that same NMI cut.
Delay days = settle day − capture day. When delay days run fat, chase NMI batch cutoffs — never invent a delay chip.
What not to do
Never invent delay days. Never paste Braintree batch indexes into NMI fields. Never treat auth expires as settle delay. Never blend MIDs when one seat owns the lag.
Related: Payments, Braintree settlement-delay, auth-expire share, partial-settle gap.
Procedure
- Type capture day, settle day, and settled txs.
- Read delay days.
- Chase NMI batch cutoffs when delay days are material.
Failure modes
- Inventing delay days.
- Pasting Braintree batch indexes into NMI fields.
- Treating auth expires as settle delay.
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
- Settlement-delay days
- Settle day − Capture day.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Braintree settlement-delay days?
- Different gateway export. [Settlement-delay days](/manuals/braintree-settlement-delay-days) reads Braintree batches. Here you subtract NMI capture day from settle day on settled txs.
- Is this NMI auth-expire share?
- Sibling NMI door. [Auth-expire share](/manuals/nmi-auth-expire-share) is auths that died before capture. This page is capture-to-settle clock on settled txs.
- What delay days should I invent?
- None. Use capture day, settle day, and settled txs from the same NMI settle cut.