Library · Payments · How to run this
Solidgate open-auth death is not Braintree auth expire
Put expired Solidgate auths over Solidgate auths in one settlement cut. The quotient is expire %.
Pair: Auth-expire share on Payments. Other gateway: Braintree auth-expire. Lag twin: auth-to-capture lag.
What you type
Auth expires — Solidgate open holds that died before capture in the cut.
Auths — Solidgate authorizations in that same cut.
Expire % = expired ÷ auths × 100. Fat expire % usually means capture lag past the hold window — chase that clock; never invent an expire chip.
What not to do
Do not invent expire %. Do not paste a Braintree or NMI expire file into Solidgate fields. Do not treat void fails as auth expires. Do not blend MIDs when one seat owns the dead holds.
Related: Payments, Braintree auth-expire, auth-to-capture lag, void-fail share.
Procedure
- Type auth expires and auths.
- Read expire %.
- Shorten capture lag when expire % is material.
Failure modes
- Inventing expire %.
- Pasting a Braintree or NMI expire file into Solidgate 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 Braintree auth-expire share?
- Different gateway book. [Auth-expire share](/manuals/braintree-auth-expire-share) reads Braintree. Here you only put Solidgate expired auths over Solidgate auths.
- Is this Solidgate auth-to-capture lag?
- Sibling Solidgate clock. [Auth-to-capture lag](/manuals/solidgate-auth-to-capture-lag) prices open auth $ across capture lag. This page is auths that died before capture.
- What expire % should I invent?
- None. Pull expired auths and auths from the same Solidgate settlement cut.