VAU Issuer Stop Advice API FAQs

1.       What is the VAU Issuer Stop Advice API?

The VAU Issuer Stop Advice API is a secure, scalable, and high-performance web service/API for issuers and issuer processors to send VAU requests to place stop advices to prevent updates for specific cardholder PAN(s) and merchant(s) combinations from being shared in VAU in responses.

2.      What are the benefits of stop advices?

The benefit of VAU Stop Advice is that an issuer can proactively block a merchant from getting an automatic VAU update (e.g., following reported fraud) while still allowing their cardholder to transact with the merchant where appropriately authorized by the customer.

The functionality allows VAU issuers to place cardholder level Stop Advice at a merchant level. Issuers can use the VAU Stop Advice feature to prevent VAU updates from being shared with specific merchants.

3.      What other benefits are there for Issuers?

• Fraud reduction: The automated solution may help break the cycle of repeated fraud. An issuer can block a merchant from getting an automatic VAU update (e.g., following reported fraud) while still allowing their cardholder to transact with the merchant where appropriately authorized by the customer.
• Dispute reduction: Easily blocking cardholder updates from being provided to merchants where fraud was reported may help reduce repeated disputes.
  
• Efficiency: Automating the stop advice creation process can reduce manual processes for issuers.

4.      How does VAU Issuer Stop Advice API work?

The VAU Issuer Stop Advice API takes as input either a single Personal Account Number (PAN), merchant ID, Card Acceptor ID (CAID) or a set of up to 100 requests containing a PAN, CAID, and merchant ID to set up the stop advice(s).

5.      Which features will be a part of this channel?

• Secure API and accessible on Visa Developer Center
  
• Stop Advices placed may apply to both VAU and Real Time VAU in one API call.
• Supports single PAN or multiple PANs per API call with multiple merchants. (Max: 100 requests per call)
• New Stop Advice Reports will be available that provide a list of stop advice issuer has placed in VAU and Real Time VAU using the new API.

6.      Which Stop Advice will be applicable to the VAU Issuer Stop Advice API – VAU or Real Time VAU?

The VAU Issuer Stop Advice API looks at the same VAU database. When using the API, it will try to apply stop advices for both VAU and Real Time VAU. If it can’t find the merchants in both VAU and Real Time VAU, it will apply where a match is found (batch or Real Time).

7.     What is the client impact?

Issuers / processors interested in using the VAU Issuer Stop Advice API should review the associated technical specifications and contact their Visa representative to discuss planning and implementation. For the technical specifications, visit the Visa Developer Center website and search for the VAU Issuer Stop Advice API.

Issuers already using the VAU application on Visa Online to place stop advices may continue that practice but will also have the option to use the API.

8.     What’s the process for new issuers/process to use the API?

To use the API in production, the issuers/processors must enroll in VAU, send cardholder updates via batch file, PAN LCM API or ISO 0302 message before the API can be used to set up stop advices.

9.      How are VAU Stop Advices different from Visa Stop Paymwnt Service (VSPS)?

VAU Stop Advices blocks VAU credential updates upon inquiry by the merchant whereas VSPS helps issuers quickly and easily stop unwanted future payments from debiting a cardholder’s account.

10.    Does VAU Stop Advice decline transactions?

No. VAU Stop Advice only blocks the VAU update (does not share any account credentials with the merchant in the VAU response) and does not result in Visa declining the transaction.

11.     Can a Stop Advice be placed on a token?

No. The VAU Stop Advice API would only support 16-digit PANs and does not take as input any tokens. However, the issuers can deactivate a token if they want to prevent the merchant's token from getting updated.

12.     Are there any fees for placing stop advice?

Not currently. Use of the VAU Issuer Stop Advice API will be free through at least 30th September 2024.

13.    How is VAU Issuer Stop Advice API different from the functionality available in VAU Visa Online?

VAU Issuer Stop Advice API is another channel being provided in addition to the one available on VAU application on Visa Online. However, there are some differences. In the case of the API, the stop advices can be applied in one API call to both VAU and Real Time VAU if there is a merchant match found for both. In using the VAU application on Visa Online, though the functionality is the same, the user must apply stop advices to VAU and Real Time VAU separately. In addition, the user cannot apply stop advices to multiple PANs at the same time unlike with the API.

14.   What is the data retention for Stop Advices?

Stop advice are stored indefinitely unless there is an end date (optional) specified or the stop advice is removed. The user needs to enter the start date – if not entered, it defaults to the next day/system date.

15.    Can VAU Stop Advice API support updating/deleting the Stop Advice?

No. It only allows issuers to set up new stop advices. To remove or change/update the effective date, the client needs to use the VAU Client facing application on Visa Online.

16.    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 and supplements VAU application on Visa Online. It is an optional service. However, we encourage clients to explore all the VAU functionality and implement the solutions that suit them best.

17.    Is the API available globally?

Yes. The API is available in all regions where VAU is available.

18.   Who can use the API?

The VAU Issuer Stop Advice API can be used by any developer associated with an issuer or processor in the sandbox.

However, to use the VAU Issuer Stop Advice API in production, the originator must either be a licensed Visa Issuer, or an issuer processor. In addition, issuers must be enrolled in VAU and provisioned with a VAU Segment ID. The API request will be validated to ensure that the submitted card numbers associated with issuing BINs are enrolled in VAU issuer segment.

19.    Are test data and test cases available?

Yes. The developers can download the test cases with test PANs from the Visa Developer Center portal and can use this data to test for various scenarios in the sandbox. Test VAU issuer segment IDs and BINs are provided as part of the sandbox test data and includes sample account numbers and expiration dates.

NOTE:  The test cases contain sample PANs and do not pass Luhn’s (Mod-10) validation. They must be used in the sandbox as is. If a client wishes to test outside the sandbox in their own environment, they need to turn off the check for Luhn’s (Mod-10) validation while using these PANs.

20.  What is required to access API in production?

If you are a new user to VAU, please first contact your Visa representative. Review VAU terms of use, and other documentation with legal, technical, operational, and customer proposition teams. Submit a completed VAU issuer enrollment form. Create an account on VDC. Verify login and set up sandbox environment.

To access the API in production, a client must be enrolled in VAU and provisioned with a VAU Segment ID and submitting account credentials to VAU. The API request will be validated to ensure that the submitted card numbers associated with issuing BINs are enrolled in VAU issuer segment.

21.    Where can I find more documentation/information on the VAU Issuer Stop Advice API?

For the latest information, VAU Issuer Stop Advice API documentation that includes swagger changes, test cases are available on Visa Developer Center (VDC).  You can also refer to VAU Implementation or Service Description Guides or contact your AE.

22.   What are the HTTP responses of the API?

The Visa Account Updater (VAU) Issuer Stop Advice API returns these HTTP 200 API responses depending on where the stop advice has been applied. These are not considered as errors.  Based on the responses, the user needs to take appropriate action.

For more information, please refer to the VDC portal or test cases examples.

23.   What is the first thing a client need to do to get started:

After reading quick start guides and working with Visa APIs, the first thing is to open a project on Visa Developer Center and select VAU Issuer Stop Advice API and complete the required fields and download the credentials for the sandbox testing. If a client is already registered in VDC, they can reuse the VDC credentials to use the API. There is no need to register again.

24.  How do I implement the VAU Issuer Stop Advice API

Visa Account Updater Issuer Stop Advice API can be used by developers in the sandbox without the need to involve client support or technical solutions team. However, when a client is ready to move to production, then, there are some steps to be followed depending on whether a client is brand new to VAU and using API only, or existing batch client and wants to use API.

If you are a brand-new to VAU, please contact your Visa representative. Review VAU terms of use, and other documentation with legal, technical, operational, and customer proposition teams. Submit a completed VAU enrollment form. Create an account on VDC and follow up the steps as outlined under Implementation Steps below.

25.  Where can I download Test cases/data for VAU Issuer Stop Advice API?

The test cases can be downloaded from the project dashboard for the API, select Assests and then select Sample Code to download.

26.   Do I need to provide my own PANs for testing?

No. The test cases include sample test PANs that are not MOD-10 Compliant and do not pass Luhn’s (Mod-10) validation.

For testing in sandbox, the client needs to use these PANs as is. If you are testing outside the sandbox and using your own test PANs, please turn off the check for Luhn’s (Mod-10) validation while using these PANs.

27.  What are the Implementation Steps for existing or new client?

Please refer to "Getting Started page" or VAU Implementation Guide for implementation steps

28.  What if I am already using other API(s) on VDC?

If you are already using other APIs on VDC, you will log in using same credential but start a new project by selecting VAU Issuer Stop Advice API. Credentials are bound to the project not the product. A client can have many projects with a single set of credentials.

29.   How long would it take to implement the API? What is the time frame in which it will take to set up a client for the VAU Issuer Stop Advice API?

A variety of factors will determine the time it takes to set up and implement the API. Factors such as client’s technical resource availability, current knowledge base, and if they are a current user of other APIs within Visa. Other factors includes legal reviewing the VDP contract and signing.

30.  Do I have to implement this API if I am already using VAU application on Visa Online to set up stop advices?

No, this API is a completely optional service.

31.    Is testing required before going live with API use?

Yes. It is best and common practice to do testing of any Visa products before the moving to production.

32.   Is certification environment required to implement VAU Issuer Stop Advice API?

No. Certification environment is not needed for VAU Issuer Stop Advice. If the VDP prod requests team responds that a certification is need, please inform them that there is a glitch in the VDP Portal that states the certification environment is required. The VDP Business Ops team is instructed to manually override/reset the flag. Only Sandbox testing is required.

33.  What is minimum and maximum of pans that can be sent?

The minimum number of PAN is 1 and can include 100 merchants. The maximum number of PANs is 100 with 1 merchant per PAN in one API call.  In essence, the API can contain between 1 and 100 requests of PAN and merchant combinations?

34.  Will the API be available 24/7?

Yes, the API will be available 24/7. The only times client 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, or displayed on the portal.

35.  Will there be new Issuer Stop Advice reports to reflect API usage?

The following new daily stop advice reports are available. These reports provide a list of stop advices the issuer has placed in VAU and Real Time VAU using the API and the Visa Online application.

• I-28 Daily Stop Advice Report by Segment (from API)
• I-29 Daily Stop Advice Report by BIN (from API)

36.   Do the issuers automatically receive these reports?

No. Issuers need to subscribe to these reports if they want to receive them.  Please contact your client support team to request for the desired reports.

37.   Do the reports categorize the responses based on the channel?

Yes. The reports I-28 and I-29 are specific to stop advices placed via API and the reports I-24, I-25, I-26, I-27 are specific to stop advices placed via VOL.

38.   What happens when a client receives an error?

When facing an error in API, the first contact is VDC at [email protected].

39.   Who do I reach if I have problem with API?

You can start with sending emails to Visa Development Center Support and they are the first point of contact. If there are issues related to actual data, then you can reach out to client support/technical solutions team mentioned above based on region.

40.  Regional specific - client support email address:

The following are the email address to contact customer support teams for each region:

• AP: [email protected]
• CEMEA: [email protected]
• NA: [email protected]
• Europe: [email protected]
• LAC: Log in to LAC Visa Online and submit a Visa Support Hub (VSH)) Self- Service case