What is an IPN?An IPN is an instant payment notification. It allows communication between PayPlug servers and your website server. Thus, it allows the payment information and the back-office e-commerce site to be updated in real time.
When the payment information is correctly processed, PayPlug transactions should show a code with an IPN 200. This means that everything went smoothly and that the orders' information were sent to your back-office.
How to know if I received an IPN error?
You receive an automatic email from us notifying from an IPN error.
You can go the menu "Payments" in your PayPlug portal, then click on the row of the selected payment. The IPN status is displayed in the payments state.
In any case, you should verify that the plugin folder has the correct permissions and that your website is online and accessible from Internet. We recommend to use the permissions 755.
If your site is in maintenance mode, you can't receive the IPNs from our servers.
What to do in case of an IPN error?
If you receive an email from us without an IPN error code but stating that the "transmission for the notification to your server failed", it is probable this is caused by a wrong installation of your intermediate certificates.
In order to test your certificates' installation, we advise that you use the following tools:
If your certificates are not correctly installed, the certificate chain cannot work properly.
Thus, IPNs are not received and the orders in the back-office of your e-commerce site are not updated.
In case of an error 500:The IPN error 500 is an error quite general, internal error to the server. The cause may be a configuration issue on your server, an error system, some wrong permisions, some missing or corrupted files on your website or server.
We advise that you investigate on the origin of this error on your server and that you check the following points:
The permissions on the folder and files where the plugin in installed. It is strongly advised that your folder and files have the permissions 755. Permissions should be neither too widely open, neither restrictive.
The configuration of your .htaccess file, more specifically paramethers' errors for rewritten parameters or the activation of simplified URLs, errors logs on your server or website,
your server's configuration, noticeably timeout response times,
the code your implemented, in the case of a technical integration,
any change you may have done recently.
In case of error 503:
An error 503 means that the server is unsavailable. It generally occurs when a server is not capable to process the http request because of an overload or a temporary maintenance.
Thus, it means that the server is temporarily out of service (it is overloaded or in maintenance mode). This situation is usually temporary.
In cas of an error 503, we advise that you check the unavailability periods for your server but also to make sure that your hosting capabilities fir your server work load.
Moreover, your site should be online and accessible from Internet. If your site is in maintenance more, you will receive some errors 503.
In case of error 401:This means an authentication is necessary in order to access the resource.
More precisely, the url is not accessible without authantication. Therefore, you can not receive the IPN from our server.
In order to solve this issue, you should verify the access rights to this url and make sure it is accessible from the Internet.
You should also check that the .htaccess is not protected by a password. If this is the case, you will have an error 401.
In case of error 403:The server understood the request, but refuses to execute it. On the contrary of error 401, authentication won't make a difference.
On the servers where authentication is requested, this means that generally, authentication was accepted but access rights don't allow the client to access the resource.
In order to fix an error 403, you should verify the following points:
authorize incoming POST requests on the server.
In case of use of a proxy, verify the rules on HTTPS and/or HTTPS requests
Verify access tights : CHMOD should be in 755 on the module's files and folder,
In case of a file .htaccess, verify that there are no restrictions,
deactivate an eventual application-layer firewall that may have been implemented on the server (on the whole domain)
In case of an error 404:An error 404 means that the requested resource (generally a web page) doesn't exist.
The root of this error is generally a renamed or deleted URL. It generally happens on a redirection page after the payment.
In order to fix this issue, you can verify your return and cancel URLs. You can also delete and reinstall your PayPlug module.