Visa Account Updater Documentation

Ready to start coding?

Things to Know

Visa Account Updater Issuer Reporting API can be used by developers in the sandbox. To access the API in production, issuers must be enrolled as a participating issuer in VAU and provisioned with a VAU Segment ID. Please contact developer@visa.com for information on how to enroll in VAU. 

In the sandbox environment, you can input a test account number and expiration date and the API will return test data.

In production, the API request will be validated to ensure that you have submitted your enrolled VAU issuer segment's card numbers in the BINs. You can receive information only on card numbers associated with your enrolled BINs.   

Note: Participation in Visa Account Updater is highest in the U.S. and Canada. Outside these markets, issuers are advised to speak to their Visa representative about VAU adoption in the countries where they operate, before deciding whether to test/deploy the API. The Visa Account Updater Issuer Reporting API is currently not available for issuers on the European VAU platform. Details of availability of this functionality for issuers in Europe will be announced in a future Visa Business News article.

Availability

The following table lists the regional availability for Visa Account Updater. To view availability of all products, refer to the Availability Matrix.

Available in entire region

Limited availability in region

Not available

Product Name Availability Notes
Visa Account Updater
Product Name Availability Notes
Visa Account Updater
Product Name Availability Notes
Visa Account Updater
Product Name Availability Notes
Visa Account Updater
Product Name Availability Notes
Visa Account Updater

Getting Started

Visa Account Updater (VAU) enables a secure electronic exchange of account information updates between participating Visa card issuers and acquirers for credential-on-file merchants, which enables a more seamless payment process. When participating issuers re-issue cards, they submit the new account number and expiration date to VAU. Participating merchants send inquiries on their credentials-on-file to VAU and are provided with updated card information, if available. This helps participating issuers retain cardholders by maintaining continuity of their payment relationships with participating merchants.

The Visa Account Updater Issuer Reporting API provides your cardholders with up-to-date information on credential-on-file merchants who have requested updates on their cards. This information enables you to develop projects that help your bank provide a better customer experience for your cardholders when their cards have been re-issued.   

The following three use cases illustrate how the API can be used:

  • Allow cardholders to view merchants who have requested updates on their cards
  • Enhance customer service by providing up-to-date information
  • Enable personalized communication during brand conversion

How Does It Work?

As a VAU participating issuer, the Visa Account Updater Issuer Reporting API provides you with up-to-date information on merchants that have requested updates on your customer's cards. When your cardholder contacts you to find out which merchants have obtained their new card information, you can submit the account number and expiration date in the Visa Account Updater Issuer Reporting API to obtain a list of merchants that have requested an update on the account number.

This API will identify the merchants that have requested an update, the date of their inquiry and the type of update they received from VAU. 

Why Use It?

VAU participating issuers can obtain up-to-date information on credential-on-file merchants that have requested updates on your customer's cards so you can deliver a better customer experience when your cardholders want to know the merchants that have obtained their new card information. 

API Included

Visa Account Updater Issuer Reporting API enables you to submit one or more account numbers and obtain a list of merchants that have requested updates on the customer's card account number(s). 

Enabling Cardholders to Identify Merchants

You can use the Visa Account Updater Issuer Reporting API in your bank mobile app to help cardholders identify credential-on-file merchants that have requested updates on their cards. As an example, when a cardholder activates their re-issued card, they receive a notification on the mobile app advising them to check back at a later date to view which credential-on-file merchants have requested their new card information. The cardholder returns to the mobile app at a later date and sees a screen similar to the following:

The screen above shows a list of merchants that have requested updated card information, the date of their inquiry, as well as, the response sent to the merchants. In reviewing this screen, the cardholder knows they do not need to contact these merchants, but they may need to contact other merchants who may have their credentials on file.

Here is an API Response code sample:

Copied to clipboard
"panData": {

"pAN": "4012345678910111",

"panResponseMsg": "Success",

"expDate": "1020",

"inquiries":

[{

"merchantName": "Internet Radio",

"subMerchantName": " "

"merchantInquiryDate": "20170117",

"merchantResponseCode": "A",

"tpaInd":"N",

}]

}
                    

Enhancing Customer Service

You can use the Visa Account Updater Issuer Reporting API in your bank customer service portal to equip customer service representatives with better information to serve customers. As an example, a cardholder with a re-issued card may see a recurring billing charge on their new card, prompting them to call customer service. The customer service representative (CSR) authenticates the cardholder and makes an API call through the customer service portal to see which merchants have requested updates. The portal displays a screen similar to the following:

The screen above shows a list of merchants that have requested updates on the card, the date of their inquiry, as well as, the response sent to the merchants. The CSR is then able to inform the cardholder which merchants have obtained the new card information. The CSR should also advise the cardholder to contact other merchants who may have their credentials on file, but are not listed. The CSR should take this opportunity to highlight the benefit and convenience your bank has provided by automatically updating these merchants, thus saving the cardholder time.

Enabling Personalized Communication

You can use Visa Account Updater Issuer Reporting API to retrieve merchant inquiry information for multiple account numbers (up to 3,000 accounts per API call).

This is useful when there is a brand conversion, as it allows your bank to personalize its customer outreach communications. For example, let's say the bank converts from another network to Visa and would like to pro-actively communicate to their cardholders on which credential-on-file merchants have been provided with the new card information. The bank submits a bulk API call with multiple account numbers and receives a response with a list of merchants and dates associated with each account number. The bank processes the response data and sends a personalized communication to each cardholder, notifying them which merchants have obtained their new card information. In addition, the bank should advise the cardholder to contact other merchants (which are not listed), but may have their credentials on file—since not all merchants participate in VAU. The bank should take this opportunity to highlight the benefit and convenience it has provided by automatically updating these merchants, thus saving the cardholder time.

Here is a code example of how you would enter multiple account numbers: 

Copied to clipboard
"pANs": [{

     "pAN": "4012345678910222",

     "expDate": "1906"

     },

     {

"pAN": "4012345678910333",

     "expDate": "1909"

    }]
                    

Exception Handling

The following are the Visa Account Updater Issuer Reporting API error codes and associated descriptions.

Status Code Description  Recommended Handling
CDI001  Internal service failure  Please wait and retry 
CDI071  Request data invalid  Check request data format  
CDI003  Missing required element value   Check to make sure PAN and Expiration Date (or BIN) and Group name are included in the request  
CDI011  Requesting Client IP is invalid  Validate Requestor IP
CDI012  Request Header Data length is invalid    Check to make sure the Request Header has the proper length
CDI013  Request data string elements length is invalid   Check to make sure PAN and Expiration Date have the proper length  
CDI041  Entry Group info lookup failure  Contact developer@visa.com to check registration information
CDI094  Invalid request. Group name is required Check to make sure Group name is included in the request 
CDI096  No Groups are configured for the requested Business Application ID   Check Header Token in the request or contact developer@visa.com to check registration information
CDI131  Entitlement is not enabled for the requested service  Contact developer@visa.com to check if registration information
CDI160 PAN/Expiration Date mismatch  Check to make sure you have the correct PAN and Expiration Date in the request
CDI161 PAN is not valid for this Issuer Segment ID  Check to make sure you have the correct Segment ID and PAN in the request 
CDI167  Request data mismatch for more than one PAN  Check to make sure you have the correct PAN and Expiration Date in the request
CDI092  No corresponding or matching data found  No data found for a given request. Try another request. 
CDI137  Invalid Group name Check Group name in the request 

Security and Authentication Requirements

The Visa Account Updater Issuer Reporting API uses the standard VDP project authentication.

Test credentials for sandbox testing can be obtained online in the Developer Dashboard for the project. Production credentials will be issued as part of the production on-boarding process. Contact developer@visa.com for more information or to begin the production on-boarding process.

Service Activation Requirements

To use the Visa Account Updater Issuer Reporting API in production, your financial institution must be enrolled as a participating issuer in VAU. Please contact developer@visa.com for information on how to enroll in VAU.

Best Practices and Tips for Using Visa Account Updater Issuer Reporting API

Disclosures

You must include the appropriate disclosures when sharing the list of merchants with your cardholders. Cardholders must be made aware that not all credential-on-file merchants participate in VAU. This list only reflects merchants who have inquired and received updates on their account number. In addition, cardholders must be advised that the updates are not guaranteed before the next billing cycle.

Submitting API Request

When you submit an API Request, you will need to determine whether to include the old or new account number. If based on the reason for the card reissuance, the update to VAU was a new Account Update (A) or a new Expiration Date Update (E), then you will need to include the new account number in the API Request. If based on the reason for the card reissuance, the update to VAU was a Closed Account advice (C) or a Contact Cardholder advice (Q), then you will need to use the old account number, since there are no new account numbers or expiration dates associated with these types of updates. 

Note: Service identifiers correspond to the merchant response code returned in the API Response. For more information on service identifier/merchant response code, please refer to the API reference link.

Using API Response Data

In the API Response, if the merchant response code is 'A' or 'E', then display the merchant names and inquiry dates returned in the API and inform the cardholder that their updated card information was provided to the listed merchants. If the merchant response code is 'C' or 'Q', then display the merchant names and inquiry dates returned in the API and inform the cardholder that the listed merchants were notified to contact the cardholder to obtain updated payment information.

In the API Response, if the third party indicator value is 'Y', this means that the merchant is a payment facilitator and the actual merchant name that should be displayed can be found in the sub merchant name field. If the sub merchant name field is populated, we recommend you display this name to your cardholders. If the sub merchant name field is not populated, we recommend you suppress the name of the payment facilitator and not display the update. Cardholders may not be familiar with payment facilitator names and may be concerned with their card information being shared with these payment service providers.