Library · Payments · How to run this
Spreedly void fail is not Solidgate void fail
Tally rejected voids against void calls in one Spreedly gateway cut. That tally is fail %.
Pair: Void-fail share on Payments. Other gateway: Solidgate void-fail. Capture sibling: capture-fail share.
What you type
Void fails — Spreedly void / reverse calls that returned reject in the cut.
Void attempts — All void calls in that same Spreedly cut.
Fail % = rejected voids ÷ void calls × 100. A fat fail % usually means the auth already settled or the vault token died — chase those paths; never invent a fail chip.
What not to do
Skip inventing fail %. Skip dumping Solidgate or Auth.net void logs into Spreedly fields. Skip counting capture rejects as void rejects. Skip mixing gateways when one MID owns the bounce.
Related: Payments, Solidgate void-fail, capture-fail share, vault-token fail.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Fix open-auth timing when fail % is material.
Failure modes
- Inventing fail %.
- Dumping Solidgate or Authorize.net CSV into Spreedly fields.
- Treating capture fails 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 Solidgate void-fail share?
- Solidgate keeps its own gateway export. [Void-fail share](/manuals/solidgate-void-fail-share) is that file. This page tallies Spreedly rejected voids only.
- Is this Spreedly capture-fail share?
- Capture fails hit when you try to capture. [Capture-fail share](/manuals/spreedly-capture-fail-share) is that door. This page is voids that bounce on an open auth.
- What fail % should I invent?
- None. Tally rejected voids and void calls from the same Spreedly gateway cut.