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-short is not Braintree vault hold-short

How to run thisPayments3 steps
CalculatorArgyle partial-auth gap · Calculator lives in the articleOpen

Ask $ minus approved hold $, then ÷ ask $, makes AG hold-short % on one Argyle pay-rail window.

Pair: Partial-auth gap on Payments. Vault twin: Braintree hold-short. Lag twin: auth-to-capture.

What you type

Requested auth $ — Cart dollars Argyle sent as the pay-rail ask.

Partial auth $ — Dollars the issuer parked on that same pay-rail window.

AG hold-short % = (ask − approved) ÷ ask × 100. Wide AG hold-short % usually means issuer or cart rules on that rail — chase that path; never invent an AG hold-short chip.

What not to do

Skip inventing AG hold-short %. Skip pouring a Braintree vault or NMI partial-auth export into Argyle fields. Skip treating capture lag hours as a first-hold short. Skip blending rails when one pay-rail owns the short pile.

Related: Payments, Braintree hold-short, auth-to-capture, void-fail.

Procedure

  1. Type requested auth $ and partial auth $.
  2. Read gap $ and AG hold-short %.
  3. Chase issuer / cart rules when AG hold-short % is material.

Failure modes

  • Inventing AG hold-short %.
  • Dumping a Braintree or NMI partial-auth file into Argyle ask / hold fields.
  • Treating a later capture lag as a first-hold short.

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 hold-short %
(Requested auth $ − Partial auth $) ÷ Requested auth $ × 100.

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

FAQ

Is this Braintree partial-auth gap?
Vault book vs pay-rail book. [Partial-auth gap](/manuals/braintree-partial-auth-gap) stays on Braintree. Ask / hold dollars never leave Argyle here.
Is this Argyle auth-to-capture lag?
Open float vs first-hold short. [Auth-to-capture lag](/manuals/argyle-auth-to-capture-lag) prices open auth $ across lag hours. Here you score ask minus approved hold.
What AG hold-short % should I invent?
None. Enter ask $ and approved hold $ from the same Argyle pay-rail export.