Library · Payments · How to run this
SeamlessChex void fail is not Primer void fail
From one SeamlessChex settlement cut, divide void fails by void attempts. That ratio is fail %.
Pair: Void-fail share on Payments. Other stack: Primer void-fail. Hold twin: settlement-hold days.
What you type
Void fails — SeamlessChex void requests that bounced in the cut.
Void attempts — Void requests in that same SeamlessChex cut.
Fail % = void fails ÷ void attempts × 100. Fat fail % usually means open-auth / cutoff timing — chase that path; never invent a fail chip.
What not to do
Never invent fail %. Never paste a Primer or Braintree void file into SeamlessChex fields. Never treat ACH return-code lag as void fail. Never blend MIDs when one seat owns the bounce.
Related: Payments, Primer void-fail, Braintree void-fail, settlement-hold days.
Procedure
- Type void fails and void attempts.
- Read fail %.
- Chase open-auth / cutoff timing when fail % is material.
Failure modes
- Inventing fail %.
- Pasting a Primer or Braintree void file into SeamlessChex fields.
- Treating ACH return-code lag as void fail.
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 Primer void-fail share?
- Different orchestration export. [Void-fail share](/manuals/primer-void-fail-share) reads Primer. Here you count SeamlessChex void fails over SeamlessChex void attempts.
- Is this settlement-hold days?
- Sibling SeamlessChex clock. [Settlement-hold days](/manuals/seamless-settlement-hold-days) is hold start to release. This page is voids that bounce.
- What fail % should I invent?
- None. Use void fails and void attempts from the same SeamlessChex cut.