The Address Verification System (AVS) is a fraud prevention tool used in credit and debit card transactions to verify that the billing address provided by the customer matches the address on file with the card-issuing bank. AVS is primarily used for card not present (CNP) transactions—such as online, phone, and mail orders—where the merchant cannot physically verify the card or the cardholder’s identity. In 2026, AVS remains one of the most widely used fraud prevention tools in payment processing, though it is most effective when used in combination with other verification methods.
How AVS Works
During a card not present transaction, the customer enters their billing address along with their card information. When the merchant submits the transaction for authorization, the payment gateway sends the billing address data to the card network, which forwards it to the issuing bank. The issuing bank compares the numeric portions of the street address and the ZIP code provided by the customer against the address on file for the cardholder’s account. The bank then returns an AVS response code indicating the degree of match.
Common AVS response codes include a full match (both the street address and ZIP code match), a partial match (either the street address or ZIP code matches but not both), and no match (neither matches). There are also codes for cases where AVS data is unavailable, the issuing bank does not support AVS, or the card is from a country that does not participate in AVS. The merchant then uses these response codes to make a decision about whether to accept, review, or decline the transaction.
Why AVS Matters for Merchants
AVS serves two important purposes for merchants. First, it helps reduce fraud by flagging transactions where the billing address provided does not match the cardholder’s records, which is a common indicator of stolen card data being used by an unauthorized person. Second, AVS responses can affect the interchange rate a merchant pays on a transaction. Many interchange categories require an AVS match for the transaction to qualify for the lowest rate. If AVS data is not submitted or does not match, the transaction may be downgraded to a higher interchange category, resulting in higher processing costs.
AVS is also relevant to chargeback disputes. When a merchant can demonstrate that a transaction had a full AVS match, it provides supporting evidence that the transaction was legitimate, which can strengthen the merchant’s case when fighting a chargeback. Conversely, processing a transaction with a no-match AVS response weakens the merchant’s position in a dispute.
Limitations of AVS
While AVS is a valuable tool, it has important limitations that merchants should understand. AVS only checks the numeric portions of the address—it does not verify the cardholder’s name, apartment numbers in text form, or any other non-numeric address elements. This means that minor formatting differences, typos in the street name, or PO Box addresses can sometimes produce mismatches even when the cardholder is legitimate. AVS also has limited effectiveness for international transactions, as many countries outside the United States, Canada, and the United Kingdom do not fully support the system.
In 2026, AVS works best as one layer in a multi-layered fraud prevention strategy. Merchants should combine AVS with CVV verification, 3D Secure authentication, device fingerprinting, velocity checks, and AI-powered fraud scoring to build a comprehensive approach to transaction security. Relying solely on AVS is insufficient given the sophistication of modern fraud techniques, but excluding it from your fraud prevention toolkit means missing a simple, low-cost verification step that can catch many fraudulent transactions before they are completed.
Configuring AVS for Your Business
Most payment gateways and processors allow merchants to configure AVS settings to automatically approve, flag for review, or decline transactions based on the AVS response code. The right configuration depends on your business model and risk tolerance. An overly strict AVS policy—declining all transactions without a full match—may reject legitimate orders from customers who have recently moved or who have address formatting differences. An overly lenient policy—accepting all transactions regardless of AVS response—increases fraud exposure. Finding the right balance requires analyzing your transaction data, understanding your customer base, and adjusting your AVS rules over time based on actual fraud and chargeback patterns.