In order to help you integrate your website with MultiSafepay, or test new features, we provide a separate test environment. In the test environment no real transactions can take place, allowing you to test different payment methods and the transaction status handling of your website.
Please start with creating a test account for MultiSafepay Control. When you’ve created your first website, you can use the test API Key found in website settings to authenticate. Alternatively you can use the test Account ID, Secure Code and Site ID to configure your plugin. You can find these credentials too in the website settings.
Every transaction processed by MultiSafepay goes through a number of standard steps. During testing it is helpful to ensure that each step is being completed successfully.
- Initiate an order
- Customer completes the payment
- MultiSafepay sends a status change notification
- Client system updates transaction status
See our Diagnosing Errors guide for help addressing any issues during testing.
1. Initiate an order
Before initiating an order, MultiSafepay validates the information contained in the request to ensure it is valid. The majority of fields are optional but these can have an impact on later stages of the payment process. In particular you should try to include as much data about the customer as possible, as this data is used by our risk and fraud detection systems. The more data available to the system, the more accurate the results.
When initiating an order should receive a link which you should redirect your customer to. If you do not receive a payment link, then something went wrong and you will receive an error code.
2. Customer completes the payment
This part of the process requires no input from the client. However you should be aware that the result of this step is made available in the transaction status and that payments may not be successful for many reasons.
3. MultiSafepay sends a status change notification
The status of an order can change for many reasons. Payments being received or reversed and charge-backs are a few examples. Each time this happens MultiSafepay will send a notification to your system with the transaction id. The URL that MultiSafepay sends this notification to can be configured in two places. The first place checked is the request when initiating an order. If there is no Notification URL provided when initiating an order then the default Notification URL set in MultiSafepay Control will be used.
You can check within MultiSafepay Control to see if we were able to successfully connect to and send a notification to your system in the Offline Actions section. This information is also available on the details screen for each transaction.
4. Client system updates transaction status
Once your system receives a notification it must retrieve the transaction status from MultiSafepay. The transaction status will clearly show whether a payment was successful or not and give a reason why a transaction was not successful.
After your system has updated the transaction or order status you can verify that the information displayed is correct by comparing it to the information displayed within MultiSafepay Control.