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 hold-lag exposure is not NMI hold-lag exposure

How to run thisPayments3 steps
CalculatorAuthorize.net auth-to-capture lag · Calculator lives in the articleOpen

Take the prior-auth $ still waiting on capture and the capture-wait hours on that same Authorize.net prior-auth float cut. The open pile is AN hold-lag $.

Pair: Auth-to-capture lag on Payments. NMI twin: capture-wait. Death twin: auth-expire.

What you type

Open auth $ — Authorize.net prior-auth dollars still uncaptured on the cut (AIM / CIM / Unsettled Transaction export).

Lag hours — Capture-wait hours from prior-auth to capture on that same cut.

AN hold-lag $ equals the prior-auth pile while capture still waits. Long capture-wait hours usually mean a capture map or batch cron lag — chase that Authorize.net seat; never invent an AN hold-lag chip.

What not to do

Do not invent AN hold-lag $. Do not load an NMI capture-wait CSV into Authorize.net prior-auth fields. Do not fold issuer partial-auth shorts or capture-fail counts into the float pile. Do not treat settled batch cash as prior-auth float.

Related: Payments, NMI capture-wait, auth-expire, partial-auth.

Procedure

  1. Type open auth $ and lag hours.
  2. Read AN hold-lag $.
  3. Tighten capture when lag hours are material.

Failure modes

  • Inventing AN hold-lag $.
  • Dumping an NMI auth-to-capture file into Authorize.net hold-lag fields.
  • Folding Authorize.net partial-auth or capture-fail 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

AN 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 the NMI capture-wait book?
Sibling gateway, different export. [NMI auth-to-capture lag](/manuals/nmi-auth-to-capture-lag) prices NMI open auth across lag. This door only prices Authorize.net prior-auth float against Authorize.net capture-wait hours.
Does a dead hold count here?
No — death grain lives under [auth-expire share](/manuals/authorize-net-auth-expire-share). Use this page while capture is still pending and the prior-auth pile is still live.
Can I invent AN hold-lag $?
No. Pull prior-auth $ and capture-wait hours from the same Authorize.net prior-auth float cut.