ST2K to STPP Payment Pages Migration Guide
Document which details the steps to migrate from ST2K to STPP.
Version: 1.1
Published: 29 April 2015
ST2K to STPP Payment Pages Migration Guide
1
Introduction
To migrate your Payment Pages solution from the legacy ST2K platform to our new STPP
platform, there are a few key aspects to consider:
Changing the URL and fields used for sending the customer to Payment Pages.
“Callbacks” under ST2K are now “Notifications” and “Redirects” under STPP.
Merchant and customer emails are handled using the STPP “Notifications”.
Customisation is now made using CSS instead of HTML.
This document aims to address these points to ensure the migration process is easy to
understand and implement.
2
Posting information to Payment Pages
When migrating to STPP, you will need to modify the HTTPS POST used to transfer your
customers to the Payment Pages.
2.1
URL
The URL to transfer the customer’s browser has changed:
ST2K
<form method="POST"
action="https://securetrading.net/authorize/form.cgi"
STPP
<form method="POST"
action="https://payments.securetrading.net/process/payments/choice">
By sending the customer’s browser to the “Choice” page (using the new URL above), the
customer can select their preferred payment method (as shown in the screenshot below) and
proceed to the ”Billing details” page.
Your system will also need to submit different fields in the HTTPS POST, as outlined overleaf.
© Secure Trading Limited 2015
29 April 2015
Page 2 / 8
ST2K to STPP Payment Pages Migration Guide
2.2
Fields
When submitting the HTTPS POST to Secure Trading, please note the following differences
to the required hidden fields:
ST2K
<input type=hidden name="merchant" value="your-site-reference">
<input type=hidden name="currency" value="transaction-currency">
<input type=hidden name="amount" value="transaction-amount">
STPP
<input
<input
<input
<input
type=hidden
type=hidden
type=hidden
type=hidden
name="sitereference" value="your-site-reference">
name="currencyiso3a" value="transaction-currency">
name="mainamount" value="transaction-amount">
name="version" value="1">
On the legacy ST2K platform, the amount was submitted in base units:
£12.34 >>> “amount”=”1234”
On the new STPP platform, the amount is to be submitted in main units:
£12.34 >>> “mainamount”=”12.34”
Ensure your transactions are authorised for the amount expected during testing.
There is a new field called version. Your system must always include this and the value must
always be “1”.

A full list of STPP fields can be found in the Payment Pages Setup Guide.
All Secure Trading documents can be found on our website.
An example orderpage.html file can be downloaded from our website
http://www.securetrading.com/support/download/order-page-html-example/
© Secure Trading Limited 2015
29 April 2015
Page 3 / 8
ST2K to STPP Payment Pages Migration Guide
2.2.1
Security
Site Security users will need to note the following changes. The field name has changed as
follows:
ST2K
<input type=hidden name="st_sitesecurity" value="security-hash">
STPP
<input type=hidden name="sitesecurity" value="security-hash">
In addition, please note that the hash generated will differ because the other field names have
changed.
ST2K required merchants to hash the value using md5 algorithm.
STPP has been upgraded to use sha256 (for increased security).
© Secure Trading Limited 2015
29 April 2015
Page 4 / 8
ST2K to STPP Payment Pages Migration Guide
3
Notifications and Redirects
On ST2K, you may have used a feature called “Callback” in order to send updates to your
system and/or redirect the customer’s browser to your website following payment.
3.1
Notifications
On STPP, “Notifications” are used instead of “Callbacks” to send updates to your system. To
configure, please sign in to MyST and supply the URL for the POST with the fields that you
wish to receive.
Benefits
A benefit of using “Notifications” is that STPP can be to configured to resend failed
notifications for up to 48 hours, whereas ST2K would not retry failed “Callbacks”.
You can configure exactly when notifications are triggered through the use of
customised filters.
Configuration
The process of setting up notifications involves the following main steps:
Selecting the correct Site Reference.
Defining filters – conditions that trigger the sending of notifications when met.
Defining destinations – where and how notifications will be sent.
Assigning filters to destinations – creating the rules linking the filter and
destination.
2
1
5
3
6
4
When you sign in to MyST, click “Notifications” from the left side-bar.
You can view notifications for different sites by using the drop-down menu at the top of the
page, and clicking “Change site”
1
.
You can define new filters and destinations by using the buttons provided
Notifications are set up by assigning filters
3
to destinations
4
2
.
.
Notifications are turned on/off by selecting/de-selecting checkboxes in the “Active” column
Notifications can be deleted by highlighting the checkboxes in the “Delete” column
6
5
.
When you have finished making your changes, click “Save”.
© Secure Trading Limited 2015
29 April 2015
Page 5 / 8
ST2K to STPP Payment Pages Migration Guide
3.2
Merchant and Customer Emails
Configuring emails to be sent out after a transaction is completed is also handled by the
“Notification” system. This includes merchant and/or customer emails.
3.3
Redirects
The ST2K platform required you to utilise callbacks to redirect the customer's browser
following payment. The STPP platform however has a “Redirect” feature specifically for this
purpose. To configure, please sign in to MyST and supply the URL and fields required and
STPP will automatically perform the redirect at the end of specified transactions.
Configuration
1
2
5
4
3
When you sign in to MyST, click “Payment pages redirects” from the left side-bar.
You can view redirect rules for different sites by using the drop-down menu at the top of the
page, and clicking “Change site”
1
.
You can define new conditions and actions by using the buttons provided
Redirects are set up by linking conditions
3
to actions
4
2
.
.
Redirects are turned on/off by selecting/de-selecting checkboxes in the “Active” column
Redirects can be deleted by highlighting the checkboxes in the “Delete” column
6
5
.
When you have finished making your changes, click “Save”.

For a full tutorial on configuring Notifications and Redirects for Payment Pages,
please refer to the MyST User Guide.
All Secure Trading documents can be found on our website.
© Secure Trading Limited 2015
29 April 2015
Page 6 / 8
6
ST2K to STPP Payment Pages Migration Guide
4
Customisation
On ST2K, customisation involved editing and maintaining HTML pages and text documents.
On the new STPP platform, customisation is achieved by uploading CSS files using the File
Manager in MyST.

For information on the MyST File Manager, please refer to the MyST User Guide.
All Secure Trading documents can be found on our website.
Once your CSS files have been uploaded, you can pass a hidden field in the HTTPS POST to
“enable” the CSS, as follows:
Parent CSS
<input type="hidden" name="parentcss" value="nameofcssfile" />
Child CSS
<input type="hidden" name="childcss" value="nameofcssfile" />
You can modify the parent CSS file to make significant changes to your Payment Pages, or
modify the child CSS file to make more minor changes to the existing Secure Trading
template (e.g. add your own company logo).
4.1
CSS Examples
Child CSS examples can be downloaded from our website here:
http://www.securetrading.com/support/download/payment-pages-child-css-example/
You can also download a copy of our Parent CSS from our website:
http://www.securetrading.com/support/download/parent-css-default/
© Secure Trading Limited 2015
29 April 2015
Page 7 / 8
ST2K to STPP Payment Pages Migration Guide
5
Additional notes
5.1
Automated transaction checks
Secure Trading provides merchants with services to help reduce fraud and chargebacks,
which can be enabled/disabled by the support team. When migrating to STPP, we
recommend contacting Secure Trading Support to establish which transaction checks are
enabled on your account ([email protected]).
5.2
Testing
You will be provided with a “test” site reference and a “live” site reference. On STPP, all test
site references are preceded with the word “test_” (e.g. “test_merchant12345”). Secure
Trading recommends you test your solution thoroughly before processing live transactions.
Your test site references will always be available for you to process test transactions, even
after going live.
Please refer to the Testing document for further information:
http://www.securetrading.com/files/documentation/STPP-Testing.pdf
5.3
Further reading
For a full guide on configuring the Payment Pages on the STPP platform, please refer to the
Payment Pages Setup Guide. This can be downloaded from the following URL:
http://www.securetrading.com/sites/default/files/downloads/ppages/STPP%20Payment%20Pa
ges%20Setup%20Guide.pdf
© Secure Trading Limited 2015
29 April 2015
Page 8 / 8