After you have finished configuring your site and have tested thoroughly, follow the final steps below to begin processing live payments.
Before you continue…
Most acquiring banks mandate that 3-D Secure is performed prior to AUTH requests.
If 3-D Secure is not implemented, you could be liable for fines from the card schemes.
Ensure you have contacted your acquiring bank and have configured 3-D Secure, if required.
You must ensure your servers are PCI compliant before processing live payments.
For further information, we recommend contacting your acquiring bank.
You must read and ensure you have understood the practices outlined in our "Checks to perform following payment".
You must perform a full suite of test payments using all 3-D Secure v2 and 3-D Secure v1 cards provided on this page and ensure your system handles each scenario correctly and displays the correct message to the customer. Click here to open this in a new tab.
You must ensure your system can submit requests using your test sitereference (starts with “test_”) and handle both successful and failure responses before processing live payments.
Rules for live site reference
When you are ready to switch your account live, you will need to consider any Rules that may have been configured on your test Site Reference, as these will need to be re-configured on your live site reference to ensure they update your system as expected. Click here for our Rule documentation.
Get in touch
Once you have tested your system and received email confirmation that your account is ready to go live, contact our Support Team with your live site reference and request to go live. You will receive a response when your live site reference is ready to begin processing payments.
Only the authorised contact for the account can request for the site reference to go live.
Make changes to your requests
You will need to make the following changes to your payment form:
- Your will need to update the payment form so your live site reference is submitted in the sitereference field. Once this change has been made, requests will be processed as live requests.
- You will also need to ensure the payment form submits the field livestatus with value 1.
(Example)
<html>
<head>
</head>
<body>
<div id="st-notification-frame"></div>
<form id="st-form" action="https://www.example.com" method="POST">
<div id="st-card-number" class="st-card-number"></div>
<div id="st-expiration-date" class="st-expiration-date"></div>
<div id="st-security-code" class="st-security-code"></div>
<button type="submit" id="st-form__submit" class="st-form__submit">
Pay securely
</button>
</form>
<script src="<CDN_DOMAIN>"></script>
<script>
(function() {
var st = SecureTrading({
jwt: 'INSERT YOUR JWT HERE',
livestatus: 1
});
st.Components();
})();
</script>
</body>
</html>
The JavaScript Library is a managed service that is regularly updated to add new features and improve existing functionality. Because of this, the JavaScript Library must be retrieved for each payment request. Failure to do so may prevent your integration from working correctly and cause payment requests to fail.
Click here for a full list of domains and replace <CDN_DOMAIN> in the example above with the appropriate value for your integration.
Live testing
Once you have switched to your live site reference, we recommend that you test this by performing a transaction using a live card, to ensure it is processed successfully. You can sign in to Portal to manage your transactions. Therefore, you can cancel transactions processed on live cards.
You should not use the same live card too many times, as the requests may still be authorised, and could cause the issuer to suspect fraud or the cardholder could exceed their limit.
You’re all set!
Remember to sign in to Portal and check your transactions regularly to ensure payments are being processed successfully. If you need assistance, please contact our Support Team.
