# Sender Account URI source: https://developer.mastercard.com/cross-border-services/documentation/additional-resources/common-sender-acct-uri/index.md For all transactions, including nested payments, the Sender Account URI scheme is a mandatory field based on the account that is initiating the transaction and must contain the ultimate sender's unique account details for the actual mobile wallet, ewallet, account identifier, bank account or card that is initiating the transaction. Accordingly, this field should not include a blanket or general account managed by the Debtor Agent. Where a bank account is the account type initiating the transaction, the international bank account number (iban) or bank account number (ban) scheme must be provided. If the initiating account is not tel, iban, or ban, then the ewallet scheme may be used. In such cases, the URI should be an identifier of the person transacting, such as the unique ID of the sender in the OI's system. | 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 | | | 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 | | 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 | | 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\> With \<\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 Examples: Using the sp URI parameter: ewallet:user011;sp=paypal Using a naming convention (not transparent for the SP): ewallet:paypal_user011 ewallet: | The platform will add the following VSF fields along with mentioned validator, and the Mexico service provider will be set up for them in accordance with the specifications below. Newly added VSFs, below are the required details: | Vendor ID | Field ID | Description/Format | Minimum Length | Maximum Length | Validator | Validation/Format | Typical Scope | Example | |-----------|----------|----------------------------------------------------------------------------------------------------------------------------|----------------|----------------|----------------------------|-----------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------| | 2390 | 109 | Gender | 1 | 2 | \^\[MFO\]$ | Must support 2 digit value Must accept M for Male F for Female O for Other/ not disclose | Network provided, from HES requests. | | | 2390 | 117 | PIN Number | 1 | 40 | \^\\d{1,40}$ | Must support only Numeric characters. Must not support the special characters. | Network provided, from HES requests. | 123126367363277121 | | 2390 | 118 | Address in Mexico or foreign country: Exterior number | 1 | 40 | \^\[\\w\\W\]{1,40}$ | Must support only Alphanumeric characters. Must support the special characters. | Network provided, from HES requests. | This refer as street number e.g. Basilica DE GPE- 1232 | | 2390 | 119 | Address in Mexico or foreign country: Interior number | 1 | 40 | \^\[\\w\\W\]{1,40}$ | Must support only Alphanumeric characters. Must support the special characters. | Network provided, from HES requests. | This is refer as apartment name \& number e.g.- Nido condos-26 | | 2390 | 124 | Federal Entity of Birth (State) | 1 | 50 | \^\[A-Z\]{3}\[A-Z\]{1,50}$ | Must apply the validation of the state fields which are existing e.g. VSF114 \& VSF214 | Network provided, from HES requests. | Michoacan | | 2390 | 142 | Delegation, municipality or political demarcation | 1 | 200 | \^\[\\w\\W\]{1,200}$ | Must apply the existing address line 2 payment.sender.address.line2 available in API request. | Network provided, from HES requests. | Behind Nido Condos, near church | | 2390 | 195 | Advanced Electronic Signature serial number | 1 | 200 | \^\[\\w\\W\]{1,200}$ | N.A. | Network provided, from HES requests. | N.A. | | 2390 | 196 | Address in Mexico or foreign country: Exterior number (Person who performed the transaction on behalf of the Legal Entity) | 1 | 40 | \^\[\\w\\W\]{1,40}$ | Must support only Alphanumeric characters. Must support the special characters. | Network provided, from HES requests. | This refer as street number e.g. Basilica DE GPE- 1232 | | 2390 | 197 | Address in Mexico or foreign country: Interior number (Person who performed the transaction on behalf of the Legal Entity) | 1 | 40 | \^\[\\w\\W\]{1,40}$ | Must support only Alphanumeric characters. Must support the special characters. | Network provided, from HES requests. | This is refer as apartment name \& number e.g.- Nido condos-26 | | 2390 | 199 | Federal Entity | 1 | 50 | \^\[A-Z\]{3}\[A-Z\]{1,50}$ | Must apply the validation of the state fields which are existing e.g. VSF114 \& VSF214 | Network provided, from HES requests. | Michoacan | | 2390 | 918 | Delegation, municipality or political demarcation (Person who performed the transaction on behalf of the Legal Entity) | 1 | 200 | \^\[\\w\\W\]{1,200}$ | Must apply the existing address line 2 payment.sender.address.line2 available in API request. | Network provided, from HES requests. | Behind Nido condos, near church |