# Additional Data Fields source: https://developer.mastercard.com/cross-border-services/documentation/additional-resources/common-additional-data/index.md Receiving Institutions may require additional data from the Originating Institution in the API calls that are not standard for all calls. Note: This following list contains the additional_data fields that might be required. Actual fields required for each corridor are provided in the Originating Institution's Technical Endpoint Guide (TEG) during the onboarding process. The field names are the numbers provided in the "Data Field Name" column below. For example, the 1200 field name would be formatted as below: ```XML 1200 123COM-WE-MWALLET ``` ##### ++Request API Call Additional Data Fields++ {#urequest-api-call-additional-data-fieldsu} | Data Field Name | Additional Data | Field Description | |-----------------|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 108 | Sender Alias (other) | Sender's formal alias name, as provided by the OI in case of consumer type. Latin characters only. Note: This field shall serve the Singapore alias name scenario, where 20% of the Singaporean individuals have a formal alias on their ID card. | | 121 | Sender Mobile Phone Number | Sender's mobile number, as provided by the sender, as a E164 number (digits only, no hyphenation). This is usually a contact number, and may be different from the source URI that may identify an independent mobile wallet. Example: +33612345678 | | 122 | Sender Landline Number | Sender's landline number, as provided by the sender, as a E164 number (digits only, no hyphenation). This is usually a contact number, and may be different from the source URI that may identify an independent mobile wallet. Example: +33612345678 | | 125 | Sender E-mail address | Example: [sender1@gmail.com](mailto:sender1@gmail.com) | | 153 | Sender ID Issued by | Sender's ID issuing authority. May contain [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Example: Passport office | | 161 | Sender Place of Birth | Sender's place of birth, as mentioned on his/her official ID documents. Free string, [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Example: Toulouse, France | | 170 | Sender Occupation | Sender's occupation (job/position). Free string, [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Valid Values: General Worker, Businessman, Professional, Supervisor, Tourist, Security Guard, House Maid, Domestic Helper, House Wife, Others | | 180 | Sender Relationship with Beneficiary | Sender relationship with recipient. **Valid Values** : Parent, Child, Spouse, In-laws, Relative, Self, Family Friend, Employee, Friend, Supplier, Service Provider, Donor/ Receiver of Charitable Funds, Trade/ Business Partner. | | 204 | Organization Name (other) | Receiver/beneficiary's name when it is a business, as provided by the sender. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Spare field (in case RI is expecting the beneficiary's name in 2 different languages). Allowed structure in case of Consumer:Note: First_Name and Last_Name are required, Middle_Name is optional. Allowed structure in case of Business, Government/Non-Government Organization | | 205 | Receivers First name (other) | Recipient's first name, as provided by the sender. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Spare field (in case RI is expecting the beneficiary's name in 2 different languages). | | 206 | Receivers Middle Name (other) | Recipient's middle name, as provided by the sender. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Spare field (in case RI is expecting the beneficiary's name in 2 different languages). | | 207 | Receivers last Name (other) | Recipient's last name, as provided by the sender. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Spare field (in case RI is expecting the beneficiary's name in 2 different languages). | | 208 | Recipient Alias (other) | Recipient 's formal alias name, as provided by the OI in case of consumer type. Latin characters only. Note: This field shall serve the Singapore alias name scenario, where 20% of the Singaporean individuals have a formal alias on their ID card. | | 222 | Recipient landline number | Recipient's landline number, as provided by the sender, as a E164 number (digits only, no hyphenation). Example: +33412345678 | | 253 | Recipient ID Issued By | Recipient's ID issuing authority. May contain [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Example: Passport office | | 260 | Recipients Date of Birth | Recipient's date of birth. In case of Business, Government/Non-Government Organization: Established Date | | 261 | Recipient Place of Birth | Recipient's place of birth, as mentioned on his/her official ID documents. Free string, [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Example: Toulouse, France | | 270 | Recipient Occupation | Recipient's occupation (job/position). Free string, [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. Example: Laborer | | 409 | Additional Communication | Additional Information field. A free communication field (structured or unstructured) as provided by the sender. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. | | 430 | Payer Payee Relationship | This field will capture Payer Payee relationship. Free string, [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. **Valid values for P2P payments:** Father, Mother, Daughter, Son, Parent, Child, Sibling, Spouse, Sister, Brother, Wife, Husband, Father-in-Law, Mother-in-Law, Aunty, Uncle, Cousin, Nephew, Niece, Grand Mother, Grand Father, Grand Daughter, Grand Son, Friend, Friend's Mother, Friend's Father, Self **Valid values for B2B payments:** Supplier, Service Provider, Trading partner, Business Partner, Outsourcing, Importer/Exporter, Seller, Buyer **Valid values for B2P payments:** Consultant, Contractor, Employee **Valid values for P2B payments:** Importer/Exporter, Seller, Buyer | | 511 | Future Processing Date | Customer who would like to use the payment scheduling service must provide a future processing date in this field. The date must be within the min and max day interval which is 7 to 14 days. The date must be in yyyy-mm-dd format. Example 2024-08-01 | | 520 | Recipient Notification | Consent to send recipient notification for a transaction. | | 630 | Beneficiary Bank Account Type | Beneficiary Account Type (Requirement for Brazil and Ecuador). **Valid Values:** C = Checking P = Savings | | 650 | Sender Bank Region | This parameter contains the region of the bank institution from which the sending consumer is instructing the transaction. This parameter holds a string of [alphanumeric special](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters with a maximum length of 64 and a minimum length of 1. Example: 69999 | | 660 | Recipient Bank Region | This parameter contains the region of the bank institution to which the recipient consumer is receiving the transaction. This parameter holds a string of [alphanumeric special](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters with a maximum length of 64 and a minimum length of 1. Example: 69999 | | 701 | Destination Country | Destination Country ISO 3166-Alpha-3 country code, in uppercase. Example: FRA | | 1150 | Debtor Agent Name | Debtor Agent Name (typically used for a Payment On Behalf Of (POBO) scenario) | | 1154 | Debtor Agent Address Street 1 | Debtor Agent Address Street 1: street name/number. [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. | | 1155 | Debtor Agent Address Street 2 | Debtor Agent Address Street 2: street name/number. (field reserved for systems which split street address in 2 lines) [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. | | 1156 | Debtor Agent Address City | Debtor Agent Address City [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. | | 1157 | Debtor Agent Address Zip | Debtor Agent Address ZIP code ASCII characters only. | | 1158 | Debtor Agent Address State | Debtor Agent Address State [Unicode](https://developer.mastercard.com/cross-border-services/documentation/api-basics/api-conventions/index.md) characters. | | 1159 | Debtor Agent Address Country | Debtor Agent Address Country. This VSF encodes this information as a ISO 3166 Alpha-3 country code, in uppercase. Example: FRA | | 1160 | Ultimate Debtor Name | Name of the party that originally ordered goods or services and to whom the seller has sent the invoice. Ultimate Debtor is used to identify the party that originally ordered goods or services and to whom the seller has sent the invoice. Ultimate Debtor is used when the receiver of the invoice is different than the Debtor (Sender Name). | | 1161 | Intermediary Agent 1 Name | The name of the first Financial institution between the debtor's agent and the creditor's agent. There can be several intermediary agents specified for the execution of a payment. There can be one to many intermediary agents specified for the execution of a payment. | | 1162 | Intermediary Agent 2 Name | The name of the second Financial institution between the debtor's agent and the creditor's agent. There can be several intermediary agents specified for the execution of a payment. If needed. | | 1163 | Intermediary Agent 3 Name | The name of the third Financial institution between the debtor's agent and the creditor's agent. There can be several intermediary agents specified for the execution of a payment. If needed. | | 1200 | Destination Service Tag | The Destination Service tag value provided by Mastercard Cross-Border Services at time of onboarding; ensures transactions are delivered to preselected corridors. Free text. | | 7260 | Destination Payment Instrument | The destination payment instrument. **Valid values (in uppercase):** BANK, CARD, EWALLET, MWALLET, CASH and BANKWIRE | ##### ++Response API Call Additional Data Fields++ {#uresponse-api-call-additional-data-fieldsu} | Data Field Name | Additional Data | Field Description | |-----------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 501 | Maximum Cash Pickup Duration | Maximum amount of time the receiver has to pick up the funds prior to the transaction being rejected. Always expressed in number of days. "XXX days" (where the X is represents a number). Only provided on a payment response for a Cash Out transaction. Format: ANS - 10 Example: 30 days | | 814 | Mastercard Trading Rate | Value that represents the Mastercard Trading Rate for the transaction. This element will ONLY be provided on payment response messages for Mastercard OIs who have been configured to receive it. This is the rate used for transaction processing minus OI or Mastercard Cross-Border Services markup. Decimal value with a maximum length of 24 and a minimum length of 1. | | 830 | Rate ID | This field will only be provided on Payment responses when an OI has opted in for Carded Rates and is configured for "Expired Rate" processing. This is the "Rate ID" associated to the rate utilized to process the payment. This field is used in conjunction with Expired Rate Indicator field (831) defined below. When Additional Data 831 = **RATE_HONORED** , the value in the Rate ID field will be the same as the value provided by the OI in the card_rate_id field of the payment request. When Additional Data 831 = **RATE_EXPIRED**, the value in the Rate ID field will be different than the value provided by the OI in the card_rate_id field of the payment request. In this case, the value in this field will represent the card rate ID associated to the rate used on the payment. | | 831 | Expired Rate Indicator | This field will only be provided on Payment responses when an OI has opted in for Carded Rates and is configured for "Expired Rate" processing. Indicator telling whether the value provided in the card_rate_id field of the payment request was honored or expired. This also indicates if the settlement amount in the payment response was recalculated as part of Expired Rates processing or not. This indicator is used in conjunction with the Rate ID field (830) defined above. Valid Values: **RATE_HONORED** : The rate ID from the card_rate_id field of the payment request was still valid when the payment was processed and was honored (used for payment processing). **RATE_EXPIRED**: The rate Id from the card_rate_id field of the payment request was no longer valid when the payment was processed and a new FX rate has been applied. The new FX rate created a new settlement amount for the payment that was processed. | | 840 | Quote ID | This field will only be provided on Quote and Payment responses when an OI is configured for "Expired Quote" processing. This is a "Quote ID" provided for each quote and payment response as part of expired quote processing. This value can be used by an OI if they need to have a unique value for backend processing or trading associated to each transaction. This field is used in conjunction with Expired Quote Indicator field (841) described below. When Additional Data 841 = **QUOTE_HONORED** , the value in the Quote ID field will be the same in the Quote and Payment response. When Additional Data 841 = **QUOTE_EXPIRED** , the value in the Quote ID field of the payment response will be different than the value provided in the Quote response. When there is a new (different) value provided in the payment response, the OI may use this new value in any backend process required to support the new settlement amount calculated as part of expired quote processing. | | 841 | Expired Quote Indicator | This field will only be provided on Payment responses when an OI is configured for "Expired Quote" processing. Indicator telling whether the proposal in the Quote used on the payment was honored or expired. This also indicates if the settlement amount in the payment response was recalculated as part of Expired Quote processing or not. This field is used in conjunction with Quote ID field (840) described above. Valid Values: **QUOTE_HONORED** : The rate from the proposal in the Quote was still valid when the payment was processed and was honored (used for payment processing). **QUOTE_EXPIRED**: The rate from the proposal in the Quote was no longer valid when the payment was processed and a new FX rate has been applied. The new FX rate created a new settlement amount for the payment that was processed. | | 890 | Max queue time | Maximum amount of time by when enough balance must be added to settlement account prior to the transaction being rejected. It holds timestamp in format yyyy-MM-dd'T'HH:mm:ssXXX. Example - 2023-07-07T12:38:10Z |