.svg)
.svg)
.svg)
.svg)
.svg)
The unified orchestration layer for wallets and alternative payments
.svg)
The secure repository for all your payment methods
.svg)
Workflow-driven payments intelligence for smarter routing and higher auth rates
.svg)
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
The visual workflow builder that ties fraud, identity, and payment routing together in one place
The unified orchestration layer for wallets and alternative payments
The secure repository for all your payment methods
Workflow-driven payments intelligence for smarter routing and higher auth rates
A flexible fraud and authentication layer. Instantly add advanced fraud tools and 3DS
One integration to sell inside ChatGPT, Gemini, and every agentic platform
The visual workflow builder that ties fraud, identity, and payment routing together in one place
AVS (Address Verification Service)
The Address Verification Service (AVS) is a fraud prevention tool used in card-not-present transactions that compares the billing address entered by the customer at checkout against the billing address on record with the issuing bank. When a merchant submits a transaction with billing address data, the issuer returns an AVS response code indicating the degree of match, full match, partial match (street number matches but zip code does not, or vice versa), or no match.
AVS was developed in the 1990s as one of the earliest card-not-present fraud prevention mechanisms. The logic is straightforward: a fraudster using a stolen card number may not know the cardholder's billing address. Requiring an address match adds a verification layer that pure card number knowledge cannot bypass. While AVS is not a comprehensive fraud solution on its own, it remains a widely used and commercially available signal in fraud scoring systems.
AVS is most established and consistently implemented in the United States, Canada, and the United Kingdom. International AVS support is inconsistent, many issuers in other markets do not participate in AVS, meaning international transactions frequently return "AVS unavailable" or "not supported" responses regardless of address accuracy. This limits AVS utility for merchants with significant international transaction volumes.
AVS response codes are returned alongside the authorization response and are used as one input in fraud decision logic. Common AVS responses include: "Y" (both street and zip match), "Z" (zip matches, street does not), "A" (street matches, zip does not), "N" (neither matches), "U" (issuer does not support AVS), and "E" (AVS error). Merchants configure their own policies for how to respond to each code, whether to accept, decline, or flag for review transactions with partial or no-match responses.
Frequently Asked Questions
How should merchants use AVS responses in their fraud logic?
AVS should be used as one signal in a broader fraud scoring approach rather than as a binary accept/decline trigger. A full AVS mismatch ("N") on a transaction from a new customer with a high-value order and an international IP address is a strong fraud signal. A partial mismatch ("Z", zip code incorrect) from a returning customer with a consistent order history may simply reflect a recently moved cardholder or a billing address formatting difference.
Does AVS failure prevent authorization?
No, AVS is a post-authorization check in most implementations. The authorization is requested and the issuer returns both the authorization response (approved or declined) and the AVS code as separate fields in the same response. The merchant receives an authorization and an AVS code and then decides, based on their own configured rules, whether to proceed with the transaction, void the authorization, or flag for review.
Is AVS still relevant in a world of 3DS2 and strong customer authentication?
AVS is less critical as a standalone fraud prevention mechanism in markets with strong 3DS2 / EMV 3-D Secure and SCA adoption, because 3DS2's rich data exchange and issuer authentication provide a much more sophisticated verification layer. However, AVS remains widely used for several reasons: it is lightweight and universally available in major English-language markets, it adds a signal at the authorization layer without adding checkout friction, and for merchants operating outside SCA-mandated markets (particularly in the US), it remains one of the more reliable fraud signals readily available in the transaction data stream.
Related Terms
