Stop!
Do you meet these requirements?
In order to deploy Payment Pages for your own e-commerce solution, you will need to adhere to the following requirements:
-
You will need to open an account with Trust Payments (Visit our website to learn more and sign up)
- You will be sent two site references that your system will reference when processing payments;
- And also instructions for signing up for a Portal account. (Used for site configuration and managing transactions)
-
You will need an internet merchant account for processing live transactions.
-
Your firewall must be configured to allow connections from Trust Payments IP Ranges.
- You will need to ensure your solution is PCI compliant (click here to learn more).
Build the request to
Trust Payments
- Embed an HTML form on your website.
- Configure the form to submit an HTTPS POST request to our endpoint.
- Include required parameters in the request to customise the checkout session.
This integration method redirects the customer's browser to our secure hosted environment for payment processing. The customer enters their payment details on our secure servers, ensuring sensitive payment data is not transmitted to your systems.
The HTTPS POST request initiates the hosted payment session according to your specified criteria. After the transaction is complete, the customer's browser can be redirected back to your website based on the URLs you provide in the initial request.
Walkthrough
To get started, select your preferences below
Do you need Trust Payments to collect the customer's address during the session?
Are you shipping a product to your customers?
When the customer's browser is redirected back to your website following the processing of a transaction, the URL includes additional parameters to allow your frontend to display the appropriate content.
In addition to the above, you can also enable URL notifications to send transaction data directly to your server without involving the customer's browser. As a server-to-server communication, this makes it more secure and reliable, and is recommend for updating your backend systems. Would you like to enable this functionality too?
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="YOUR SITE REFERENCE">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="strequiredfields" value="customerfirstname">
<input type="hidden" name="strequiredfields" value="customerlastname">
<input type="hidden" name="strequiredfields" value="customerpremise">
<input type="hidden" name="strequiredfields" value="customerstreet">
<input type="hidden" name="strequiredfields" value="customertown">
<input type="hidden" name="strequiredfields" value="customercounty">
<input type="hidden" name="strequiredfields" value="customerpostcode">
<input type="hidden" name="strequiredfields" value="customercountryiso2a">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="YOUR EMAIL ADDRESS">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A111
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides both their billing and delivery addresses before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="strequiredfields" value="customerfirstname">
<input type="hidden" name="strequiredfields" value="customerlastname">
<input type="hidden" name="strequiredfields" value="customerpremise">
<input type="hidden" name="strequiredfields" value="customerstreet">
<input type="hidden" name="strequiredfields" value="customertown">
<input type="hidden" name="strequiredfields" value="customercounty">
<input type="hidden" name="strequiredfields" value="customerpostcode">
<input type="hidden" name="strequiredfields" value="customercountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A112
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides both their billing and delivery addresses before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="YOUR SITE REFERENCE">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="strequiredfields" value="customerfirstname">
<input type="hidden" name="strequiredfields" value="customerlastname">
<input type="hidden" name="strequiredfields" value="customerpremise">
<input type="hidden" name="strequiredfields" value="customerstreet">
<input type="hidden" name="strequiredfields" value="customertown">
<input type="hidden" name="strequiredfields" value="customercounty">
<input type="hidden" name="strequiredfields" value="customerpostcode">
<input type="hidden" name="strequiredfields" value="customercountryiso2a">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="YOUR EMAIL ADDRESS">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A121
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides both their billing and delivery addresses before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="strequiredfields" value="customerfirstname">
<input type="hidden" name="strequiredfields" value="customerlastname">
<input type="hidden" name="strequiredfields" value="customerpremise">
<input type="hidden" name="strequiredfields" value="customerstreet">
<input type="hidden" name="strequiredfields" value="customertown">
<input type="hidden" name="strequiredfields" value="customercounty">
<input type="hidden" name="strequiredfields" value="customerpostcode">
<input type="hidden" name="strequiredfields" value="customercountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A122
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides both their billing and delivery addresses before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
When the customer's browser is redirected back to your website following the processing of a transaction, the URL includes additional parameters to allow your frontend to display the appropriate content.
In addition to the above, you can also enable URL notifications to send transaction data directly to your server without involving the customer's browser. As a server-to-server communication, this makes it more secure and reliable, and is recommend for updating your backend systems. Would you like to enable this functionality too?
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="merchant@email.com">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A211
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides their billing address before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A212
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides their billing address before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="merchant@email.com">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A221
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides their billing address before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="25.00">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="strequiredfields" value="billingpremise">
<input type="hidden" name="strequiredfields" value="billingstreet">
<input type="hidden" name="strequiredfields" value="billingtown">
<input type="hidden" name="strequiredfields" value="billingcounty">
<input type="hidden" name="strequiredfields" value="billingpostcode">
<input type="hidden" name="strequiredfields" value="billingcountryiso2a">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: A222
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, the example includes strequiredfields to force the customer to enter their billing first name, last name and email address.
Postal Addresses
Don't worry about submitting the customer's address in the request. We will prompt the customer for this info on the checkout.
Note that the example includes strequiredfields to ensure the customer provides their billing address before they can complete the purchase.
How it looks
The field stprofile is used to customise the checkout appearance.
Leave as "default" for the standard preset.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
When the customer's browser is redirected back to your website following the processing of a transaction, the URL includes additional parameters to allow your frontend to display the appropriate content.
In addition to the above, you can also enable URL notifications to send transaction data directly to your server without involving the customer's browser. As a server-to-server communication, this makes it more secure and reliable, and is recommend for updating your backend systems. Would you like to enable this functionality too?
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="billingpremise" value="No 789">
<input type="hidden" name="billingstreet" value="Test Street">
<input type="hidden" name="billingtown" value="Bangor">
<input type="hidden" name="billingcounty" value="Gwynedd">
<input type="hidden" name="billingpostcode" value="TR45 6ST">
<input type="hidden" name="billingcountryiso2a" value="GB">
<input type="hidden" name="customerfirstname" value="Jay">
<input type="hidden" name="customerlastname" value="Doe">
<input type="hidden" name="customerpremise" value="No 789">
<input type="hidden" name="customerstreet" value="Test Street">
<input type="hidden" name="customertown" value="Bangor">
<input type="hidden" name="customercounty" value="Gwynedd">
<input type="hidden" name="customerpostcode" value="TR45 6ST">
<input type="hidden" name="customercountryiso2a" value="GB">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="merchant@email.com">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: B11
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
Postal Addresses
Follow our field specification to submit billing and customer details as necessary:
- Billing fields are for the billing contact details.
- Customer fields are for the recipient (i.e. delivery).
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="billingpremise" value="No 789">
<input type="hidden" name="billingstreet" value="Test Street">
<input type="hidden" name="billingtown" value="Bangor">
<input type="hidden" name="billingcounty" value="Gwynedd">
<input type="hidden" name="billingpostcode" value="TR45 6ST">
<input type="hidden" name="billingcountryiso2a" value="GB">
<input type="hidden" name="customerfirstname" value="Jay">
<input type="hidden" name="customerlastname" value="Doe">
<input type="hidden" name="customerpremise" value="No 789">
<input type="hidden" name="customerstreet" value="Test Street">
<input type="hidden" name="customertown" value="Bangor">
<input type="hidden" name="customercounty" value="Gwynedd">
<input type="hidden" name="customerpostcode" value="TR45 6ST">
<input type="hidden" name="customercountryiso2a" value="GB">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: B12
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
Postal Addresses
Follow our field specification to submit billing and customer details as necessary:
- Billing fields are for the billing contact details.
- Customer fields are for the recipient (i.e. delivery).
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
You may also find it useful to have email notifications sent following transactions. There are two main types:
- Emails to your business to inform of payments made.
- Emails to your customers that act as a receipt to confirm their purchase.
Would you like to enable email notifications?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="billingpremise" value="No 789">
<input type="hidden" name="billingstreet" value="Test Street">
<input type="hidden" name="billingtown" value="Bangor">
<input type="hidden" name="billingcounty" value="Gwynedd">
<input type="hidden" name="billingpostcode" value="TR45 6ST">
<input type="hidden" name="billingcountryiso2a" value="GB">
<input type="hidden" name="customerfirstname" value="Jay">
<input type="hidden" name="customerlastname" value="Doe">
<input type="hidden" name="customerpremise" value="No 789">
<input type="hidden" name="customerstreet" value="Test Street">
<input type="hidden" name="customertown" value="Bangor">
<input type="hidden" name="customercounty" value="Gwynedd">
<input type="hidden" name="customerpostcode" value="TR45 6ST">
<input type="hidden" name="customercountryiso2a" value="GB">
<input type="hidden" name="ruleidentifier" value="STR-2">
<input type="hidden" name="ruleidentifier" value="STR-3">
<input type="hidden" name="ruleidentifier" value="STR-4">
<input type="hidden" name="ruleidentifier" value="STR-5">
<input type="hidden" name="merchantemail" value="merchant@email.com">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: B21
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
Postal Addresses
Follow our field specification to submit billing and customer details as necessary:
- Billing fields are for the billing contact details.
- Customer fields are for the recipient (i.e. delivery).
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
Emails to Customers
Note the presence of field ruleidentifier to enable the below:
STR-2 is a rule that sends an email notification to the billingemail address following a successful transaction.
STR-3 is a rule that sends an email notification to the billingemail address following a declined transaction.
Emails to Merchants
Note the presence of field ruleidentifier to enable the below:
STR-4 is a rule that sends an email notification to the merchantemail address following a successful transaction.
STR-5 is a rule that sends an email notification to the merchantemail address following a declined transaction.
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="billingpremise" value="No 789">
<input type="hidden" name="billingstreet" value="Test Street">
<input type="hidden" name="billingtown" value="Bangor">
<input type="hidden" name="billingcounty" value="Gwynedd">
<input type="hidden" name="billingpostcode" value="TR45 6ST">
<input type="hidden" name="billingcountryiso2a" value="GB">
<input type="hidden" name="customerfirstname" value="Jay">
<input type="hidden" name="customerlastname" value="Doe">
<input type="hidden" name="customerpremise" value="No 789">
<input type="hidden" name="customerstreet" value="Test Street">
<input type="hidden" name="customertown" value="Bangor">
<input type="hidden" name="customercounty" value="Gwynedd">
<input type="hidden" name="customerpostcode" value="TR45 6ST">
<input type="hidden" name="customercountryiso2a" value="GB">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: B22
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
Postal Addresses
Follow our field specification to submit billing and customer details as necessary:
- Billing fields are for the billing contact details.
- Customer fields are for the recipient (i.e. delivery).
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
When the customer's browser is redirected back to your website following the processing of a transaction, the URL includes additional parameters to allow your frontend to display the appropriate content.
In addition to the above, you can also enable URL notifications to send transaction data directly to your server without involving the customer's browser. As a server-to-server communication, this makes it more secure and reliable, and is recommend for updating your backend systems. Would you like to enable this functionality too?
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="ruleidentifier" value="STR-8">
<input type="hidden" name="successfulurlnotification" value="http://yourwebsite.com/successful">
<input type="hidden" name="ruleidentifier" value="STR-9">
<input type="hidden" name="declinedurlnotification" value="http://yourwebsite.com/declined">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: C1
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
URL Notifications
Note the presence of field ruleidentifier to enable the below:
STR-8 is a rule that sends a URL notification to the successfulurlnotification following a successful transaction.
STR-9 is a rule that sends a URL notification to the declinedurlnotification following a declined transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Here is an example HTML form that can be used as a template when redirecting your customers to the Payment Pages. Start by copying and pasting the below to a text file and save as an HTML form.
<html>
<body>
<form method="POST" action="https://payments.securetrading.net/process/payments/details">
<input type="hidden" name="sitereference" value="test_site12345">
<input type="hidden" name="currencyiso3a" value="GBP">
<input type="hidden" name="mainamount" value="10.00">
<input type="hidden" name="billingfirstname" value="Jay">
<input type="hidden" name="billinglastname" value="Doe">
<input type="hidden" name="billingemail" value="test@email.com">
<input type="hidden" name="strequiredfields" value="billingfirstname">
<input type="hidden" name="strequiredfields" value="billinglastname">
<input type="hidden" name="strequiredfields" value="billingemail">
<input type="hidden" name="ruleidentifier" value="STR-6">
<input type="hidden" name="successfulurlredirect" value="REDIRECT URL GOES HERE">
<input type="hidden" name="version" value="2">
<input type="hidden" name="stprofile" value="default">
<input type="hidden" name="stdefaultprofile" value="st_cardonly">
<input type="hidden" name="sitesecurity" value="SITE SECURITY GOES HERE">
<input type="hidden" name="sitesecuritytimestamp" value="2019-05-28 14:22:37">
<input type="submit" value="Pay">
</form>
</body>
</html>Start over Example ref: C2
Summary
The above example will form the foundation of your request to our hosted Payment Pages. Let's go through the different components:
Field Specification
The form above serves as an example to help get you started.
Please ensure you change the site reference in the HTML to include the test site reference provided to you within your welcome email when you signed up.
Visa Requirements
To ensure your checkout adheres to Visa's requirements, your request must include the billingfirstname, billinglastname and billingemail fields. The request must also include the strequiredfields included in the example to enforce these requirements.
How it looks
The field stprofile is used to customise the checkout appearance.
stprofile=default ensures that the default preset is applied.
stdefaultprofile=st_cardonly prevents the customer from submitting their address on the hosted checkout.
Site Security
Site security is used to protect payments from unauthorised modification.
To learn how to generate the site security hash, click the link below:
URL Redirects
Note the presence of field ruleidentifier to enable the below:
STR-6 is a rule that redirects the customer's browser to the successfulurlredirect following a successful transaction.
Review and edit the example above based on your specific requirements and save it as an HTML file when you are ready to test it. You can then open this in your web browser and a “Pay” button will be displayed. Click this button, and you will be redirected to your test site, where you can process payments in our testing environment.
If you have configured the HTML above correctly, you should be able to view the following Payment Page hosted by Trust Payments:
When testing, you can use the following test card details to simulate a “Successful” response:
- Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
- Set expiry date to any valid date in the future
- Use security code “123”
Now you understand the basics, let's take a look at what else Payment Pages can do.
Apple Pay
Apple Pay is a wallet-based mobile payment service by Apple Inc. that lets users process payments using an iPhone, iPad or Mac.
Google Pay
Google Pay™ is a digital wallet platform and online payment system developed by Google lets users to process payments with Android phones, tablets, or watches.
PayPal
PayPal is an international e-commerce business allowing payments and money transfers to be made online.
Alternative Payment Methods (APM)
We support a wide range of local payment methods that your international customers trust.
Subscription Engine
Take the hassle out of processing recurring payments and instalments. Process one request and we handle the rest.
Display in iframe
Streamline the checkout experience by directly embedding our checkout into your online store.
Change the layout
Select from a number of presets to quickly make adjustments to the page layout.
Use these tools to customise the look and feel of your checkout.
Apply custom code
Write your own HTML, CSS and JavaScript to build a solution that is bespoke to your needs.
Setting required fields
By default, the customer only needs to enter info that's directly required to facilitate the transaction, but if you need extra info (e.g. their email address), you make adjustments to the required fields.
Time to test your solution
Before you start processing live payments using TRU Connect, you will need to test your integration with us. It is critically important to ensure your system behaves as expected under a range of different possible scenarios.
Our Testing Centre provides guidance and test credentials that can be used to simulate different responses in our sandbox environment.
Ready to launch?
After you have finished configuring your site and have tested thoroughly, follow the final steps outlined in our Going live documentation to begin processing live payments.
