Library · Payments · How to run this
Braintree held-batch share is not auth-to-capture lag
BT held-batch % = held settlements ÷ settlements × 100 on one Braintree hold cut.
Pair: Settlement-hold share on Payments. Auth twin: auth-to-capture. Argyle twin: ACH held-batch.
What you type
Held settlements — Braintree settlement batches still parked before merchant payout in the cut.
Settlements — Settlement batches in that same Braintree hold cut.
BT held-batch % = held ÷ settlements × 100. Fat BT held-batch % usually means risk / reserve rules are biting the rail — chase that release path; never invent a BT held-batch chip.
What not to do
Skip inventing BT held-batch %. Skip dumping auth-to-capture indexes into share fields. Skip treating refund fails as held batches. Skip blending MIDs when one seat owns the parked pile.
Related: Payments, auth-to-capture, Argyle ACH held-batch, refund-fail.
Procedure
- Type held settlements and settlements.
- Read BT held-batch %.
- Chase release when BT held-batch % is material.
Failure modes
- Inventing BT held-batch %.
- Dumping an Argyle/Spreedly held-batch file or Braintree auth-to-capture index into hold fields.
- Folding Braintree refund-fail share or batch-reject into held-batch counts.
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 held-batch %
- Held settlements ÷ Settlements × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Braintree auth-to-capture lag?
- Clock grain. [Auth-to-capture lag](/manuals/braintree-auth-to-capture-lag) prices auth day vs capture day. This page only divides held batches by settlement batches.
- Is this Argyle settlement-hold share?
- Different processor ledger. [Argyle settlement-hold share](/manuals/argyle-settlement-hold-share) reads Argyle ACH holds. Here you only score Braintree held batches.
- What BT held-batch % should I invent?
- None. Pull held settlements and settlements from the same Braintree hold cut.