The Merchant Preferences page is used to configure your merchant account integration preferences. The Preferences page contains the following sections:
For additional security you can sign your requests with a signature key which will be added to the end of a checksum for your request. This feature is mandatory and is pre-set to a randomly generated 'key' for each merchant account.
For further information and example of how to generate a signature, please see here.
For additional security a merchant can set an additional password in the MMS. This password must be sent along with any call to Gateway via the hosted or direct integration methods. This is an optional parameter.
Transaction actions such as Refunds, Captures, Cancels and manual authorisations can only normally be made through this application if the user has sufficient permissions. If you wish to send these operations via the Direct Integration method, you must set your IP address here, otherwise such operations received from non-authorised IP addresses will not be accepted.
Direct integration transactions require you to set your IP address here. Requests received from non-authorised IP addresses will not be accepted. Standard IPs can process Sales and Preauths, whilst advanced IP’s can process Refunds, Captures, Cancels and manual authorisations
IP address ranges can be specified using either hyphened ranges (188.8.131.52-184.108.40.206), wildcard addresses (1.2.3.*), CIDR addresses (220.127.116.11/24) or net-masks (18.104.22.168/255.255.255.0). Multiple IP addresses or IP address ranges can be separated by semicolons.
Merchant Category Code (MCC)
Merchants can provide or update their MCC. Merchant Category Codes (MCCs) are 4 digits long and used to identify the type of business in which a Merchant is engaged.
They are assigned to Merchants by their acquiring bank based on the type of product or service they provide. There are many MCCs used, and it is important for Merchants to make sure they are assigned to the appropriate code. Merchants need to enter an MCC to avoid their 3DSv2 transactions falling back to version 1.
Once Merchants have entered an MCC value, this field becomes mandatory and cannot be removed without a new code being entered.