This page accepts an example transaction and signature key and will then show step by step how to create the signature that should be passed to the gateway with the transaction. This signature ensures that the transaction has not been tampered with during transmission.
Signatures are especially important when a transaction is stored on a payment form in hidden fields as the shopper can easily use tools built into their browser to modify these hidden fields and change things like the amount they should be charged etc.
Please POST your sample transaction to this page. Your test signature key must be passed in the URL 'key' parameter.
For example:
<form action="https://mms.cardstream.com/devtools/sigtest.php?key=MySecretKey" method="POST">
<input type="hidden" name="action" value="SALE">
<input type="hidden" name="type" value="1">
<input type="hidden" name="currencyCode" value="826">
<input type="hidden" name="countryCode" value="826">
<input type="hidden" name="amount" value="2512">
<input type="hidden" name="transactionUnique" value="55f01b80eda38">
<input type="hidden" name="orderRef" value="Signature Test">
<input type="hidden" name="cardNumber" value="4929 4212 3460 0821">
<input type="hidden" name="cardExpiryDate" value="1213">
<input type="submit" value="Submit">
</form>
Note: This page is for debugging and development purposes only and should not be used in a live environment to actually calculate the signature. The sample PHP code, or equivalent code in the developers preferred language, should be used. The signature key used with this script should be a test key used during development and not the actual key used in production so that the production key remains a secret and, unlike this page, is never transmitted with the actual transaction.
1SHA-512 is the preferred hashing algorithm but others are allowed if your chosen development language doesn't have a convenient way to do SHA-512 hashing. Please refer to the integration guides on how to use other algorithms.