Library · Payments · How to run this
Capture fail is not refund fail
Capture fails ÷ capture attempts make fail %. Type both.
Pair: Capture-fail share on Payments. Refund: refund-fail share. Partial: partial capture gap.
What you type
Capture fails — Spreedly capture attempts that failed in the window.
Capture attempts — Capture attempts in that same Spreedly window.
Fail % = capture fails ÷ capture attempts × 100. Fix gateway / vault when fail % is fat — do not invent a fail chip.
What not to do
Do not invent fail %. Do not mix refund fails into capture fails. Do not treat partial-capture gaps as capture fails. Do not average every MID when one owns the hole.
Related: Payments, refund-fail share, partial capture gap, auth-to-capture lag.
Procedure
- Type capture fails and capture attempts.
- Read fail %.
- Fix gateway / vault when fail % is material.
Failure modes
- Inventing fail %.
- Mixing refund fails into capture fails.
- Treating partial-capture gaps as capture fails.
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
- Capture-fail share %
- Capture fails ÷ capture attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this refund-fail share?
- Sibling settle grain. [Refund-fail share](/manuals/braintree-refund-fail-share) is refund fails \u00f7 refund attempts. This page is Spreedly capture-fail share.
- Is this partial capture gap?
- Related capture book. [Partial capture gap](/manuals/authorize-net-partial-capture-gap) is captured $ vs authorized $. This page is capture fails \u00f7 attempts.
- What fail % should I invent?
- None. Type capture fails and capture attempts from the same Spreedly window.