AVS (Address Verification Service)

AVS exists because a stolen card number rarely comes with the cardholder’s correct billing address. In a card-not-present transaction, the merchant submits the numeric parts of the billing address (street number and ZIP code) with the authorization. The issuer compares them against its records and returns a response code alongside the approval: full match (typically code Y), ZIP-only match (Z), street-only match (A), no match (N), or unavailable (U, common for non-US issuers).

How merchants use it

AVS does not approve or decline anything by itself; the authorization can be approved even when the address fails to match. The merchant (or its gateway rules) decides what to do with the code: many merchants auto-void approved transactions that return a full mismatch, hold partial matches for review on high-ticket orders, and pass full matches through. AVS results also matter after the fact: a full AVS match is standard evidence in chargeback representment, and some interchange categories for keyed transactions require an AVS check to qualify for the better rate.

Its limits are real. AVS checks only numeric fields, it is largely a US, UK, and Canada tool, and a fraudster who has the victim’s full identity will pass it. That is why it is one layer in a stack, used alongside CVV checks, velocity rules, and 3-D Secure rather than instead of them.

Why it matters

When evaluating a processor, check that AVS codes are returned in full through the API, that rules can act on them automatically, and that AVS data flows into dispute evidence without manual work.

QorPay’s QorCommerce API returns complete AVS and CVV response codes on every transaction, documented for rule-building and dispute evidence.