Address Verification Service (AVS) is a fraud prevention mechanism that reduces fraud and chargebacks. The service verifies if the card issuer recognizes the address provided by a cardholder. The results of the verification will help you determine whether to accept or decline a particular transaction or take further action. AVS is effective to both reduce fraud and reduce chargebacks.

Use Cases

• Customer Onboarding and Account Opening: You use AVS to confirm the address details provided by new customers when opening accounts on your platform.
• Saving Cards on Your Platform: You want to ensure all saved cards used on your platform will have low chargeback rates by using AVS when a customer adds a new card.
• e-Commerce: You want to verify the billing address for saved cards and guest checkouts to check against the issuer's records to reduce your chargebacks.

Why Choose AVS?

AVS was designed to reduce fraud in the Card Not Present (CNP) environment, where a possession of physical card alone isn't sufficient to conduct an e-commerce transaction.

While AVS certainly detects obvious mismatches in address information, it is not a guaranteed fraud prevention tool. TabaPay suggests utilizing a variety of fraud detection tools in conjunction with AVS to identify and prevent fraud.

AVS Workflow

1. Your customer onboards on to your platform, and adds a card, and address information.
2. You send Query Card with query parameter AVS to TabaPay.
3. TabaPay sends card and address information to the issuer.
4. Issuer returns with address verification response codes.
5. TabaPay returns the Query Card response with an AVS Response Code.
6. You present the relevant information to your customer.

How AVS works

1. Request your consumer’s to provide cardholder billing data - Street Address and ZIP Code, and send this address to us using the Query Card API.
2. This information will be forwarded to the card issuer - Issuers validate key elements of the address, and match the values received against the values they have received from their customer (the cardholder).
3. TabaPay will provide you the results of the Address Verification. Based on the result, you can determine if you want the consumer to proceed further in the transaction or not. It is recommended to proceed with the transaction in the case of a full or partial match. When there is no match, the transaction request should be terminated.

1. Query Card Request

The Query Card request includes the query parameter, ?AVS.

https: //FQDN/v1/clients/ClientID/cards?AVS'

Query Card Response

{
    "SC": 200,
    "EC": "0",
    "card": {
        "pull": {
            "enabled": true,
            "network": "IntlMasterCard",
            "type": "Debit",
            "regulated": false,
            "currency": "840",
            "country": "124"
        },
        "push": {
            "enabled": false
        },
        "bin": "850584",
        "last4": "9998"
    },
    "AVS": {  
        "avsID": "eNvalYDkRcY9EujXLx6tIa",
        "networkRC": "05",
        "networkID": "2024082323004167000",
        "authorizeID": "230041",
        "resultText": "DECLINE",
        "codeAVS": "A",
        "ANI": {
            "codeMatch": "U"
        }
    }
}

The response includes the AVS object, which contains avsID, networkRC, networkID, authorizeID, resultText, codeAVS, and ANI.

Recipes

More Resources

• AVS Response Codes
• AVS with Card Query