Library · Payments · How to run this
Partial capture is not partial auth
(Authorized $ − captured $) ÷ authorized $ make capture gap %. Type both.
Pair: Partial capture gap on Payments. Amount: capture vs auth amount. Issuer: partial auth gap.
What you type
Captured $ — dollars captured against the holds in that window.
Authorized $ — dollars authorized (held) in that same window.
Capture gap % = (authorized $ − captured $) ÷ authorized $ × 100. Fix capture rules when gap % is fat — do not invent a gap chip.
What not to do
Do not invent capture gap %. Do not mix voids into captured $. Do not treat auth-to-capture lag hours as gap %. Do not average every MID when one owns the hole.
Related: Payments, capture vs auth amount, partial auth gap, void vs refund mix, auth-to-capture lag.
Procedure
- Type captured $ and authorized $.
- Read capture gap %.
- Fix capture rules when gap % is material.
Failure modes
- Inventing capture gap %.
- Mixing voids into captured $.
- Treating auth-to-capture lag hours as gap %.
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
- Partial capture gap %
- (Authorized $ − captured $) ÷ authorized $ × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this capture vs auth amount?
- Sibling amount door. [Capture vs auth amount](/manuals/capture-vs-auth-amount) names match / leftover / overcapture. This page is (authorized − captured) ÷ authorized on Authorize.net.
- Is this partial auth gap?
- Related issuer grain. [Partial auth gap](/manuals/nmi-partial-auth-gap) is issuer partial vs requested auth. This page is partial capture gap.
- What capture gap % should I invent?
- None. Type captured $ and authorized $ from the same Authorize.net window.