Library · Payments · How to run this
Spreedly vault-auth drop is not Primer hold timeout
Divide vault-auth drops by Spreedly auths in one vault cut. That ratio is drop %.
Pair: Auth-expire share on Payments. Primer twin: hold timeout. Void twin: void-fail share.
What you type
Auth expires — Spreedly vault auths that dropped before capture in the cut.
Auths — Spreedly authorizations in that same vault cut.
Drop % = vault-auth drops ÷ auths × 100. Fat drop % usually means capture lag past the vault hold — chase that clock; never invent a drop chip.
What not to do
Skip inventing drop %. Skip pasting a Primer or Solidgate expire file into Spreedly fields. Skip treating void fails as vault-auth drops. Skip blending MIDs when one seat owns the dead holds.
Related: Payments, hold timeout, void-fail share, vault-token fail.
Procedure
- Type auth expires and auths.
- Read expire %.
- Shorten capture lag when expire % is material.
Failure modes
- Inventing expire %.
- Pasting a Primer or Solidgate expire file into Spreedly fields.
- Treating void fails as auth expires.
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
- Auth-expire share %
- Auth expires ÷ Auths × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Primer auth-expire share?
- Different orchestration book. [Auth-expire share](/manuals/primer-auth-expire-share) reads Primer hold timeouts. Here you only divide Spreedly vault-auth drops by Spreedly auths.
- Is this Spreedly void-fail share?
- Sibling Spreedly door. [Void-fail share](/manuals/spreedly-void-fail-share) is voids that bounce. This page is vault auths that dropped before capture.
- What drop % should I invent?
- None. Pull vault-auth drops and auths from the same Spreedly vault cut.