Library · Payment orchestration · How to run this
AVS retry is not AVS fail share
AVS-driven retries ÷ all retries make share %. Type both.
Pair: AVS retry share on Orchestration. Fail share: AVS fail share. Partial: partial auth gap.
What you type
AVS-driven retries — retry attempts whose prior fail was AVS mismatch.
All retries — retry attempts in that same window.
Share % = AVS-driven retries ÷ all retries × 100. Fix AVS rules when share % is fat — do not invent a share chip.
What not to do
Do not invent share %. Do not mix soft-decline buckets into AVS retries. Do not treat first-try AVS fails as retries. Do not average every MID when one owns the hole.
Related: Orchestration, AVS fail share, partial auth gap, retry cost waterfall, AVS/CVV tradeoff.
Procedure
- Type AVS-driven retries and all retries.
- Read share %.
- Fix AVS rules when share % is material.
Failure modes
- Inventing share %.
- Mixing soft-decline buckets into AVS retries.
- Treating first-try AVS fails as retries.
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
- AVS retry share %
- AVS-driven retries ÷ all retries × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this AVS fail share?
- Sibling AVS grain. [AVS fail share](/manuals/solidgate-avs-fail-share) is AVS fails ÷ auths. This page is AVS-driven retries ÷ all retries on NMI.
- Is this partial auth gap?
- Related NMI door. [Partial auth gap](/manuals/nmi-partial-auth-gap) is issuer partial vs requested auth. This page is AVS retry share.
- What share % should I invent?
- None. Type AVS-driven retries and all retries from the same NMI window.