Documentation
API ReferenceRecipesChangelogCommunity
Start typing to search…

Address Verification Service (AVS)

Protect against fraudulent transactions. Available worldwide.

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.

Benefits

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.

📘

Using ANI with AVS

Clients are encouraged to grab the avsID from the Query Card API response, and use it in the Create Transaction API request. This would not verify users again during the transaction, but would help track and monitor efficacy of both AVS and ANI on processing.

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.

Request

The example includes the Query Parameter, ?AVS.

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

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.

📘

Numeric Verification Only

Only the numerical portion of the address is verified by the issuer during an AVS check. Typically, only the house number and ZIP/postal code are compared.

When the issuer is unable to match the values exactly, AVS code that indicates 'how' the address verification failed is returned. For example: AVS code of A indicates that the address matches (again, numeric portion of the address) but the ZIP code doesn’t match.

Recipes


More Resources

Updated 4 days ago

What’s Next