An AVS test checks whether the billing address a customer enters matches the address the card issuer has on file. The payment gateway sends the street number and ZIP code to the issuer, which replies with a single-letter response code. Merchants run AVS tests to confirm their checkout handles every code correctly before real orders arrive.
What does AVS test mean in payments?
AVS stands for Address Verification System, a fraud tool built into the card networks. It compares two fields from the checkout form, the numeric street address and the ZIP or postal code, against bank records. An AVS test is the practice of sending sample transactions through a gateway to see which codes come back and how the system reacts to each one.
AVS does not verify a cardholder's identity and does not replace CVV checks. It only flags whether the address data lines up.
How does an AVS check work?
- The customer enters a billing address at checkout.
- The gateway formats the street number and ZIP into the authorization request.
- The issuer compares them to the address on file and returns a letter code.
- Your rules engine approves, flags, or declines the order based on that code.
The whole exchange happens inside the normal authorization, so it adds no extra step for the buyer.
What are the common AVS response codes?
- Y: street address and 5-digit ZIP both match.
- X: exact match on street address and all 9 ZIP digits.
- A: street address matches, ZIP does not.
- Z: ZIP matches, street address does not.
- W: 9-digit ZIP matches, street address does not.
- N: neither field matches.
- U: address data is unavailable at the issuer.
- G: card issued outside AVS-supported countries.
- S: the issuer does not support AVS.
- R: the system asks you to retry.
- E: an error occurred in the AVS lookup.
Codes A, Z, and W are partial matches and usually deserve a manual review rather than an automatic decline.
How do merchants run an AVS test?
Every major gateway publishes a sandbox with test card values that force specific AVS responses. You pair those values with matching or mismatched addresses and confirm your code routes each result to the right outcome. Document the expected response for each combination so future developers can regression-test the rules.
What are the limits of AVS testing?
AVS is only reliable for cards issued in the United States, Canada, and the United Kingdom, and issuers elsewhere often return G or S. Some banks store address data inconsistently, so a legitimate customer can still return N. Treat AVS as one signal among several, alongside CVV validation, velocity checks, and device fingerprinting.
Is it legal to test AVS with real card numbers?
You may test with your own cards or with the sandbox credentials your processor provides. Running address checks against card data you do not own or have written permission to use is a crime in most jurisdictions, regardless of whether the transaction settles. Test environments exist precisely so live card data never needs to be used for integration work.
Do AVS tests affect authorization rates?
No. An AVS lookup rides along with the authorization request, so it does not create an additional charge or decline on its own. Your own rules decide whether a mismatch blocks the sale, and overly strict rules are a common cause of false declines.