# Recipient Account URI
source: https://developer.mastercard.com/cross-border-services/documentation/additional-resources/common-recipient-acct-uri/index.md

This page provides additional information about some of the values required for some of the API fields.
Note: The Recipient Account URI mandatory scheme is provided in the Technical Endpoint Guide.

| Scheme  |                                                                                                                                                                                                                                                                                                                                     Scheme specific data                                                                                                                                                                                                                                                                                                                                     |
|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| tel     | E.164 number identifying a Telephony Subscriber. The number (usually a MSISDN) must be expressed as an E164 number containing: \[+\]\[country code\]\[area code\]\[local phone number\] + - plus sign country code - international country code area code/national destination code - code without leading 0 phone number - local phone number The '+' sign is mandatory (it is compliant with RFC3966 format / international number only). Example: | Country | Local Phone Number | E.164 Formatted Number | |---------|--------------------|------------------------| | USA     | 415 123 1234       | +14151231234           | | UK      | 020 1234 1234      | +442012341234          | |
| pan     | Specifies a card account number with a maximum length of 35 and a minimum length of 12. Data format: NNNNNNNNNNNNNNNN\[NNN\]\[;exp=YYYY-MM\]. Examples: pan:5432123456789012;exp=2017-02 pan:5432123456789012333;exp=2017-02 pan:5432123456789012 pan:5432123456789012333                                                                                                                                                                                                                                                                                                                                                                                                                    |
| iban    | International Bank Account Number as an ISO 13616:2007 identifier, case sensitive. This scheme is provided for convenience. You may prefer use the BAN scheme instead. A receiver system that supports IBAN-based identification of its managed accounts should also support BAN-based identification for those same accounts. Data format: alpha-numeric, max length: 34 Example: iban:CH5108686001256515001                                                                                                                                                                                                                                                                                |
| ban     | Bank Account Number A bank account number (BAN) identifier, formed by the account number (its format depends on the bank involved) and the bank identifier code (BIC). This scheme is suitable to identify most bank accounts worldwide, contrary to the IBAN scheme, which is mostly limited to European bank accounts. The BIC is formed by 8 uppercase alpha numeric characters, optionally followed by a 3 alpha numeric character branch code. Data format: alpha-numeric;bic=\<\<bic\>bic\> With \<\<bic\>bic\> matching the ISO 9362 standard, in uppercase Example: ban:30056001140114000251817;bic=CCFRFRPP                                                                         |
| ewallet | E-Wallet account identifier As there is no standard to identify an e-wallet account globally, the payment provider must decide with its SP what the exact format of such an ID will be. To help keep the format simple and avoid collisions between SP's local identification convention, an additional URI parameter named 'sp' may be used, identifying the e-wallet account provider. With such a model, each SP can keep its local e-wallet identification scheme and transpose it transparently. Data format: alpha-numeric Example: Using the sp URI parameter: ewallet:user011;sp=paypal Using a naming conventions (not transparent for the SP): ewallet:paypal_user011 ewallet:     |