Library · Payments · How to run this
Solidgate void fail is not Authorize.net void fail
From one Solidgate export, divide failed voids by void tries. That ratio is fail %.
Pair: Void-fail share on Payments. Processor twins: Authorize.net void-fail, Braintree void-fail.
What you type
Void fails — Solidgate reverse / void calls that returned fail in the export.
Void attempts — Every void call in that same Solidgate export.
Fail % = failed voids ÷ void tries × 100. High fail % usually means the auth already settled or timed out — chase that path; do not invent a fail chip.
What not to do
Never invent fail %. Never paste an Authorize.net or Braintree void file into Solidgate fields. Never count soft declines as void fails. Never mix MIDs when one seat owns the bounce.
Related: Payments, Authorize.net void-fail, Braintree void-fail, NMI void-fail.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Fix open-auth timing when fail % is material.
Failure modes
- Inventing fail %.
- Dumping Authorize.net or Braintree CSV into Solidgate fields.
- Treating soft declines as void 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
- Void-fail share %
- Void fails ÷ void attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Authorize.net void-fail share?
- Different processor file. [Void-fail share](/manuals/authorize-net-void-fail-share) is Authorize.net. This page only reads Solidgate void fails over void tries.
- Is this soft-decline share?
- Soft declines hit at auth. Void-fail share hits when you try to reverse an open auth. Different clock.
- What fail % should I invent?
- None. Use failed voids and void tries from the same Solidgate export.