On This Page

{#jumplink-list}  
[Markdown](/docs/vas/en-us/api-fields/reference/all/rest/api-fields/merch-defined-info-aa/merch-defined-info-key.md)  
Filter  
FILTER BY TAG

merchantDefinedInformation\[\]. key {#merchant-defined-info-key}
================================================================

The number you assign as the key for your merchant-defined data field.  
This topic describes the sequence of fields from merchantDefinedInformation\[0\].key through merchantDefinedInformation\[100\].key.

> IMPORTANT
> When you include this field in a request, you must also include the corresponding merchantDefinedInformation\[\].value field, which contains the value that corresponds to the merchantDefinedInformation\[\].key field.
> WARNING
> Merchant-defined data fields are not intended to and must not be used to capture personally identifying information. Accordingly, merchants are prohibited from capturing, obtaining, or transmitting any personally identifying information in or through the merchant-defined data fields. Personally identifying information includes, but is not limited to, address, payment card number, social security number, driver's license number, state-issued identification number, passport number, and card verification numbers (CVV, CVC2, CVV2, CID, CVN). In the event ` Visa Acceptance Solutions ` discovers that a merchant is capturing or transmitting personally identifying information through the merchant-defined data fields, whether or not intentionally, ` Visa Acceptance Solutions ` will immediately suspend the merchant's account, which will result in a rejection of any and all transaction requests submitted by the merchant after the point of suspension.
> **Payer Authentication**  
> Only fields 1 through 5 are supported in Payer Authentication. The value appears in the Case Management Details window in the Business Center. The first four fields are the same fields that are used by the Secure Data services.  
> **`Visa Platform Connect`**  
> For installment payments with Mastercard in Brazil, use merchantDefinedInformation\[0\].key and merchantDefinedData_mddField_2merchantDefinedInformation\[1\].key for data that you want to provide to the issuer to identify the transaction.  
> For installment payments with Mastercard in Brazil:

* The value for merchantDefinedInformation\[0\].key corresponds to the following data in the TC 33 capture file:
  * Record: CP07 TCR5
  * Position: 25-44
  * Field: Reference Field 2
* The value for merchantDefinedInformation\[1\].key corresponds to the following data in the TC 33 capture file:
  * Record: CP07 TCR5
  * Position: 45-64
  * Field: Reference Field 3

Specifications {#merchant-defined-info-key_Specifications}
----------------------------------------------------------

* **Installment payments with Mastercard on `Visa Platform Connect` in Brazil:**
  * **Data Type:** String
  * **Data Length:** 20
* **All other transactions:**
  * **Data Type:** String
  * **Data Length:** 50

Mapping Information {#merchant-defined-info-key_Mapping}
--------------------------------------------------------

* **REST API Field:** merchantDefinedInformation\[\].key
* **SCMP API Field:** merchant_defined_data1 through merchant_defined_data100
* **Simple Order API Field:** merchantDefinedData_mddField_1 through merchantDefinedData_mddField_100  
  RELATED TO THIS PAGE