If you prefer to receive the actual response code from the card or network, you can turn these on in your Customer Area: We also have a number of Adyen AVS response codes to accommodate acquirers that send in slightly different raw AVS responses.įor the mapping of AVS results for point-of-sale MOTO transactions with AVS, refer to AVS responses for point of sale. Many of them are mapped to the response codes that you receive from Adyen. AVS responses and mappingĭifferent card brands and networks have specific AVS response codes. In your custom rule, for the field avsResponseCode, you can use the Adyen response values from the mapping table to define the risk rule behavior. You can use and configure the standard consistency risk rule Billing address does not match cardholder address (AVS).Īlternatively, you can configure custom risk rules using AVS responses. This table shows AVS response codes returned by Adyen, which are mapped to raw AVS response codes from acquirers.
You can choose to have the HPPs pre-populate the billing address information from your own system, as shown below:
You must turn it on for each skin to apply AVS.įor a list of parameters required for this call, refer to HPP billing address and AVS fields.
Provide the child element stateOrProvince as defined in ISO 3166-2. Required for for shoppers from the UK, US or Canada. The country value format needs to adhere to the ISO 3166-1 alpha-2 standard. An invalid country code results in a transaction/request rejection. You can look up country codes on the ISO website.Ī maximum of five digits for an address in the US, or a maximum of ten characters for an address in all other countries. When you submit the billingAddress object for AVS, the following child elements are required:.
Provide the full address of the shopper using the billingAddress child element: Send the collected billing address information in the payment authorisation request. Classic integration: Make sure that you collect the shopper's billing address details to include them in the /authorise request.
If you're using a client-side integration for Web, the Web Drop-in and Card Component can be configured to collect your shopper's billing address.
Credit card issuers in the United States, Canada, and the United Kingdom must support AVS verification requests when you send them in, however, using AVS is not mandatory for you as a merchant. Based on the AVS response, you can decide what to do with the payment: you can accept, make an exception, or cancel a transaction.ĪVS is supported for card payments with Visa, Mastercard, Discover or American Express. You can use the standard risk rule Billing address does not match cardholder address, or you can create a custom risk rule.
When the AVS check results in a mismatch, you can trigger a risk rule. You can see the mapping in the mapping table.
The response to the payment request will contain an Adyen AVS response code that is mapped to a raw AVS response code. When you have enabled AVS, the system checks if and to what extent these billing address details match the information that the issuing bank has on file about the holder of the credit card. Then, you send that data in the billingAddress object in the payment authorisation request. When a shopper pays for a transaction, you can collect their billing address details. AVS is a widely used fraud-prevention measure for Card Not Present (CNP) transactions, such as online payments or point-of-sale Mail Order/Telephone Order (MOTO) payments.ĪVS gives you a way to check if the shopper who is placing the order is the same person as the cardholder, which is more likely if the billing address details match. The Address Verification System (AVS) is a service that verifies if a billing address matches the address of a credit card cardholder.