Visa Travel Notification Service Documentation

Ready to start coding?

Things To Know

Visa Travel Notification Service delivers value by providing Visa card issuers, the Visa Travel Authorization Tag in the VisaNet authorization message. The Visa Travel Notification API can be used by any developer in the sandbox, however, since the Visa Travel Authorization Tag is delivered to issuers in the VisaNet authorization message, only Visa issuers can sign up for Visa Travel Notification Service and use the API in production. The Visa Developer sandbox environment currently does not have VisaNet connectivity, so you cannot validate the receipt of an authorization message with the Visa Travel Authorization Tag in the sandbox.

You are responsible for collecting travel plans from your cardholders, including building and managing any mobile app screens or web pages where cardholder can inform you of their travel plans. Once a cardholder has informed you of their plans, you send the applicable information to the Visa Travel Notification API.

You can also use the Visa Travel Notification API to retrieve travel itineraries that you had previously submitted to the Visa Travel Notification API. However, you must follow these rules when using the Retreive operation of the Visa Travel Notification API:

  • Requests to the Retrieve operation must not exceed four (4) times the number of Add requests you submitted in any given month. For example, if you submit 10,000 Add requests, you are not allowed to send more than 40,000 Retrieve requests in that month.
  • Although the Retrieve operation returns full PANs, you must not display the full PAN on any cardholder-exposed devices or screens in order to help prevent “shoulder surfing”.

See the API Reference link for details on the API. 

Information for Issuers in the United States and Canada

If you are an issuer in the United States or Canada, the Visa Travel Authorization Tag is also an input to Visa Advanced Authorization scoring. You should refer to the Visa Travel Notification Service Description for more information on scenarios when Visa populates the Visa Travel Authorization Tag in the authorization message outside of the Visa Travel Notification Service.

To request a copy of Visa Travel Notification Service Description, contact developer@visa.com or your Visa representative.

Availability

The following table lists the regional availability for Visa Travel Notification Service. 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 Travel Notification Service
Product Name Availability Notes
Visa Travel Notification Service
Product Name Availability Notes
Visa Travel Notification Service
Product Name Availability Notes
Visa Travel Notification Service
Product Name Availability Notes
Visa Travel Notification Service

Getting Started

The Visa Travel Notification Service helps you avoid mistaken purchase declines while your cardholders are traveling by incorporating cardholder self-reported travel plans into the VisaNet authorization message. With Visa Travel Notification Service, Visa informs you whether your cardholder is transacting during the travel dates and at the travel destination they reported, helping you more confidently approve transactions when your cardholders make purchases while travelling.

The first step in getting started with Visa Travel Notification Service is to understand the general flow, the role of the API, and the role the Visa Travel Authorization Tag plays.

Visa Travel Notification Service: How It Works

When cardholders inform you of their travel plans, you send those travel details to Visa using the Visa Travel Notification API. Visa then stores the travel itinerary for use when your cardholder starts the trip. When your cardholder transacts, Visa analyzes whether the transaction is located near the travel destination and falls within the travel dates reported by your cardholder. Based on this analysis, Visa populates the Visa Travel Authorization Tag in the authorization message and updates the Visa Advanced Authorization score so you can use these in your decision to approve or decline the transaction. Note: The Visa Advanced Authorization score is only impacted by Visa Travel Notification Service if you are an issuer in the United States or Canada.

It is up to you to determine how cardholders inform you of their travel plans and how they can tell you when those plans change. Visa recommends you include a form in your mobile app and online banking website where cardholders can easily enter their travel destination and travel dates. When your cardholders enter a travel plan, you send those details to the Visa Travel Notification API. If your cardholders call your customer service center to tell you their travel plans, your customer service system backend can send the information to the Visa Travel Notification API.

Refer to the figures below that provide sample screens for a cardholder to report their travel plans to you in your mobile app.

Cardholder Travel

How Does It Work?

When your cardholders inform you of their travel plans (e.g. via an online form or your call center), you can send those travel details to Visa using the Visa Travel Notification API. Visa then stores the travel itineraries for use when your cardholders makes purchases while travelling. When your cardholder transacts, Visa analyzes whether the transaction is located near the travel destination and during the travel dates you sent to Visa. Based on this analysis, Visa sends you an enhanced Visa Advanced Authorization Score and populates the Visa Travel Authorization Tag in the authorization message so you can use them in your decision of whether or not to approve a transaction.
Note: The Visa Travel Notification Service only impacts the Visa Advanced Authorization score if you are an issuer in the United States or Canada.

Since Visa Travel Notification Service is API based, you can send travel details to Visa regardless of how your cardholders tell you their plans. For example, if you have an online or mobile form that cardholders can enter their travel plans into, you can send the cardholder-reported plan to the Visa Travel Notification API. If your cardholder calls your customer service center, your customer service backend system can send the cardholder-reported travel plan to the Visa Travel Notification API.

Why Use It?

Fewer Inaccurate Transaction Declines

Confirmation that cardholders are transacting at their reported travel destinations helps you authorize transactions more confidently and keep your travelling cardholders happy.

Reduce Cost

Can help decrease calls to your call center by helping to reduce mistaken declines and pre-travel notification calls.

API Included

Visa Travel Notification API

The Visa Travel Notification API allows you to send new travel itinerary details to Visa, update a travel itinerary, delete a travel itinerary, and request details of travel itineraries you previously sent to Visa.

Using the Travel Notification Service API

Visa Travel Notification Service includes one API with two resources. The first resource allows you to add, update, and delete travel itineraries. The second resource allows you to retrieve details of travel itineraries you previously submitted to Visa. The following sections provide descriptions of the Add, Update, Delete, and Retrieve operations.

Add

The Add operation allows you to send new travel plans to Visa. When your host system receives a new travel itinerary from a cardholder (e.g. cardholder enters information into an online form, calls your automated system, or speaks to your Customer Service Representative and your Customer Service Representative manually enters the cardholder’s travel plans into your system), you are responsible for sending the travel itinerary details in an Add request. Travel itinerary details consist of the cardholder’s destination country, departure date, and return date. When Visa receives a successful Add request, Visa responds with a Travel Itinerary ID created for that travel plan.

Update

The Update operation allows you to update details of travel itineraries you previously sent to Visa. When cardholders inform you that their travel plans have changed or you need to make a change to existing travel itineraries, you are responsible for sending the updated travel details in an Update request. When Visa receives a successful Update request, Visa replies with a confirmation that the update was successful.

Delete

The Delete operation allows you to delete travel itineraries you previously sent to Visa. When cardholders inform you that they have cancelled their travel plans or you need to delete existing travel itineraries, you are responsible for sending a Delete request. When Visa receives a successful Delete request, Visa replies with a confirmation that the deletion was successful.

Retrieve

The Retrieve operation allows you to request details of travel itineraries you previously sent to Visa. When Visa receives a successful Retrieve request, Visa replies with the list of travel itineraries and corresponding details that match the criteria in your request. You must follow these rules when using the Retrieve operation: 

  • The Retrieve operation is for one-off inquiries, and the service is not architected to be a data storage solution or your system of record. Requests to the Retrieve operation must not exceed four (4) times the number of Add requests you submitted by in any given month. For example, if you submit 10,000 Add requests, you are not allowed to send more than 40,000 Retrieve requests in that month.
  • Although the Retrieve operation returns full PANs, you must not display the full PAN on any cardholder-exposed devices or screens in order to help prevent “shoulder surfing”.

For further information on the Visa Travel Notification API, refer to the API Reference link.

Understanding the Visa Travel Authorization Tag

When your cardholder transacts at the travel destination and within the dates of a travel itinerary on file with Visa, Visa sends you a Visa Travel Authorization Tag in the authorization message. For further details on using the Visa Travel Authorization Tag, please see the Visa Travel Notification Service Description. For details on implementing the Visa Travel Authorization Tag, refer to Article 3.4 of Visa’s October 2013 Global Technical Letter. To request a copy of the Visa Travel Notification Service Description or the October 2013 Global Technical Letter, contact developer@visa.com.

Security and Authentication Requirements

Visa Travel Notification API uses mutual SSL authentication and channel encryption, which requires that you obtain a user ID and password as well as install a PKI certificate issued by Visa. You can obtain the test credentials online in the Project Console for sandbox testing. Production credentials will be supplied to you 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

Cardholder Disclosure Requirements

You must implement Visa Travel Notification Service in accordance with applicable law and are responsible for gathering necessary authorization and consent from your cardholders to share travel itinerary information with Visa.

Activation Requirements

You must sign up for the service with Visa by signing a Fraud Risk Products Agreement, indicating Visa Travel Notification Service as the service for participation. After signing an agreement, Visa will assign you an Implementation Manager who will be your main point of contact at Visa during implementation. They will provide you with a project plan for implementing Visa Travel Notification Service.

For a full list of activation requirements, refer to the Visa Travel Notification Service Description. For a copy of the Visa Travel Notification Service Description or Fraud Risk Products Agreement, contact developer@visa.com.