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

Spreedly vault-hold float is not SeamlessChex ACH-hold float

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

SP vault-hold $ is the vault open pile on one Spreedly vault-capture cut. Type that pile and the capture-wait hours beside it.

Pair: Auth-to-capture lag on Payments. SeamlessChex twin: ACH-hold. Death twin: auth-expire.

What you type

Open auth $ — Spreedly vault-authorized dollars still uncaptured on the cut (vault / processor export).

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

SP vault-hold $ equals the vault open pile. Long capture-wait hours usually mean a vault capture map lag — chase that Spreedly seat; never invent an SP vault-hold chip.

What not to do

Do not invent SP vault-hold $. Do not paste a SeamlessChex ACH-capture or Primer workflow-float CSV into Spreedly vault-capture fields. Do not fold issuer partial-auth shorts or auth-expire counts into the vault open pile. Do not treat settled batch cash as vault capture wait.

Related: Payments, SeamlessChex ACH-hold, auth-expire, partial-auth.

Procedure

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

Failure modes

  • Inventing SP vault-hold $.
  • Dumping a SeamlessChex or Primer auth-to-capture file into Spreedly vault-hold fields.
  • Folding Spreedly partial-auth or auth-expire into vault-hold 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

SP vault-hold $
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 SeamlessChex ACH capture wait?
Different processor book. [SeamlessChex auth-to-capture lag](/manuals/seamless-auth-to-capture-lag) prices ACH / eCheck open dollars. This door only scores Spreedly vault open dollars against Spreedly capture-wait hours.
Is a dead vault hold the same metric?
No. [Auth-expire share](/manuals/spreedly-auth-expire-share) is vault-auth drops ÷ auths. Keep this page for dollars still waiting on vault capture.
Can I invent SP vault-hold $?
No. Pull the vault open pile and capture-wait hours from the same Spreedly vault-capture cut.