AVS — how a billing address declines a working card
Last updated · Reviewed quarterly
The most frustrating decline of all: a valid card, funded, not expired, refused with a message that says nothing — because a postcode did not match what your bank has on file. Address Verification is the check nobody tells you about and the easiest of the three card failures to fix, once you know it is what happened.
Key takeaways
- AVS compares the billing address you type against the one your card issuer holds. It is not checking whether the address is real.
- A postcode mismatch alone is enough to decline at merchants that require a full match, and the error message will not say so.
- Many countries have no postcodes at all, which produces partial matches that stricter merchants reject.
- Inventing a US address makes it worse, not better — it guarantees the mismatch you were trying to avoid.
What is actually being compared
When you type a billing address at checkout, it is sent to your card issuer, which compares it against the address on your account and returns a result: full match, partial match, no match, or unavailable. The merchant then decides what to accept.
Two things follow from that, and both surprise people. AVS is not validating that your address exists — a perfectly real address that differs from your bank’s records fails. And the decision to refuse is the merchant’s, not the bank’s: the issuer only reports the comparison. Two merchants can receive the same result and one approves while the other declines.
Why it fails when your address is correct
- The postcode differs by formatting. A space, a hyphen or a missing letter is a mismatch to a string comparison.
- Your bank holds an old address. People move and update the delivery address they use for shopping, not the one on a card account opened years ago.
- The bank stores an abbreviation you did not use, or the reverse — Street against St, Apartment against Apt.
- Your country has no postcodes, so there is nothing to match on and the result comes back partial.
- The name on the account differs from what you typed, which some checks include.
- You are entering a delivery address out of habit rather than the billing address on the card.
The fourth point is the one that disproportionately affects the audience for this site. Where postcodes do not exist or are not used in practice, no entry produces a full match — and a merchant configured to require one will refuse every attempt no matter what is typed.
Fixing it, in order
- Find your card’s billing address as your bank has it — on a statement, or in the card details section of your banking app. Do not type it from memory.
- Copy it exactly, including the formatting of the postcode and any abbreviations the bank uses.
- Retry once. If the previous failure was AVS, this usually resolves it outright.
- If your country has no postcode, try the placeholder your bank stores. Many use 00000, some use the city name, and support can tell you which.
- If it still fails, update the address held by your card issuer rather than experimenting further at the checkout. Once that is done, the address you type can finally match.
- Give it a few minutes between attempts, and change one thing at a time so you know what worked.
Telling AVS apart from the other two card failures
| Symptom | AVS mismatch | BIN refusal | 3-D Secure failure |
|---|---|---|---|
| Error message | Generic decline | Generic decline | Usually none — it hangs |
| Speed | Immediate | Immediate | Hangs, then times out |
| Same card elsewhere | Often works | Usually works | Varies |
| Effect of correcting the address | Fixes it | None | None |
| Effect of adding balance | None | None | None |
| Worth retrying | Yes, once corrected | No | Yes, carefully |
The fourth row is the whole diagnosis. AVS is the only one of the three that a change you can make yourself, in thirty seconds, will resolve — which is why it is worth ruling out before assuming the card is unusable.
When the address is not the problem
If a corrected, statement-copied address still fails identically, AVS is not what is happening. At that point the likely causes are a card-range refusal, an issuer block on international or online transactions, or a country restriction — none of which any address will fix.
That is the point to stop editing form fields and change route. A payment rail with no card in it — an app store balance funded locally, or a gift subscription bought on somebody else’s ordinary card — has no address to verify and therefore nothing to mismatch.
Address corrected and still refused? A gift code has no billing address in the transaction at all.
See plans and pricesFrequently asked questions
What does AVS mean on a card payment?
Address Verification Service — a check that compares the billing address you enter against the one your card issuer holds on the account. It returns a match, partial match or mismatch, and the merchant decides what to accept. It is not checking whether the address exists, only whether the two records agree.
Can a wrong postcode alone decline my card?
Yes, at merchants configured to require a full match, and the error you see will be a generic decline with no mention of the address. A formatting difference is enough — a space, a hyphen, or a missing character all read as a mismatch to a string comparison.
What billing address do I use if my country has no postcodes?
Use whatever placeholder your card issuer has stored, which is commonly 00000 or the city name. Your bank can tell you exactly what is on the account. Without a postcode no entry produces a full match, so a merchant requiring one will refuse every attempt regardless of what you type.
Should I enter a US address to make a payment work?
No — it makes refusal more likely. AVS compares your entry against your bank’s records, so a fabricated address guarantees a mismatch. A foreign-issued card presented with a domestic billing address is also a recognised fraud pattern, so you are adding a second reason to decline rather than removing one.
How do I know whether my decline is AVS or something else?
Correct the address from your bank statement and retry once. If it goes through, it was AVS. If it fails identically, it is not — a card-range refusal, an international-transaction block or a country restriction are the likely causes, and no address will fix any of them.
Sources
Primary sources where one exists. All links checked on publication; if one has rotted or the rule has changed, tell us and we will fix it.
- [1]Stripe decline codes — StripeSupports: That address and postcode verification failures are reported as their own decline reasons, distinct from balance, authentication and card-type refusals.
Related guides
- Claude Pro Card Declined — Why It Happens and How to Fix ItWhy claude.ai declines your card — issuer blocks, prepaid BINs, 3-D Secure, country restrictions — and what actually fixes each one in 2026.
- What a card BIN is, and why it gets your card declinedThe first six to eight digits of a card number. It is why a funded virtual card fails instantly, why retrying never helps, and why support cannot help.
- What 3-D Secure is, and why it fails without telling youThe verification step between your bank and a checkout. When it breaks it produces no error at all — the page just hangs. Why, and how to get through it.
- Buy Claude Pro with an app store gift cardPay for Claude Pro with an App Store or Google Play gift card bought for cash locally — no bank card, no crypto, at or near list price, and it renews.