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