Library · Payment orchestration · How to run this
Soft decline is not cascade fail
Soft decline codes ÷ all decline codes make soft %. Type both.
Pair: Soft-decline share on Orchestration. Hop: cascade fail share. Cost: retry cost waterfall.
What you type
Soft declines — Issuer soft codes on Solidgate in the window (retry-eligible).
All declines — Soft + hard decline codes in that same Solidgate export.
Soft % = soft declines ÷ all declines × 100. Widen soft retry / cut hard burns when soft % is fat. Do not invent a soft chip.
What not to do
Do not invent soft %. Do not fold cascade hop fails into soft codes. Do not paste Sticky rebill soft onto a Solidgate MID. Do not blend processors when one MID owns the mix.
Related: Orchestration, cascade fail share, retry cost waterfall, rebill soft-decline share.
Procedure
- Type soft declines and all declines.
- Read soft %.
- Tune retry / cascade when soft % is material.
Failure modes
- Inventing soft %.
- Mixing cascade fails into soft declines.
- Treating Sticky rebill soft as Solidgate soft share.
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
- Soft-decline share %
- Soft declines ÷ all declines × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this cascade fail share?
- Sibling Solidgate hop. [Cascade fail share](/manuals/solidgate-cascade-fail-share) is hops that die. This page is soft codes ÷ all decline codes.
- Is this rebill soft-decline share?
- CRM soft mix. [Rebill soft-decline share](/manuals/sticky-rebill-soft-decline-share) is Sticky rebill soft. This page is Solidgate gateway soft-decline share.
- What soft % should I invent?
- None. Type soft declines and all declines from the same Solidgate export.