Testing best practices

Before you start processing live payments, you will need to test your implementation. It is critically important to ensure your system behaves as expected under a range of different possible scenarios. Failure to detect problems in your integration ahead of public release could lead to payments being abandoned on your website!

To help, we provide you with a test site reference that allows you to process test transactions in our sandbox environment. We simulate a bank interface, which listens for incoming requests from your test site, and responds in the way a real bank would.

 

What should I test?

What you will need to test depends entirely on the nature of your integration, but here are some ideas to help you get started.

 

From the customer’s perspective:

  • Ensure the customer is able to complete transactions on desktop and mobile devices.
  • Ensure that if an error occurs (such as a declined payment or invalid field), an error message is clearly displayed in the browser and that the customer is able try again if needed.
  • Ensure that any customisation made to the appearance of the page (e.g. through HTML, JavaScript or CSS) is applied correctly.
  • Ensure your website correctly handles the customer’s browser session following a successful transaction.
  • Ensure that email notifications are received by customers (if enabled).

From the back-office perspective:

  • Ensure your own back-office systems are correctly logging orders and that you are securely storing the transaction reference returned in the response for future reference.
  • Ensure transactions are being shown as successful in MyST.
  • Ensure URL notifications are being received (if enabled).
  • Ensure that you receive merchant email notifications (if enabled).
  • Ensure your Google Analytics solution is performing as expected (if enabled).

 

  Before you begin testing…

Please be aware of the following notes:

  • When you sign up, you will be provided with a “live” account and a “test” account (the latter is prefixed with “test_”). When testing, ensure requests submitted to Trust Payments reference your test sitereference.
  • Most fields submitted to our test system will be accepted. Any data breaching its defined specification will return an error message.
  • Any test data that generates a successful response when submitted while a merchant is in test mode, will produce a declined response when a merchant is switched into live mode. In some cases, the test data may return an error response.
  • Our test system attempts to simulate responses in a similar fashion to the live system. However, depending on your acquirer you may find some responses differ slightly from those given by the test system.
  • In the interest of security, we recommend against using real payment details when using your test account.
  • We recommend specifying the main amount “10.50” when testing. Other amounts can be used but may return unexpected responses.

 

  Ready to start testing?

Click here to open a list of test payment credentials in a new tab.
Our “fake” bank will simulate different responses depending on the values you submit.

  And for when you have finished testing…

Click here to learn about going live.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request