Library · Payments · How to run this
Braintree auth expire is not Authorize.net auth expire
From one Braintree settlement cut, divide expired auths by auths. That ratio is expire %.
Pair: Auth-expire share on Payments. Other gateway: Authorize.net auth-expire. Void twin: void-fail share.
What you type
Auth expires — Braintree authorizations that died before capture in the cut.
Auths — Authorizations in that same Braintree cut.
Expire % = expired auths ÷ auths × 100. Fat expire % usually means capture lag — shorten that clock; never invent an expire chip.
What not to do
Never invent expire %. Never paste an Authorize.net expire file into Braintree fields. Never treat void fails as auth expires. Never blend MIDs when one seat owns the hole.
Related: Payments, Authorize.net auth-expire, NMI auth-expire, void-fail share.
Procedure
- Type auth expires and auths.
- Read expire %.
- Shorten capture lag when expire % is material.
Failure modes
- Inventing expire %.
- Dumping an Authorize.net expire file into Braintree 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 Authorize.net auth-expire share?
- Different gateway export. [Auth-expire share](/manuals/authorize-net-auth-expire-share) reads Authorize.net. Here you count Braintree expired auths over Braintree auths.
- Is this Braintree void-fail share?
- Sibling Braintree door. [Void-fail share](/manuals/braintree-void-fail-share) is voids that bounce. This page is auths that died before capture.
- What expire % should I invent?
- None. Use expired auths and auths from the same Braintree cut.