Library · Payments · How to run this
Primer void fail is not Spreedly void fail
Count bounced voids against void calls in one Primer orchestration window. Bounced ÷ calls is fail %.
Pair: Void-fail share on Payments. Vault hop: Spreedly void-fail. Rule twin: condition-miss rate.
What you type
Void fails — Primer void / reverse steps that bounced in the window.
Void attempts — Every void step Primer ran in that same window.
Fail % = bounced voids ÷ void calls × 100. A fat fail % usually means the auth settled early or the workflow timed out — chase those steps; never invent a fail chip.
What not to do
Skip inventing fail %. Skip dumping Spreedly void logs into Primer inputs. Skip counting retry successes as bounced voids. Skip mixing processors when one MID owns the bounce.
Related: Payments, Spreedly void-fail, condition-miss rate, retry-success share.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Fix open-auth / workflow timing when fail % is material.
Failure modes
- Inventing fail %.
- Dumping Spreedly or Solidgate CSV into Primer fields.
- Treating retry successes 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 Spreedly void-fail share?
- Spreedly is a vault / gateway hop. [Void-fail share](/manuals/spreedly-void-fail-share) is that hop. This page counts bounced voids inside Primer orchestration only.
- Is this Primer condition-miss rate?
- Condition misses are routing rules that did not fire. [Condition-miss rate](/manuals/primer-condition-miss-rate) is that door. This page is void calls that bounced.
- What fail % should I invent?
- None. Count bounced voids and void calls from the same Primer orchestration window.