Library · Payments · How to run this
Authorize.net auth expire is not NMI auth expire
Auths expired before capture ÷ auths make expire %. Type both.
Pair: Auth-expire share on Payments. NMI: auth-expire share. Settle: settlement-reject share.
What you type
Auths expired before capture — Authorize.net authorizations that died before capture in the window.
Auths — Authorizations in that same Authorize.net window.
Expire % = auths expired before capture ÷ auths × 100. Shorten capture lag when expire % is fat. Do not invent an expire chip.
What not to do
Do not invent expire %. Do not paste NMI expire exports into Auth.net counts. Do not treat settlement rejects as auth expire. Do not blend MIDs when one owns the hole.
Related: Payments, auth-expire share, settlement-reject share, partial capture gap.
Procedure
- Type auths expired before capture and auths.
- Read expire %.
- Shorten capture lag when expire % is material.
Failure modes
- Inventing expire %.
- Pasting NMI expire exports into Auth.net counts.
- Treating settlement rejects as auth expire.
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 %
- Auths expired before capture ÷ auths × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this NMI auth-expire share?
- Sibling gateway grain. [Auth-expire share](/manuals/nmi-auth-expire-share) is NMI. This page is Authorize.net auths expired before capture ÷ auths.
- Is this settlement-reject share?
- Related Auth.net settle grain. [Settlement-reject share](/manuals/authorize-net-settlement-reject-share) is batch rejects. This page is Authorize.net auth-expire share.
- What expire % should I invent?
- None. Type auths expired before capture and auths from the same Authorize.net window.