Authentication methods for Visa Alias Directory Service
Resolve recipients Alias Directory Service to send funds without exposing account numbers.
Security and Authentication Requirements
All of the Visa Alias Directory Service APIs requires Two-Way SSL (Mutual Authentication) or X-Pay Token for authentication.
Two-Way SSL
As one of the security protocols, Visa Developer secures its connections with clients by means of Two-Way SSL (Mutual Authentication) method.
Please refer to the Two-Way SSL tutorial to quickly learn about how to get credentials to start building with Two-Way SSL.
Note for clients connecting to api.uk.visa.com:
Clients connecting to api.uk.visa.com may need to install additional certificates. Please speak with your implementation manager and visit this page for more information.
X-Pay Token
Some Visa Developer APIs require an API Key-Shared Secret Authentication, which Visa refers to as x-pay-token. To invoke an API using x-pay-token, you will need an API Key and a Shared Secret, which is provided via the link below.
Visit the X-pay Token Guide to learn more.
Data Encryption
Message Level Encryption
Visa requires Message Level Encryption (MLE) for Visa Alias Directory Service APIs.
Please refer to the Message Level Encryption guide for more details.