On This Page
REST API

merchantDefinedSecureInformation[]. key

Name that you assign as the key for your merchant-defined secure data field.
This field is available only on the
Visa Platform Connect
 processor.
You can pass up to four merchant-defined secure data fields in a single authorization request. To add merchant-defined secure data to a request, include an optional array of up to four name-value pairs.
Cybersource
 encrypts the data before storing it in the payments repository.
This topic describes the sequence of key fields from
merchantDefinedSecureInformation[1].key
 through
merchantDefinedSecureInformation[4].key
.
IMPORTANT
When you include this field in the request, you must also include the corresponding
merchantDefinedSecureInformation[].value
 field, which contains the secure value that corresponds to this field.
For each secure data field to be passed in the request, add two
REST
 API fields in the form illustrated in this example: 
"merchantDefinedSecureInformation": [
	{
		“key”: “1”,
		“value”: “XXXXXXXXXXXXXXXXXXXXXXXXXXXX5627::|6703611202308240110111111”
	},
	{
		“value”: “XXXXXXXXXXXXXXXXXXXXXXXXXXXX5627::|6703611202308240110222222”,
		“key”: “2” 
	},
	{
		“key”: “3”,
		“value”: “XXXXXXXXXXXXXXXXXXXXXXXXXXXX5627::|6703611202308240110333333”
	},
	{
		“key”: “4”,
		“value”: “XXXXXXXXXXXXXXXXXXXXXXXXXXXX5627::|6703611202308240110444444”
	}
]

Specifications

  • Data Type:
     String
  • Data Length:
     100

Mapping Information

No corresponding fields.