Library · Payments · How to run this
Authorize.net void fail is not Braintree void fail
Open one Authorize.net cut. Put void fails over void attempts. That is the fail %.
Pair: Void-fail share on Payments. Braintree: void-fail share. Mix: void vs refund mix.
What you type
Void fails — Authorize.net void requests that returned fail / decline in the cut.
Void attempts — Void attempts in that same Authorize.net cut.
Fail % = void fails ÷ void attempts × 100. When fail % is fat, fix open-auth timing — never type a fake fail %.
What not to do
Skip inventing a fail %. Skip dumping a Braintree or NMI CSV into the Auth.net fields. Skip treating void-vs-refund mix as fail share. Skip blending MIDs when one MID owns the skew.
Related: Payments, void-fail share, void-fail share, void vs refund mix.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Fix open-auth timing when fail % is material.
Failure modes
- Inventing fail %.
- Dumping Braintree or NMI CSV into Auth.net fields.
- Treating void-vs-refund mix as 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 Braintree void-fail share?
- Different gateway export. [Void-fail share](/manuals/braintree-void-fail-share) reads Braintree. Here you type Authorize.net void fails over void attempts.
- Is this void vs refund mix?
- Related Auth.net count mix. [Void vs refund mix](/manuals/authorize-net-void-vs-refund-mix) is void vs refund counts. This page is void-fail share.
- What fail % should I invent?
- None. Pull void fails and void attempts from the same Authorize.net cut.