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

Primer orchestration hold float is not Authorize.net prior-auth float

How to run thisPayments3 steps
CalculatorPrimer auth-to-capture lag · Calculator lives in the articleOpen

PR hold-lag $ is the uncaptured orchestration pile on one Primer capture-workflow cut. Type that pile and the capture-wait hours beside it.

Pair: Auth-to-capture lag on Payments. Authorize.net twin: prior-auth float. Death twin: auth-expire.

What you type

Open auth $ — Dollars Primer authorized that the capture workflow has not yet posted (orchestration / processor export).

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

PR hold-lag $ equals the uncaptured orchestration pile. Long capture-wait hours usually mean a Primer workflow or processor map lag — chase that orchestration seat; never invent a PR hold-lag chip.

What not to do

Do not invent PR hold-lag $. Do not paste an Authorize.net AIM/CIM prior-auth file or an NMI capture-wait CSV into Primer capture-workflow fields. Do not fold partial-auth shorts or batch-reject counts into the uncaptured pile. Do not treat settled batch cash as orchestration float.

Related: Payments, Authorize.net prior-auth float, auth-expire, partial-auth.

Procedure

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

Failure modes

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

PR 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 Authorize.net prior-auth float?
Different processor book. [Authorize.net auth-to-capture lag](/manuals/authorize-net-auth-to-capture-lag) prices AIM/CIM prior-auth dollars. This door only scores Primer’s uncaptured orchestration pile.
Is a timed-out Primer auth the same metric?
No. [Auth-expire share](/manuals/primer-auth-expire-share) is expired holds ÷ auths. Keep this page for dollars still waiting on capture workflow.
Can I invent PR hold-lag $?
No. Pull the uncaptured orchestration pile and capture-wait hours from the same Primer capture-workflow cut.