Address verification service

In this how-to guide, you will find information how to manage and operate the Address Verification Service (AVS) in card domain.

About address verification service

In card domain, the AVS is a service designed to verify cardholder address data. In certain markets, such as the UK, AVS is a mandatory regulatory requirement. AVS is typically employed in various financial transaction flows, including:

• Card transaction authorisation.

• Card digitisation, such as adding a card to a mobile wallet.

Tuum Card Management System (CMS) supports AVS checks in the Mastercard Digital Enablement Service (MDES) digitisation flow when approval is requested for adding a card to Mastercard digitisation service.

Configuring address verification service

The AVS configuration, which allows the AVS check to be enabled or disabled based on market needs, can be managed through the Tuum mastercard-api system property. This configuration only affects the flow where the CMS is directly involved in card token provisioning. In this case, it impacts digitisation in the MDES flow, as the CMS communicates directly with MDES and performs AVS checks, unlike setups where a third-party handles this interaction. See the table below.

Enable or disable AVS checks

To enable or disable AVS checks in the Tuum Mastercard API, follow these steps:

1. Go to Administration > Settings > System properties.

2. From the content menu, choose Mastercard API to open the System property (mastercard-api) page.

3. Find the AVS_REQUIRED parameter and click Edit.

1. The Update system property modal opens with prefilled parameters.

2. You can select Yes (to enable) or No (to disable) from the drop-down list to configure AVS requirement in the Mastercard API.

3. Click Save to apply your changes.

Enabled AVS in operation

Once AVS is enabled, the address verification is performed against the cardholder's billing address stored in the Tuum CMS.

• If AVS_REQUIRED is set to Yes:

  • The values in the accountHolderAddress parameter from the incoming MDES Authorize Service API request are validated.

  • The validation result is returned in the response via the avsResponse parameter, using codes defined by the MDES specification.

  • If the billing address exists in Tuum CMS, the address data from the request is compared against the data stored in Tuum CMS, and the validation result is returned. The data matching check during AVS is not case-sensitive.

  • If the billing address is missing in Tuum CMS, the request is declined and error code 1011 (Billing address required but not defined) is returned.

• If AVS_REQUIRED is set to No, the avsResponse parameter is updated to AVS_NOT_SUPPORTED.