Legacy site security

currencyiso3a = GBP
mainamount = 100.00
sitereference = test_site12345
password = PASSWORD

Using this example, we would have the following string generated:

GBP100.00test_site12345PASSWORD

(Any blank fields are omitted from the hash)

When generating the hash, the fields must be in the same order as listed above. If the fields are not in the correct order, the request will fail.

The order in which fields are hashed can be changed if required. Please contact the Support team for assistance.

The password field must always be the last field in the string used to generate the hash. It cannot be re-positioned among the other fields or removed entirely.

If a field included in the hash has multiple values, these values are concatenated in the order submitted in the POST.

Consider the following additional fields:
ruleidentifier=STR-7&ruleidentifier=STR-6

When included in the string generated above, it becomes:
GBP100.00test_site12345STR-7STR-6PASSWORD

Example string:

GBP100.00test_site12345PASSWORD

Hashing using SHA-256 will leave us with the following hash:

479d0850496e3d911c442a40324140a1774580cc92219110fcfdb3345f06577e

You can use the following code examples as a reference when generating your hash:

#!/usr/bin/python

import hashlib
stringToHash= "GBP100.00test_site12345PASSWORD"
print hashlib.sha256(stringToHash).hexdigest()

<?php
echo hash("sha256", "GBP100.00test_site12345PASSWORD");
?>

import java.math.BigInteger;
import java.security.MessageDigest;
public class mysha256 {
    public static void main(String args[]) throws Exception {
	String stringToHash = "GBP100.00test_site12345PASSWORD";
	MessageDigest digestObj = MessageDigest.getInstance("SHA-256");
	digestObj.update(stringToHash.getBytes("UTF-8"));
	String merchantHash = String.format("%064x",new BigInteger(1,digestObj.digest()));
	System.out.println(merchantHash);
    }
}

#!/usr/bin/perl

use Digest::SHA qw(sha256_hex);
$stringToHash = "GBP100.00test_site12345PASSWORD";
$merchantHash = sha256_hex($stringToHash);
print $merchantHash;

Failure to do so could invalidate the hash and stop legitimate transactions.

g479d0850496e3d911c442a40324140a1774580cc92219110fcfdb3345f06577e

This is the final value that would need to be submitted in the sitesecurity field for this transaction.

This is to ensure the correct version of the site security feature is used.

Failure to do so could invalidate the hash and stop legitimate transactions.