Causes of an Instant Payment Notification URL failure

Note

If you have just changed your host or server, your new IP address may not yet be known by the DNS of different operators. The propagation of this new address may take up to 48 hours.

To see the details of the Instant Payment Notification URL call error via your Expert Back Office:
  1. Double-click the transaction in question
  2. Click the Event log tab

    You will see the error type on the Instant Payment Notification URL call line.

    The different error types and their solutions are presented below.

    1. HTTP 401 and 403 error - Unauthorized or forbidden access
    2. HTTP 404 - File not found
    3. HTTP 500 - Internal server error
    4. HTTP 504 - Gateway timeout
    5. Other HTTP 5XX, 4XX errors

HTTP 401 and 403 error - Unauthorized or forbidden access

This error signifies unauthorized or forbidden access.

Make sure that the called file is not protected by an .htaccess file.

HTTP 404 - File not found

Make sure that the called file is present on your server in the correct directory.

Make sure that you notification URL is not of the http://localhost/ type. The IPN URL must contain your domain name or your public IP address.

HTTP 500 - Internal server error

This error signifies that there is an applicative error on the server side that is hosting your shop. See the logs of your HTTP server (usually apache).

The only way of resolving this issue is by interfering with your server, we do not have control over this type of error.

HTTP 504 - Gateway timeout

This error signifies that your shop did not respond to the IPN URL within the allocated timeout of 10 seconds.

Please check the availability and performance of your server.

Other HTTP 5XX, 4XX errors

See the logs of your HTTP server (usually apache) in order to determine why your shop returned this error message.

If you have confided the administration of your shop to a WEB agency, send them an e-mail with the received notification.