If your Payment Pages looks like:
Or if your HTTPS POST includes version=1
You’re on version 1
Please follow the steps below to benefit from the new features available.
If your Payment Pages looks like:
Or if your HTTPS POST includes version=2
You’re on version 2
You’re all set!
To migrate from Payment Pages version 1 to version 2, you will need to make the following changes to your existing HTTPS POST:
- Change “version” from “1” to “2”.
- Submit an additional field “stprofile” with a value of “default”.
When getting started with version 2, perform these changes on your test site reference and ensure the appearance and behaviour is as expected before making changes to your live site reference.
The following is an example of an HTTPS POST to Payment Pages version 2:
<form method="POST" action="<DOMAIN>/process/payments/choice">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="currencyiso3a" value="USD">
<input type="hidden" name="mainamount" value="100.00">
<input type="hidden" name="version" value="2">
<input type="hidden" name="orderreference" value="myorder12345">
<input type="submit" value="Pay">
</form>
Replace <DOMAIN> with a supported domain. Click here for a full list.
Customisation
In Payment Pages version 2, we have improved how you can customise the appearance and layout of your pages, allowing for greater flexibility.
New features supported:
- Use custom HTML to perform advanced customisation on the payment pages.
- The ability to implement different stprofiles, which allow you to switch between different layouts on your payment pages on a request-by-request basis.
If you have already implemented custom CSS on your Payment Pages, you will need to make changes to your CSS to support version 2. Click here to get started.
