# Visa Receiver Directed Payouts

\\
Start a Project](https://developer.visa.com/portal/#users/new) \\
API Overview](https://developer.visa.com/capabilities/visa-receiver-directed-payouts)

- [Getting Started](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/docs-getting-started)
  - [About Receiver Directed Payouts](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/docs#section0)
  - [How Does It Work?](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/docs#section1)
  - [Consumer Information required](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/docs#section2)
- [How to Use Receiver Directed Payouts](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/docs-how-to)
- [Product Terms](https://developer.visa.com/capabilities/visa-receiver-directed-payouts/product-terms)

Navigate to...

_keyboard\_arrow\_down_

## Getting Started with Receiver Directed Payouts

### About Receiver Directed Payouts

A front-end Java Script SDK that is embedded within the client's User Experience, Receiver Directed Payouts is a feature of the Visa Alias Directory and provides an opportunity for individual capture of a receiver's payment credentials.

As an originator or enabler you can securely capture, verify, validate and store payment credentials with an alias (e.g. telephone number) in the Visa Alias Directory

Key Stakeholder:

|     |     |
| --- | --- |
| **Entity** | **Description** |
| Originator/Enabler | The corporate entity sending the payment to the Recipient |
| Visa | Credential Capture Widget that is invoked by Visa’s SDK |
| Recipient | Recipient who is receiving the money from the Originator |

### How Does It Work?

**The credential capure flow:**

**Education and OTP verification**

1. Client displays payout screen where the user can navigate to RDP flow by requesting to add new payment account
2. User selects Add Payment Method, which invokes the SDK widget which is hosted in the client’s UX (webpage, app, etc.)
3. User is prompted to enter OTP sent to their phone number on file with client for identity verification purposes
4. Once OTP is entered, user can tap Verify and proceed with enrolment
5. After successful verification, card credential capture follow

**Credential Capture and 3DS authentication**

1. User adds a card through the card credential capture form
2. After card information is submitted, user is directed to authenticate card credentials with 3DS and its OTP method
3. To complete enrolment, user confirms by linking their payment credentials to their mobile phone number

**Payout Confirmation**

1. Originator / Enabler is now able to make payment to receiver and confirm funds have been sent.

### Consumer Information required

The consumer information that RDP will require

|     |     |     |     |     |     |
| --- | --- | --- | --- | --- | --- |
| **Field Name** | **Type** | **Mandatory (M) / Optional (O)** | **Length** | **Validation** | **Description** |
| First Name | String | M | Min Length: 2<br>Max Length: 22 | Length validation | Card holder’s first name |
| Last Name | String | M | Min Length: 1<br>Max Length: 1 | Length validation | First letter only of card holder’s last name |
| Address Line 1 | String | O | Min Length: 1<br>Max Length: 50 | Length validation | First line of the card holder’s address |
| Address Line 2 | String | O | Min Length: 0<br>Max Length: 50 | Length validation |  |
| City | String | O | Min Length: 1<br>Max Length: 50 | Length Validation |  |
| Zip Code | String | O | Min Length: 1<br>Max Length: 16 | Length Validation |  |
| Card Number | Numeric | M |  | Modulus 10 Check<br>Supported card Validation (VISA) |  |
| Expiration Date | Numeric | M |  | Date is greater than current month/year.<br>Numeric only | First 2 digits = Month<br>Second 2 digits = Year |

_arrow\_upward_ Back to top