Library · Payments · How to run this
Refund-fail share is not void vs refund mix
Refund fails ÷ refund attempts make fail %. Type both.
Pair: Refund-fail share on Payments. Void book: void vs refund mix. Auth clock: auth expiry reauth.
What you type
Refund fails — Braintree refund requests that failed / were declined in the window.
Refund attempts — Refund requests submitted in that same window.
Fail % = refund fails ÷ refund attempts × 100. Fix token / settle state when fail % is fat — do not invent a fail chip.
What not to do
Do not invent fail %. Do not mix voids into refund fails. Do not treat auth-expiry reauths as refund fails. Do not blend every MID when one owns the hole.
Related: Payments, void vs refund mix, auth expiry reauth, auth vs settle gap.
Procedure
- Type refund fails and refund attempts.
- Read fail %.
- Fix token / settle state when fail % is material.
Failure modes
- Inventing fail %.
- Mixing voids into refund fails.
- Treating auth-expiry reauths as refund 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
- Refund-fail share %
- Refund fails ÷ refund attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this void vs refund mix?
- Sibling cash door. [Void vs refund mix](/manuals/authorize-net-void-vs-refund-mix) is void count vs refund count. This page is Braintree refund fails ÷ refund attempts.
- Is this auth vs settle gap?
- Related settle book. [Auth vs settle gap](/manuals/argyle-auth-vs-settle-gap) is auth $ vs settled $. This page is refund-fail share.
- What fail % should I invent?
- None. Type refund fails and refund attempts from the same Braintree window.