The fact that some orders do not appear in the PrestaShop Back Office can be related to several things:
- Make sure the notification URL is configured correctly: Look up the Configuring the Instant Payment Notification URL section in the documentation and verify that you have configured it correctly.
-
Check the response code for the call to the notification URL: Log in to Merchant Back Office, locate the transaction in question, and double-click it.
On the Details tab, search for Instant Payment Notification URL status and verify that the status is Sent. The most common errors are as follows:
-
Error 500
Sometimes the error 500 appears when calling the Instant Payment Notification URL. This error is an application bug and it does not mean that the problem comes from our module. To view the error details, you must enable the apache logs of your server and search the call that provoked the error.
If you do not have access to the server logs, please refer to the chapter How do I display 500 errors in PrestaShop? in the FAQ to have the errors displayed on the return page.
-
Error 404
Make sure that the notification URL is configured correctly (see the first section of this article).
-
Error 500
-
Verify that the module responded correctly during the call: To verify the module's response, log in via the Merchant Back Office, locate the transaction in question, and double-click it.
Click the Event log tab then select the Payment Notification URL call, line in the Complementary information section: Payment Notification URL call, you should see this:OK-Accepted payment, order has been updated.
If you see the fatal error message, it can be related to:- The notification URL that has been configured is for a store that is deactivated or in maintenance mode: In a multi-store setup, our module displays the URL of the default Prestashop store; if that store is deactivated or in maintenance mode, you will need to enter the URL of another store in the Merchant Back Office.
-
A CMS-related error: In this case, you'll need to check your server's error logs to figure out what's wrong, for example:
-
validateOrder - Secure key does not match : Rare case of a buyer who creates two identical customer accounts by making a wrong manipulation, PrestaShop creates asecureKeyin the tableps_cartdifferent from thesecureKeyof the tableps_customer.
The solution would therefore be to use an identicalsecureKeyin both tables and then retry the call to the notification URL.
-
validateOrder - Secure key does not match : Rare case of a buyer who creates two identical customer accounts by making a wrong manipulation, PrestaShop creates asecureKeyin the tableps_cartdifferent from thesecureKeyof the tableps_customer.