RDX Specification

InitiateActionRequest.MerchantInfo (Object)

NameDescriptionTypeLengthRequired
AcquirerIdAcquirerId for the merchant performing the purchase request.StringUp to 11 charactersOptional
AcquirerCountryCodeCountry code of the Acquirer. ISO 3166-1 Numeric format.

Issuers need to be aware of the Acquirer Country Code when the acquirer country differs from the merchant country and the acquirer is in the EEA (this could mean that the transaction is within the European Economic Area).

Note: Currently only available on EMV 3DS for Visa and Mastercard and 3DS 1.0 Visa transactions when data is present and PSD2 flag is enabled.
StringUp to 3 charactersOptional
MerchantId Merchant ID for the merchant performing the purchase request.StringUp to 35 charactersOptional
MerchantName Merchant name for the merchant performing the purchase request.StringUp to 40 charactersOptional
MerchantURL URL or App Name for the merchant performing the purchase request.StringUp to 2048 charactersRequired
MerchantCategoryCode Code used to describe the merchant’s type of business product or service that is payment network specific. Please refer to each payment network for more details.StringUp to 4 charactersOptional
MerchantCountryCode Country code of the merchant: 3-digit numeric format; e.g. 840StringUp to 3 charactersOptional
MerchantAppRedirectURL Merchant app declaring their URL within the CReq message so that the Authentication app can call the Merchant app after OOB authentication has occurred. Each transaction requires a unique Transaction ID by using the SDK Transaction ID. VCAS will validate the value to ensure it contains a scheme which will route the authentication app to the associated merchant app.

Example: merchantScheme://appName?transID=b2385523-a66c-4907-ac3c-91848e8c0067
StringUp to 256 charactersOptional