Library · Payments · How to run this
NMI hold-lag exposure is not Solidgate hold-lag exposure
Price open auth $ across typed lag hours on one NMI hold-lag window. That open pile is NM hold-lag $.
Pair: Auth-to-capture lag on Payments. Solidgate twin: hold-lag. Death twin: auth-expire.
What you type
Open auth $ — NMI authorized dollars not yet captured in the window.
Lag hours — Hours from auth to capture on that same NMI hold-lag window.
NM hold-lag $ = open auth $ (exposure while capture lags). Fat lag hours usually mean capture map lag — chase that seat; never invent an NM hold-lag chip.
What not to do
Never invent NM hold-lag $. Never paste a Solidgate auth-to-capture file into NMI hold-lag fields. Never fold partial-auth or auth-expire counts into hold-lag exposure. Never mix settled $ into open auth.
Related: Payments, Solidgate hold-lag, auth-expire, partial-auth.
Procedure
- Type open auth $ and lag hours.
- Read NM hold-lag $.
- Tighten capture when lag hours are material.
Failure modes
- Inventing NM hold-lag $.
- Dumping a Solidgate auth-to-capture file into NMI hold-lag fields.
- Folding NMI partial-auth or auth-expire into hold-lag exposure.
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 hold-lag $
- Open auth $ held across typed auth-to-capture lag hours (exposure $ = open auth $).
Work with us — We run this job on your accounts. Services
FAQ
- Is this Solidgate auth-to-capture lag?
- Different gateway book. [Auth-to-capture lag](/manuals/solidgate-auth-to-capture-lag) prices Solidgate open auth across lag. Here you only price NMI open auth $ across NMI lag hours.
- Is this NMI auth-expire share?
- Hold death, not lag exposure. [Auth-expire share](/manuals/nmi-auth-expire-share) is auths expired before capture ÷ auths. This page is open auth $ while capture still lags.
- What NM hold-lag $ should I invent?
- None. Type open auth $ and lag hours from the same NMI hold-lag window.