An AVS test is a check of how a payment gateway or processor handles Address Verification System responses. It confirms that the address and ZIP code data sent with a transaction produce the response codes and decline rules you expect. An AVS test does not verify a cardholder's identity; it validates your payment configuration.
What an AVS test actually checks
The Address Verification System compares the numeric portion of the billing street address and the ZIP code submitted at checkout against the records the card issuer holds. An AVS test focuses on the plumbing around that comparison rather than on the customer.
- The address and ZIP fields your checkout sends to the processor
- The response code the issuer returns, such as match, partial match, no match, or unavailable
- How your gateway maps those codes to approve, review, or decline outcomes
- Whether your rules behave the same way across card networks and countries
In practice, an AVS test is usually run with test credentials and processor-supplied test cards, so no real cardholder data is involved.
Why merchants run AVS tests
AVS results feed risk rules, so a misconfigured rule can approve bad orders or reject good ones. A structured test catches both problems before they reach production.
- Confirm that address fields are transmitted correctly and not dropped by a form or API
- Verify that each response code triggers the intended action in your fraud settings
- Check behavior for international cards, where AVS support varies by issuer and country
- Validate results after a gateway migration, plugin update, or checkout change
Common AVS response codes to test
Codes differ by network and processor, but most suites cover a core set of outcomes. Test each one your gateway exposes and record the resulting order status.
- Full match: street address and ZIP match issuer records
- Address match only: street matches, ZIP does not
- ZIP match only: ZIP matches, street does not
- No match: neither element matches
- Unavailable or unsupported: the issuer cannot or does not return a result
Also test partial and nine-digit ZIP variants if your gateway supports them, since they often carry different risk weights.
How to run an AVS test in a sandbox
- Get test API keys and test card numbers from your processor or gateway.
- Submit transactions with matching address and ZIP pairs, then with deliberate mismatches.
- Log the response code returned for each scenario alongside your rule outcome.
- Repeat with international addresses and with blank or malformed address fields.
- Review the results with your risk or compliance owner before enabling rules in production.
Limits and compliance notes
AVS covers billing address data only. It is one signal among several, and a passing result is not proof that a transaction is legitimate. Keep testing inside a sandbox and use only non-production card data. Any handling of real cardholder information must follow PCI DSS requirements, and your gateway's documentation is the authority on which response codes apply to your account.