Library · Payments · How to run this
Solidgate refund reject mix is not Primer refund miss
On one Solidgate refund export, ratio refund fails to refund attempts. That mix is SG refund-fail %.
Pair: Refund-fail share on Payments. Primer twin: PR refund-fail. Capture twin: sg-capture miss.
Refund-export fields
Refund fails — Solidgate refund posts that rejected / failed in the export.
Refund attempts — Refund posts submitted in that same Solidgate refund export.
SG refund-fail % = refund fails ÷ refund attempts × 100. Fat SG refund-fail % usually means token / settle state on refund — chase that path; never invent an SG refund-fail chip.
Guardrails
Do not invent SG refund-fail %. Do not dump Primer or Braintree refund rows into Solidgate boxes. Do not fold capture misses into refund fails. Do not blend MIDs when one seat owns the reject pile.
Related: Payments, PR refund-fail, sg-capture miss, settlement-reject.
Procedure
- Type refund fails and refund attempts.
- Read SG refund-fail %.
- Chase token / settle state when SG refund-fail % is fat.
Failure modes
- Inventing SG refund-fail %.
- Loading Primer refund rows into Solidgate boxes.
- Folding capture misses into refund 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
- SG refund-fail %
- Refund fails ÷ refund attempts × 100 on one Solidgate settle export.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Primer refund-fail share?
- Solidgate refund export vs Primer settle route. [Refund-fail share](/manuals/primer-refund-fail-share) stays on Primer. Refund rejects / posts never leave Solidgate here.
- Is this Solidgate capture-fail share?
- Refund rejects vs capture misses. [Capture-fail share](/manuals/solidgate-capture-fail-share) ratios capture fails. This page ratios refund rejects ÷ refund posts.
- What SG refund-fail % should I invent?
- None. Pull refund fails and refund attempts from the same Solidgate refund export.