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

Braintree gateway-hold float is not Spreedly vault-hold float

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

On one Braintree gateway-hold cut, type open auth $ and lag hours. The tool surfaces BT gateway-hold $ — the open auth float still waiting on capture.

Pair: Auth-to-capture lag on Payments. Spreedly twin: vault-hold. Death twin: auth-expire.

What you type

Open auth $ — Authorized dollars still uncaptured on the Braintree gateway cut.

Lag hours — Hours from auth to capture (or to the cut clock) for that same Braintree gateway-hold window.

BT gateway-hold $ mirrors open auth $ while lag hours name how long the float sits. Fat lag hours usually mean capture workflow lag — chase that queue; never invent a BT gateway-hold chip.

What not to do

Do not invent BT gateway-hold $. Do not load a Spreedly vault-hold or SeamlessChex ACH-hold file into Braintree gateway-hold fields. Do not fold auth-expire or partial-auth into capture-lag exposure. Do not blend gateways when one owns the open pile.

Related: Payments, Spreedly vault-hold, auth-expire, partial-auth.

Procedure

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

Failure modes

  • Inventing BT gateway-hold $.
  • Dumping a Spreedly vault-hold or SeamlessChex ACH-hold file into Braintree gateway-hold fields.
  • Folding Braintree auth-expire or partial-auth into capture-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

BT gateway-hold $
Open auth $ still waiting on Braintree capture across the typed lag hours.

Work with us — We run this job on your accounts. Services

FAQ

Is this Spreedly auth-to-capture lag?
Different hold book. [Auth-to-capture lag](/manuals/spreedly-auth-to-capture-lag) reads Spreedly vault-hold $. Here you only score Braintree gateway open auth $ across lag hours.
Is this Braintree auth-expire share?
Death grain, not lag float. [Auth-expire share](/manuals/braintree-auth-expire-share) is auth expires ÷ auths. This page is open auth $ still waiting on capture.
What BT gateway-hold $ should I invent?
None. Pull open auth $ and lag hours from the same Braintree gateway-hold cut.