Library · Payments · How to run this
Spreedly vaulted AVS refuse is not Primer routed AVS refuse
Divide vaulted AVS refuses by auth attempts on one Spreedly vault cut. That ratio is SP AVS-fail %.
Pair: AVS-fail share on Payments. Route twin: Primer AVS. Capture twin: capture-fail.
What you type
AVS fails — Spreedly auth attempts that failed AVS on the vaulted gateway in the cut.
Auth attempts — Auth attempts in that same Spreedly vault cut.
SP AVS-fail % = AVS fails ÷ auth attempts × 100. Fat SP AVS-fail % usually means vault AVS rule heat or bad bill-to on that gateway — retune that vault path; never invent an SP AVS-fail chip.
What not to do
Skip inventing SP AVS-fail %. Skip dumping a Primer, Authorize.net, or NMI AVS file into Spreedly fields. Skip folding capture fails or condition misses into AVS refuses. Skip blending vaults when one gateway owns the refuse pile.
Related: Payments, Primer AVS, Authorize.net AVS, capture-fail.
Procedure
- Type AVS fails and auth attempts.
- Read SP AVS-fail %.
- Retune vault AVS rules when SP AVS-fail % is material.
Failure modes
- Inventing SP AVS-fail %.
- Dumping a Primer, Authorize.net, or NMI AVS file into Spreedly fields.
- Folding capture fails into AVS refuses.
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 AVS-fail %
- AVS fails ÷ Auth attempts × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Primer AVS-fail share?
- Routed processor vs Spreedly vault. [AVS-fail share](/manuals/primer-avs-fail-share) reads Primer. Here you only divide Spreedly vaulted AVS refuses by auth attempts.
- Is this Spreedly capture-fail share?
- Capture bounce vs AVS refuse. [Capture-fail share](/manuals/spreedly-capture-fail-share) is capture fails ÷ attempts. This page is AVS refuses ÷ auth attempts.
- What SP AVS-fail % should I invent?
- None. Pull AVS fails and auth attempts from the same Spreedly vault cut.