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

Argyle pay-rail-hold float is not Braintree gateway-hold float

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

Open auth $ on an Argyle pay-rail-hold cut stays uncaptured across lag hours. AG pay-rail-hold $ mirrors that open auth float while lag hours name the wait.

Pair: Auth-to-capture lag on Payments. Gateway twin: Braintree hold. Expire twin: auth-expire.

What you type

Open auth $ — Authorized dollars still uncaptured on the Argyle pay-rail cut.

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

AG pay-rail-hold $ = open auth $ while lag hours name duration. Wide lag hours usually mean capture queue delay on that rail — chase that workflow; never invent an AG pay-rail-hold chip.

What not to do

Skip inventing AG pay-rail-hold $. Skip pouring a Braintree gateway-hold or SeamlessChex ACH-hold export into Argyle fields. Skip folding auth-expire % or void-fail counts into capture-lag exposure. Skip blending rails when one pay-rail owns the open pile.

Related: Payments, Braintree hold, auth-expire, void-fail.

Procedure

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

Failure modes

  • Inventing AG pay-rail-hold $.
  • Dumping a Braintree gateway-hold or SeamlessChex ACH-hold file into Argyle fields.
  • Folding auth-expire or void-fail 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

AG pay-rail-hold $
Open auth $ still waiting on Argyle capture across the typed lag hours.

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

FAQ

Is this Braintree auth-to-capture lag?
Gateway-hold vs pay-rail-hold. [Auth-to-capture lag](/manuals/braintree-auth-to-capture-lag) prices Braintree open auth $. Here both fields stay on one Argyle pay-rail-hold cut.
Is this Argyle auth-expire share?
Expire % vs open float. [Auth-expire share](/manuals/argyle-auth-expire-share) is auth expires ÷ auths. This page prices open auth $ still waiting on capture.
What AG pay-rail-hold $ should I invent?
None. Enter open auth $ and lag hours from the same Argyle pay-rail-hold export.