Library · Payments · How to run this
Spreedly vault soft share is not a gateway soft share
Soft decline codes ÷ all decline codes on one Spreedly vault file make SP soft-decline %. Type both.
Pair: Soft-decline share on Payments. Workflow twin: Primer soft. Processor twin: Auth.net soft. Vault twin: partial auth gap.
Vault counts
Soft declines — Issuer soft / retryable codes on Spreedly tokens in the window.
All declines — Soft + hard decline codes in that same Spreedly vault export.
SP soft-decline % = soft ÷ all × 100. Widen soft retry / cut hard burns when SP soft-decline % is fat. Do not invent an SP soft-decline chip.
Do not
Invent no SP soft-decline %. Fold no settle-die rejects into soft codes. Paste no Primer or Auth.net decline rows onto a Spreedly vault MID. Blend no processors when one Spreedly seat owns the mix.
Related: Payments, Primer soft, Auth.net soft, partial auth gap.
Procedure
- Type soft declines and all declines.
- Read SP soft-decline %.
- Seat retry / updater when SP soft-decline % is material.
Failure modes
- Inventing SP soft-decline %.
- Loading Primer or Braintree decline rows into Spreedly inputs.
- Folding settle-reject counts into soft.
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
- SP soft-decline %
- Soft declines ÷ all declines × 100 on one Spreedly decline export.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Primer soft-decline share?
- Vault book vs Primer workflow. [Soft-decline share](/manuals/primer-soft-decline-share) stays on Primer. Soft / all counts never leave Spreedly here.
- Is this Authorize.net soft-decline share?
- Separate processor stack. [Soft-decline share](/manuals/authorize-net-soft-decline-share) stays on Authorize.net. Spreedly owns every count here.
- What SP soft-decline % should I invent?
- None. Source soft declines and all declines from the same Spreedly decline file.