Library · Payments · How to run this
Braintree settle-capture miss is not Spreedly capture fail
Divide settle-capture misses by capture attempts on one Braintree settle export. That ratio is settle-miss %.
Pair: Capture-fail share on Payments. Spreedly twin: capture-fail. Refund twin: refund-fail.
What you type
Capture fails — Braintree capture attempts that missed settle / failed in the export.
Capture attempts — Capture attempts in that same Braintree settle export.
Settle-miss % = settle-capture misses ÷ capture attempts × 100. Fat settle-miss % usually means processor decline or timeout on capture — chase that path; never invent a settle-miss chip.
What not to do
Skip inventing settle-miss %. Skip dumping a Spreedly capture file into Braintree fields. Skip folding refund fails into settle-capture misses. Skip blending MIDs when one seat owns the miss pile.
Related: Payments, capture-fail, refund-fail, void-fail.
Procedure
- Type capture fails and capture attempts.
- Read fail %.
- Chase processor path when fail % is material.
Failure modes
- Inventing fail %.
- Dumping a Spreedly capture file into Braintree fields.
- Folding refund fails into settle-capture misses.
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
- Capture-fail share %
- Capture fails ÷ Capture attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Spreedly capture-fail share?
- Different stack book. [Capture-fail share](/manuals/spreedly-capture-fail-share) reads Spreedly vault captures. Here you only divide Braintree settle-capture misses by capture attempts.
- Is this Braintree refund-fail share?
- Sibling Braintree door. [Refund-fail share](/manuals/braintree-refund-fail-share) is refund fails. This page is settle-capture misses ÷ capture attempts.
- What settle-miss % should I invent?
- None. Pull settle-capture misses and capture attempts from the same Braintree settle export.