1. What is the VAU Acquirer API?
VAU Acquirer API is a secure, scalable, high performance web service/API service for acquirers and/or processors for merchants to submit VAU inquiries and receive real time updates with information from the Visa Account Updater database, helping enable an improved customer experience for card reissuance events. It is an optional feature that supplements batch VAU and Real Time VAU and can be used to proactively update buyer credentials prior to any purchase transaction.
2. What are the differences between Acquirer API and Real Time VAU?
3. Does this API replace other existing VAU channels?
No, this API is not meant to replace any other existing VAU channels. It is an additional channel added to enable an improved customer experience for card reissuance events. It is an optional service. However, we encourage clients to explore all the VAU services and implement the solutions that suit them best.
4. Is the API available globally?
The API is available in regions where VAU batch is available
5. As a TPA, if I am supporting multiple acquirers, do I need to register for each acquirer?
Yes. Separate registration is required for each acquirer, as each acquirer has their own unique Business ID and attached segment IDs.
6. Which Stop Advice will be applicable to the VAU Acquirer API – the VAU or the Real Time VAU?
The VAU Acquirer API looks at the same database VAU. We typically recommend the issuer to apply Stop Advice on both VAU and Real Time VAU when they are setting up Stop Advices.
7. Will there be a separate acquirer reports to reflect API usage?
No. If you are using both batch and API, the data is included in the same VAU reports that you currently receive.
8. Which reports are affected by the API?
The following reports will be included as a part of this API: A4, A6, A8, A10, and A11. There is no separate categorization/breakdown of inquiries for API and the counts are aggregated.
9. How are the Acquirer VAU reports delivered?
For clients using batch and API, they will get the reports using the same channel (OFD/VFT/VFES).
For clients using Acquirer API only, the reports will be delivered via VOL.
10. Where can I find more information on the VAU Acquirer API?
The latest information on VAU Acquirer API documentation will be available on Visa Developer Center (VDC) ([email protected]). We will also be updating the VAU Implementation guides.
11. What is minimum and maximum of PANs that can be sent?
The minimum number of PANs is 1 and the API can handle up to 100 PANs in one call.
12. Will the API be available 24/7?
Yes, the API will be available 24/7. The only times clients may not be able to access the API is during periods of maintenance on VDC; however, clients will receive advance notification from VDC of maintenance periods.
13. How much do I get charged per update?
Each update is the same price as VAU (and will be billed on the same billing line).
14. Will I be charged if I request the same update more than once?
Each time an update is provided, there will be a charge. To avoid duplicate charges, a parameter “previouslySentFlag“ is included as part of the response. This parameter is populated with ‘N’ (No) or ‘Y’ (Yes). The first time the response is provided, the field is populated with ‘N’. However, subsequent inquiries to the API with the same request information with result in charges along with populating the ‘previouslySentFlag’ to ‘Y’.
To avoid duplicate charges, the seller should update their database with the information provided.
Start a Project
API Overview
API Reference