Getting Started with Visa Alias Directory

Visa Alias Directory Service

Simplify the push payment experience. Link and resolve an Alias to a payment credential.


Start a Project
API Overview
API Reference

Getting Started with Visa Alias Directory Service

Alias Directory 2.0

Alias Directory offers capabilities for clients to link Aliases to payment credentials. An Alias is an identifier such as mobile number or email address that can be used in place of sensitive payment credential details. A payment credential could be a card or bank account. Additional payment credential types, like wallet, can be added in the future. The Alias Directory provides services for clients to manage the lifecycle of an Alias and to resolve an Alias to receive the associated payment credential.

The documentation in this page is for Alias Directory 2.0. Clients who are using Alias Directory 1.0 can find the technical documentation here.

Key enhancements in Visa Alias Directory Service 2.0

Availability

The following table lists the regional availability for Visa Alias Directory.

North America Asia-Pacific Europe CEMEA LAC Notes

KEY

Key Functionalities

Linking Aliases to Payment Credentials

An Alias Directory provides the flexibility to map different Aliases, such as phone and email, to a payment credential.

Zoom

Alias Resolution

A client can use Visa Alias Directory Service to improve the consumer experience during push payments. For example, a Visa client can provide Visa Alias Directory Service with an Alias and receive the payment credential linked to that Alias (e.g., card or bank account). This credential can then be used in a push payment.

Zoom

Alias Lifecycle Management Tutorial Video

play_circle_outline

Alias Resolution and Alias Inquiry Tutorial Video

play_circle_outline

Directory Network Manager

Alias Directory offers the capability to connect to remote directories via a component called Directory Network Manager. Directory Network Manager has the capability to query available remote directories with an Alias and retrieve the associated payment details, if available.

Zoom

Directory Network Manager Marketing Video

Directory Network Manager Marketing Video

play_circle_outline

Potential benefits to participating remote directories:

Implementation Overview

1. Pre-Implementation

Estimated duration: 1-2 weeks

Key Activities:

2. API Implementation

Estimated duration: 4-8 weeks

Key Activities:

3. User Experience Design

Estimated duration: 4-8 weeks

Key Activities:

4. General Availability

Estimated duration: 4-6 weeks

Key Activities:

Next Steps

Contact Us

To reach the product office, please reach out to developer@visa.com