Library · Payments · How to run this
Void fail is not refund fail
Void fails ÷ void attempts make fail %. Type both.
Pair: Void-fail share on Payments. Refund: refund-fail share. Mix: void vs refund mix.
What you type
Void fails — Braintree voids that errored while the auth was still open.
Void attempts — Void calls in that same Braintree window.
Fail % = void fails ÷ void attempts × 100. Fix open-auth state or gateway when fail % is fat. Do not invent a fail chip.
What not to do
Do not invent fail %. Do not fold refund fails into void errors. Do not paste void-vs-refund mix onto fail %. Do not blend MIDs when one owns the hole.
Related: Payments, refund-fail share, void vs refund mix, capture-fail share.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Fix auth state / gateway when fail % is material.
Failure modes
- Inventing fail %.
- Mixing refund fails into void fails.
- Treating void-vs-refund mix as void-fail share.
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
- Void-fail share %
- Void fails ÷ void attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this refund-fail share?
- Sibling Braintree settle grain. [Refund-fail share](/manuals/braintree-refund-fail-share) is refund fails ÷ attempts. This page is void fails ÷ void attempts.
- Is this void vs refund mix?
- Count mix. [Void vs refund mix](/manuals/authorize-net-void-vs-refund-mix) is void vs refund counts. This page is Braintree void-fail share.
- What fail % should I invent?
- None. Type void fails and void attempts from the same Braintree export.