1.       What is VAU Push Subscribe Service?

The VAU Push Subscribe Service consists of Inbound and Outbound APIs available through the Visa Developer Center (VDC) for acquirers and processors.

For acquirers or processors, the VAU Push Subscribe Service offers improved speed and efficiency by providing credential updates proactively ("push") when changes occur, rather than requiring acquirers to request updates.

2.      How does VAU Push Subscribe Service work?

Acquirers and processors have the ability to subscribe to a list of cardholder primary account numbers (PANs) through the Subscription Creation API. Upon subscribing, they will receive automatic updates via the Outbound (Callback) API whenever an issuer provides a VAU update to Visa for the specified PANs.

Furthermore, the Unsubscribe API is available for removing PANs from the subscription list, and a Subscription Inquiry API can be used to verify the status of subscribed PANs.

1.       Who can use VAU Push Subscribe Service?

The service is available to any acquirers/processors operating globally.

2.      How can acquirers/processors subscribe to VAU Push Subscribe Service?

Acquirers and processors can utilize the Subscription Creation API to subscribe to a list of cardholder primary account numbers (PANs). Upon subscription, they will automatically receive updates via the Outbound (Callback) API whenever an issuer submits a VAU update to Visa for those PANs.

3.      What are the benefits of Push Subscribe Service?

The service eliminates the need for repeated inquiries, enhances authorization rates, eliminates file transmission costs when utilizing VAU batch files, and improves the cardholder experience by ensuring that current credentials are shared with the seller.

4.     What are the differences between VAU Acquirer API, VAU Push Subscribe Service and Real Time VAU?

• VAU Acquirer API is a “pull” model and hosted on VDC and works like Batch VAU, and the clients can proactively update buyer credentials prior to any purchase  transaction (a two-step process)
• VAU Push Subscribe is a “push” model and is also hosted on VDC and provides proactive updates on cardholder credentials through push notification, instead of  requiring manual inquiry requests.
• Real Time VAU eliminates “pre-auth” and provides credentials in one step as part of authorization transaction on VisaNet.

5.      Does this Push Subscribe service replace other existing VAU channels?

No, this service is not intended to replace any other existing VAU channels (batch VAU Acquirer API and Real Time VAU). It serves as an additional channel designed to enhance customer experience during card reissuance events.

This service is optional; however, we encourage clients to explore all available VAU services and implement the solutions that best meet their needs.

6.      Is the API available globally?

The API is available in regions where VAU is available

7.      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.

8.       What are the salient features of the API?

The VAU APIs are designed to be secure, scalable, and high-performance web services/API services.

9.      Is Push Subscribe Service mandatory?

No. It is an optional service that complements batch VAU, VAU Acquirer API, and Real Time VAU, providing a proactive method to update buyer credentials before any purchase transaction.

10.      How can Acquirers/Processors subscribe PANs?

Acquirers and processors may subscribe by utilizing the Subscription Creation API to register a list of cardholder PANs, ranging from 1 to 100. The API will return either a “subscribed” or “non subscribed” status. In cases where a PAN is not subscribed, the API will provide a rejection code and the corresponding reason for rejection.

11.     How can Acquirers/Processors unsubscribe PANs?

Acquirers and processors by using Unsubscribe API to unsubscribe to a list (1-100) of cardholder PANs.

12.      How does Acquirers/Processors check PAN status?

Acquirers and processors can check the PAN status by using Subscription Inquiry API to a list (1-100) of cardholder PANs

13.      What additional work the client needs to do in addition to using the APIs on VDP?

Since the Push Subscribe API necessitates Visa to update the client's system, the client is required to develop the outbound account updates API. Additionally, they must deploy this API in their non-production/sandbox environment during the testing phase.

14.      What happens when Visa/VAU tries to update client system, and it is not available?

If a client’s system cannot be reached, the VAU Push Subscribe Service will attempt six retries per day for a duration of seven days. After the retry period concludes, the client must re-subscribe to receive the latest updates.

1.     What are the features of Push Subscribe Service?

• Allows to subscribe a single or up to 100 PANs in one subscription call
• Proactive push of account updates to acquirers and merchants as soon as issuers send to Visa
• Used to inquire the subscription status of PANs as well as to unsubscribe PANs
• Reduces declines and improves authorization rates by having the latest credential

2.     What type of updates are pushed through the Push Subscribe Service?

Updates include changes due to replacement, card expiration, or account changes

3.     What are the components of Push Subscribe Service?

There are two components of Push Subscribe Service:

1.          In-Bound Bundled Name: Visa Account Updater subscription API.

Subscription creation API: This service allows up to 100 PANs to be subscribed for updates within a single request. Upon validation, the Visa Account Updater (VAU) will supply new updates if available or return the appropriate rejection codes and messages.

Unsubscribe API: This service enables the PANs to be unsubscribed.  It returns "Success" upon successful completion or provides error codes and messages when issues  are detected.

Subscription Inquiry API: This service enables clients to check the subscription status of PANs. It returns whether the PAN is "Subscribed" or "Not Subscribed," or provides  error codes and messages if any issues are identified.

2.         Out-Bound API: 

Client (acquirers/processors) outbound API: The client, which includes acquirers and processors, is required to develop this API. This will enable VAU to transmit PAN  updates to the client whenever a subscribed PAN is updated in VAU.

1.       Will there be a new acquirer reports to reflect Push Subscribe service usage?

For acquirers that opt into the VAU Push Subscribe Service and subscribe to the reports, the following new reports will be generated

A-23: VAU Push Subscription Monthly Billing Detail—This report includes a summary of the count of PAN chains (accounts) added, deleted and unchanged per merchant, along with billing details.

A-24: VAU Push Update Monthly Billing Detail—This report includes PAN updates billed monthly for the VAU Push Subscribe Service.

A-25: VAU Push Update Monthly Summary for Merchants— This report provides a monthly summary of updates at the acquirer segment level, including the count of total VAU response codes and count by merchant update types (A, E, C, Q, O, D) sent from the VAU Push Subscribe Service.

2.      How are the Acquirer VAU reports delivered?

For clients using batch and API, they will get the reports using the same channel (OFD/VFG/VFT/VFES).

For clients using VAU Push Subscribe Service only, the reports will be delivered via VOL.