Card payment verification
AVS stands for Address Verification Service. It is a card-payment check that compares billing address information supplied during a transaction with information held by the card issuer. The issuer returns a result through the payment network and provider, usually indicating whether the street-address portion, postal code, both, or neither matched.
AVS is most useful as one input within a broader order-review process. A match does not prove that a customer is legitimate, and a mismatch does not prove fraud. Merchants should interpret the result together with the transaction context, their provider's available controls, and other relevant signals.
For an AVS check to occur, the checkout or keyed-payment workflow generally needs to collect supported billing address fields. The submitted address information travels with the authorization request. The issuer compares supported portions against its cardholder record and sends back a response rather than disclosing the address it has on file.
Official Authorize.net documentation explains that issuers typically focus on the numeric part of the street address and the postal code because spelling and address formatting can vary. Stripe's documentation likewise describes issuer checks of the postal code and billing street address when those fields are collected. The exact fields evaluated and the response presented to the merchant depend on the issuer, country, network, gateway, and processing configuration.
A response may indicate that both supported address elements matched or that only one element matched. A partial match can result from an outdated postal code, a formatting difference, or another ordinary customer-data issue, so it deserves context rather than an automatic conclusion.
A no-match result means the compared elements did not align with the issuer's record. It can be a useful reason to review an order, but legitimate customers can mistype an address or use information that has not yet been updated with the issuer.
Some results indicate that the check could not be performed, the issuer did not support it, or the needed data was not provided. AVS availability varies by issuer and country, so an unavailable result is not the same as a confirmed mismatch.
An AVS response and a card authorization answer are related pieces of a payment workflow, but they are not identical. Provider documentation may allow a merchant to accept, decline, or hold a transaction based on configured AVS rules. Those actions are provider-specific, and a merchant should verify what its own system supports before changing settings.
Overly strict handling can reject legitimate customers, while permissive handling can leave weak signals unreviewed. A sensible review process considers the AVS result alongside order value, customer history, delivery details, device or account signals, and other checks available in the merchant's approved payment setup. No single signal should be described as a guarantee.
Read the code definition supplied by the active gateway or processor. Similar-looking response labels can have provider-specific meanings, and a merchant should not apply a code table from an unrelated system.
Look for a mistyped house number, postal code, or recently changed billing address. If customer follow-up is appropriate, use normal business contact channels and do not ask for a complete card number, security code, password, bank credential, or secret key.
Consider the mismatch with the rest of the transaction and fulfillment context. Follow documented staff procedures for review, cancellation, or fulfillment rather than improvising a decision from AVS alone.
Track how AVS rules affect legitimate orders and suspicious activity over time. Review the provider's current settings and documentation before changing an automated action.
These questions help a business evaluate the workflow without assuming that every gateway, processor, issuer, or card type handles AVS the same way.
See practical steps for reducing ecommerce fraud across checkout, account, and fulfillment workflows.
Learn what account testing fraud is and how repeated low-value attempts can appear.
Use the guide to reducing credit card fraud as a starting point for layered controls.
Browse more fraud prevention and security FAQs for national merchant education.
If AVS results are unclear, start by documenting the codes shown by your current payment system and comparing them with that provider's current documentation. Then define who reviews mismatches, which additional order signals they use, and how customer follow-up protects sensitive information.
Payments Max can help merchants organize questions about payment workflows and evaluation criteria. Any feature availability or configuration decision must be confirmed with the merchant's actual provider and documented setup.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US
