AVS is one of the older fraud-prevention tools in the card-not-present stack and one of the most consistently misunderstood. AVS — Address Verification Service — matches the cardholder billing address (or just the numeric portion of it) against the issuer-side record at the moment of the transaction. It returns a match code that the merchant uses to decide whether to accept the transaction. Used properly, caribbean avs verification screens out a meaningful share of CNP fraud. Used wrongly, it rejects legitimate transactions and drives merchant-side false-decline costs that exceed the fraud it was meant to prevent.
This piece walks through how AVS actually works, what the match codes mean, where it fits in the broader Caribbean CNP fraud stack, and where its limitations matter.
How caribbean avs verification works mechanically
At the moment of a CNP transaction, the merchant collects two pieces of cardholder information beyond the card details: the numeric portion of the billing address (street number) and the postal code (or postal-code equivalent in the issuer country). These are sent through the authorization request along with the card details.
The issuer receives the authorization request, matches the submitted address details against the address on file for the cardholder, and returns a match code in the authorization response. The match codes vary across networks but typically look like: full match (street and postal both match), partial match (one of the two matched), no match (neither matched), unable to verify (issuer cannot run the check), or service not supported (issuer or merchant country does not support AVS for this card type).
The merchant decision based on the match code is then up to the merchant rules. A common default: accept full matches, accept partial matches with caution, decline no-matches. Caribbean AVS verification is one input to the merchant fraud screening decision, not the sole input.
Where it works well in Caribbean CNP
AVS is particularly useful at catching one specific fraud pattern: a stolen card number used without the actual card. The fraudster has the card details (often from a data breach or skimmer compromise) but does not have the cardholder billing address. AVS catches this because the fraudster cannot guess the address. The match code returns no-match, the merchant declines, the fraud attempt fails.
For Caribbean merchants accepting US-issued cards on CNP transactions, caribbean avs verification works reliably because the US issuer-side AVS infrastructure is mature and the address-on-file records are accurate. The match rate on legitimate transactions is around 92-95%. The catch rate on stolen-card attempts is around 75-85%.
Where it falls short
The Caribbean has structural complications that make AVS less reliable than in the US.
Caribbean-issued cards often have addresses on file that do not match standard US-style street-and-postal formats. Many Caribbean residential addresses do not have street numbers (rural addresses, district-style addressing, or P.O. box addresses are common). The numeric portion of the address that AVS expects to match often does not exist on the issuer-side record.
Caribbean postal codes are inconsistent. Some islands have postal codes implemented (Jamaica, Trinidad, Barbados have standardized postal codes). Others do not (parts of the Eastern Caribbean still operate without consistent postal coding). AVS on a card issued in a non-postal-code jurisdiction returns service-not-supported regardless of whether the submitted address is correct.
Visiting customers from non-AVS-supporting countries trigger service-not-supported responses. A French-issued card spending on a Caribbean merchant site returns no AVS data because France does not participate in the AVS network. The merchant has to decide how to handle these transactions through other fraud signals.
What caribbean avs verification looks like on a typical Caribbean merchant book
For a Caribbean merchant with 30% Caribbean-issued cards, 50% US-issued cards, and 20% European/other cards, the AVS distribution typically looks like:
- US-issued cards: 85% full match, 8% partial match, 3% no match, 4% other
- Caribbean-issued cards: 35% full match, 15% partial match, 12% no match, 38% service not supported
- European/other cards: 10% any match data, 90% service not supported or unable to verify
For US-issued card traffic, AVS provides clear fraud signal. For Caribbean-issued and European-issued cards, AVS is mostly silent. The merchant has to rely on other fraud signals — 3DS authentication, device fingerprinting, velocity rules, BIN analysis — to fill the gap.
Tuning the merchant decision rules
AVS works best when the merchant decision rules are tuned per card-issuer region rather than applied uniformly. A common tuning:
- US-issued cards: decline no-match, accept partial match with secondary fraud check, accept full match.
- Caribbean-issued cards: do not decline based on AVS alone, weight AVS as a secondary signal among 3DS and velocity rules.
- European/other cards: ignore AVS, rely on 3DS as the primary CNP fraud signal.
This tuning captures the AVS value where it works (US-issued cards), avoids the false-decline cost where it does not work (Caribbean and European cards), and shifts the fraud-screening burden to better-fitting tools in those regions.
Talk to our team on WhatsApp →
Where caribbean avs verification fits in the broader fraud stack
AVS is one piece. The full Caribbean CNP fraud stack typically combines: AVS for issuer-side address validation, 3DS for cardholder authentication, device fingerprinting for repeat-attacker recognition, velocity rules for high-frequency attack detection, BIN-level signals for known-bad-issuer ranges, and processor-level fraud scoring (like Sentinel) for the integrated risk decision.
AVS contributes one signal to that stack. It is most useful as a confirming signal when other signals are ambiguous, and as a primary signal when the card is US-issued. It is least useful as a standalone gate on Caribbean-issued or European-issued traffic, where it produces too many false declines for the fraud it catches.
The merchants who use caribbean avs verification well treat it as one input to a tuned decision rule, not as a binary accept-or-reject gate. The ones who use it badly run uniform rules across all traffic and absorb either the fraud they did not catch or the false declines they did not need.