← Back to all articles

AVS (Address Verification System): How Payment Processors Validate Your Address

Every time you pay by card online, the checkout may silently ask one extra question behind the scenes: does the billing address you typed match the one the card issuer has on file? That question is answered by the Address Verification System (AVS), a fraud filter that has been part of card-not-present payments for decades.

How AVS actually works

When a transaction is authorized, the processor sends the numeric parts of the billing address — typically the street number and the ZIP or postal code — to the issuing bank. The bank compares them against its own records and returns a single-letter code. Common results include Y (address and ZIP both match), Z (ZIP matches, address does not), N (neither matches) and U (unavailable). Each letter is a hint, not a verdict.

Critically, AVS only checks the numbers. Apartment numbers and full street names are usually ignored, which is why a mismatch is not automatically a sign of fraud and a match is not proof of identity.

Why legitimate orders get declined

A mismatch does not hard-block a payment by itself; the merchant's risk rules decide what to do with it. That is why a cardholder who just moved, or who entered "Main St" while the bank has "Main Street", can still see a perfectly good card declined. Merchants that treat AVS too aggressively lose real revenue, while those that ignore it absorb chargebacks.

What this means for testing

If you build or test checkout flows, you need addresses that look real and match realistic formats. A generated address with a coherent street number, city and postal code is far more useful for QA than a placeholder like "123 Test Street", because it exercises the same AVS fields a real transaction would.