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