Authentication
All requests must specify which Merchant Account they are for, using the merchantID request field. In addition to this, the following security measures can be used:
Password Authentication
You can configure a password for each Merchant Account, using the Merchant Management System (MMS). This password must then be sent in the merchantPwd field in each request. If an incorrect password is received by the Gateway, then the transaction will be aborted, and an error response is returned.
Warning: Use of a password is discouraged in any integration where the transaction is posted from a form in the client browser as the password may appear in plain text in code.
Message signing
You can configure a signing secret phrase for each Merchant Account using the Merchant Management System (MMS). When configured, each request will need to be ‘signed’ by providing a signature field containing a hash generated from the combination of the serialised request and this signing secret phrase. On receipt, the Gateway will then re-generate the hash and compare it with the one sent. If the two hashes are different, then the request received must not be the same as that sent and so the contents must have been tampered with and the transaction will be aborted, and an error response is returned.
The Gateway will also return hash of the response message in the returned signature field, allowing you to create your own hash of the response (minus the signature field) and verify that the hashes match.
Message signing maybe mandatory on some Merchant Accounts and if so, the Merchant Management System will only allow the secret phrase to be changed but not removed entirely.
If message signing is enabled, then the data POSTed to any callback URL will also be signed.
See the Sample Signature Calculation section for information on how to create the hash.
Allowed IP addresses
You can configure a list of IP addresses using the Merchant Management System (MMS). Two different address lists can be configured, one for standard requests, such as sales: and one for advanced requests, such as refunds and cancellations. If a request is received from an address other than those configured, then it will be aborted, and an error response is returned.
\