Library · Payments · How to run this
Solidgate hard kills are not soft retries
On one Solidgate decline file, put hard codes over all codes. That ratio × 100 is SG hard-decline %. Enter both counts.
Pair: Hard-decline share on Payments. Soft twin family: Argyle soft. Reject twin: settlement reject.
Inputs
Hard declines — Issuer hard / terminal codes on Solidgate in the window.
All declines — Soft + hard decline codes in that same Solidgate export.
SG hard-decline % = hard ÷ all × 100. When SG hard-decline % runs tall, cut hard burns and widen soft retry elsewhere — leave blank chips alone.
Hard stops
Leave SG hard-decline % blank rather than invent. Keep soft-only counts out of the hard pile. Keep settlement-reject rows out of decline boxes. Keep one Solidgate MID per run when that seat owns the mix.
Related: Payments, Argyle soft, settlement reject, AVS fail.
Procedure
- Type hard declines and all declines.
- Read SG hard-decline %.
- Cut hard burns when SG hard-decline % is material.
Failure modes
- Inventing SG hard-decline %.
- Loading soft-only counts into the hard pile.
- Folding settlement-reject rows into decline boxes.
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 hard-decline %
- Hard declines ÷ all declines × 100 on one Solidgate decline export.
Work with us — We run this job on your accounts. Services
FAQ
- Is this a soft-decline share page?
- Hard / terminal pile vs soft retry pile. Soft-decline pages stay on soft codes. Here you only score hard declines over all declines on Solidgate.
- Is this Solidgate settlement reject share?
- Settle-die batches vs issuer hard codes. [Settlement reject](/manuals/solidgate-settlement-reject-share) stays on batch rejects. This page is hard declines ÷ all declines.
- What SG hard-decline % should I invent?
- None. Source hard declines and all declines from the same Solidgate decline file.