Direct Answer
Address Verification Service (AVS) sends the billing address a buyer gives at checkout inside the card authorization request and asks the issuer whether it matches the address held for that cardholder. The issuer returns a result code in the authorization response. Visa’s rules let a merchant use AVS in the card-absent environment; in the regions named in Visa’s issuer rule an issuer must verify the postal code, may optionally verify the street address, and supply a match result code. Approval and matching are separate: an approved payment can still carry a failed address check.
Source: Visa, “Visa Core Rules and Visa Product and Service Rules” (§10.11.1.1; §10.11.1.2 for the AP, Canada, Europe, LAC and US Regions only; ed. 18 April 2026); Stripe, “Fraud prevention rules” (Stripe Radar’s AVS rule), accessed 2026-09-04.
What AVS actually compares
AVS is an address-matching question attached to a card authorization, not a separate transaction. The billing address travels with the authorization request, and the issuer answers with a result code carried back in the response. Visa’s rules permit a merchant to use AVS for a transaction in the card-absent environment. In the regions named in Visa’s issuer requirement, an issuer must participate in AVS, verify the postal code (or country equivalent) where postal codes are in use, optionally verify the street address, and provide a result code in the authorization response.
Source: Visa, “Visa Core Rules and Visa Product and Service Rules” (§10.11.1.1 “Address Verification Service (AVS) Eligible Transactions” and §10.11.1.2 “Address Verification Service (AVS) Issuer Requirements – AP, Canada, Europe, LAC, and US Regions”, the second applying to those named regions only, edition 18 April 2026), accessed 2026-09-04.
The result code is a signal, not the authorization decision
Matching and approval are decided by different logic. Stripe states that a payment can still succeed when the address (AVS) check fails, because issuers evaluate numerous risk factors, and it offers an optional rule to block payments that fail postal-code verification unless Stripe scores them low risk. Adyen runs its AVS rules after authorization, which is why an Adyen AVS rule cannot be linked to its Dynamic 3D Secure feature; Adyen separately lists a refusal reason, AVS Declined, for address data entered incorrectly. Those are two providers’ designs, not one industry mechanism — write down which system in your own stack makes the final call.
Source: Stripe, “Fraud prevention rules” (Stripe Radar’s CVC/AVS and 3DS rule behaviour); Adyen, “Address Verification System (AVS)” (Adyen’s AVS implementation, coverage limits and response-code mapping); Adyen, “Refusal reasons” (Adyen’s refusal-reason list), accessed 2026-09-04.
Read the response before you write a rule
Response you may see | What the provider documentation says | Check before you act on it |
|---|---|---|
Postal code and address both match | Adyen folds raw codes A, D, F, M, X and Y into one “both match” value, with different per-scheme meanings behind it | Whether the address that matched is also the address you shipped to |
Postal code matches, address does not | Adyen maps raw T, W and Z here; the digits compared differ by scheme and by whether the address is inside the US | Whether your rule assumes five-digit or nine-digit postal data |
Neither matches | Adyen maps raw N for Visa, Mastercard, Discover and American Express | Whether the issuer approved anyway, and who owns the decision to keep or cancel the order |
AVS unavailable | Adyen maps raw R, S and U here, and has a separate value for card types it does not cover | That you are not penalising issuers or card types that never perform the check |
No AVS data provided | Adyen reports a distinct value here, and an unknown value when no answer came back from the issuing bank | That your checkout actually collected and forwarded a billing address |
Source: Adyen, “Address Verification System (AVS)” (Adyen’s AVS implementation, coverage limits and response-code mapping), accessed 2026-09-04.
Coverage is uneven, so scope the rule to the market
Adyen documents AVS for card payments with Visa, Mastercard, Discover or American Express, and states that issuers in the United States, Canada, the United Kingdom and Europe (Visa only) must support AVS verification requests, while in other countries or regions this is not the case; using AVS stays optional for the merchant. Visa’s AVS acquirer requirement is written for the Europe and US Regions. Stripe adds that the impact of data such as the full billing address might vary by card brand and country. A threshold tuned on US traffic should not be assumed to hold elsewhere.
Source: Adyen, “Address Verification System (AVS)” (Adyen’s AVS implementation, coverage limits and response-code mapping); Visa, “Visa Core Rules and Visa Product and Service Rules” (§10.11.1.5 “Address Verification Service (AVS) Acquirer Requirements – Europe and US Regions” — those two regions only, edition 18 April 2026); Stripe, “Card declines” (Stripe’s decline-handling guidance), accessed 2026-09-04.
Send clean data, then keep the evidence
Adyen’s API requires country, city, street, house number or name and postal code in the billing address object, with state or province required for US and Canadian shoppers even though AVS does not validate that field; postal code is capped at five digits for a US address and ten characters elsewhere. Visa’s acquirer rule for the Europe and US Regions, marked effective 25 July 2026, requires AVS data in authorization and account-verification requests to contain genuine cardholder address data obtained directly from the cardholder — padding the field to lift match rates is not an option. In the Canada Region, Visa requires a participating acquirer to carry the AVS result code into the clearing record.
- Store the raw acquirer response as well as your provider’s mapped code; Adyen returns both in its live environment once the acquirer-result fields are switched on.
- Keep the address exactly as it was submitted, including country and postal code.
- Record which rule acted on the result and who is allowed to override it.
- Keep the authorization reference so the AVS result can be tied to a later dispute.
- Re-check field and coverage requirements before opening a new market.
Source: Adyen, “Address Verification System (AVS)” (Adyen’s AVS implementation, coverage limits and response-code mapping); Visa, “Visa Core Rules and Visa Product and Service Rules” (§10.11.1.5 “Address Verification Service (AVS) Acquirer Requirements – Europe and US Regions” and §10.11.1.3 “Address Verification Service (AVS) Results Code Population – Canada Region”, each limited to the regions named in its title, edition 18 April 2026), accessed 2026-09-04.
Where AVS sits next to CVV and 3DS
AVS compares address data; it does not establish who is holding the card. EMVCo describes EMV 3-D Secure as authentication of consumers to prevent card-not-present fraud, and Stripe notes that when 3DS authenticates a payment, liability for fraud-related disputes typically shifts from the seller to the issuer. AVS results carry weight in narrower places: Visa’s invalid-dispute rules name an airline or passenger-railway transaction where the issuer’s AVS response was Y and tickets were mailed to the cardholder billing address on file — among entries that each carry their own country and region qualifiers.
Source: EMVCo, “EMV 3-D Secure” (EMVCo’s description of EMV 3DS); Stripe, “Fraud prevention rules” (Stripe Radar’s CVC/AVS and 3DS rule behaviour); Visa, “Visa Core Rules and Visa Product and Service Rules” (§11.7.5.3 “Dispute Condition 10.4: Other Fraud – Card-Absent Environment – Invalid Disputes”, whose entries carry their own country and region qualifiers, edition 18 April 2026), accessed 2026-09-04.
Read Card Verification Value (CVV) and 3-D Secure (3DS) for the neighbouring checks, payment authorization for the message the result rides on, issuing bank for who answers the inquiry, merchant acquirer for who passes it through, and chargeback for where the record is used later.
Editorial note: AI-assisted educational content prepared for HaiPay. It is not investment, legal or tax advice. The cited sources explain the concepts; your provider agreement and applicable rules govern your arrangement.
FAQ
No. AVS reports whether address data matched, not who used the card. Stripe states that a payment can still succeed when the address check fails, because issuers evaluate numerous risk factors, so a match and an approval are independent outcomes. Visa’s rules do give an AVS result evidentiary weight, but only in narrow situations — for instance an invalid-dispute entry covering airline or passenger-railway transactions where the issuer’s AVS response was Y and tickets went to the billing address on file. Outside those named cases, treat AVS as one signal among several.
Source: Stripe, “Fraud prevention rules” (Stripe Radar’s CVC/AVS and 3DS rule behaviour); Visa, “Visa Core Rules and Visa Product and Service Rules” (§11.7.5.3 “Dispute Condition 10.4: Other Fraud – Card-Absent Environment – Invalid Disputes”, whose entries carry their own country and region qualifiers, edition 18 April 2026), accessed 2026-09-04.
Sources
Related terms
Card scheme basics
Card Verification Value (CVV)
Card Verification Value (CVV) is the three- or four-digit security code printed on a payment card, used to verify that the customer likely possesses the physical or virtual card during checkout.
Card scheme basics
3-D Secure (3DS)
3-D Secure (3DS) is a cardholder authentication protocol that adds a step-up challenge during online checkout so issuers can confirm the payer before authorizing high-risk transactions.
Acquiring and settlement
Payment Authorization
Payment authorization checks whether a card transaction is approved by the cardholder’s issuing institution or a service acting for it before funds can later be captured.
Acquiring and settlement
Issuing Bank
An issuing bank provides payment cards to customers and manages the accounts used for those cards throughout authorization, clearing, and settlement.
Acquiring and settlement
Merchant Acquirer
A merchant acquirer is a payment service provider that contracts with businesses to accept and process card payments on behalf of participating card networks.
Risk and compliance
Chargeback
A chargeback is a forced reversal of a card transaction initiated by the cardholder through their issuer, usually citing fraud, non-delivery, or billing disputes, and debited from the merchant through the acquirer.
Usage Guide
Read GuidePayment Roles
Merchant Acquiring Explained: Acquirer vs Processor vs Acquiring Bank vs PayFac
Need help mapping your payment stack?
Accept major card networks with routing, 3DS, and settlement built for cross-border sales.
Contact Us