Running tests and troubleshooting

In order to test the notifications, follow the steps below:

  1. Make a payment (in TEST mode or in PRODUCTION mode).
  2. Once the payment is complete, look for the transaction in your Back Office (Management > Transactions or TEST Transactions menu if you made the payment in TEST mode).
  3. Double-click the transaction to view the transaction details.
  4. In the transaction details, search for the section entitled Technical data.
  5. Check the status of the Instant Payment Notification URL:

    The list of possible statuses is provided below:

Status Description
N/A The transaction did not result in a notification or no notification rules have been enabled.
Undefined URL An event has triggered the notification rule for end of payment but the URL is not configured.
Call in progress The notification is in progress. This status is temporary.
Sent The notification has been successfully sent and a remote device returned an HTTP 200, 201, 202, 203, 204, 205 or 206 response status code.
Sent (permanent redirection)

The merchant website has returned an HTTP 301 or 308 response status code with a new URL to contact. A new call in POST mode has been made to the new URL.

Sent (temporary redirection) The merchant website has returned an HTTP 302 or 307 response status code with a new URL to contact. A new call in POST mode has been made to the new URL.
Sent (redirection to another page) The merchant website has returned an HTTP 303 response status code with a new URL to contact. A new call in GET mode has been made to the new URL.
Failed Generic error different from the codes described below.
Server unavailable The notification has lasted more than 35s.
SSL handshake failure Your server is incorrectly configured.

Run a test on the Qualys website (https://www.ssllabs.com/ssltest/) and correct the errors.

Connection interrupted Communication error.
Connection refused Communication error.
Server error 300 Case of redirection not supported by the gateway.
Server error 304 Case of redirection not supported by the gateway.
Server error 305 Case of redirection not supported by the gateway.
Server error 400 The merchant website returned a HTTP 400 Bad Request code.
Server error 401 The merchant website returned a HTTP 401 Unauthorized code.

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

Server error 402 The merchant website returned a HTTP 402 Payment Required code.
Server error 403 The merchant website returned a HTTP 403 Forbidden code.

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

Server error 404 The merchant website returned a HTTP 404 Not Found code.

Make sure that the URL is correctly specified in the rule configuration.

Make sure that the file is present on your server.

Server error 405 The merchant website returned a HTTP 405 Method Not allowed code.
Server error 406 The merchant website returned a HTTP 406 Not Acceptable code.
Server error 407 The merchant website returned a HTTP 407 Proxy Authentication Required code.
Server error 408 The merchant website returned a HTTP 408 Request Time-out code.
Server error 409 The merchant website returned a HTTP 409 Conflict code.
Server error 410 The merchant website returned a HTTP 410 Gone code.
Server error 411 The merchant website returned a HTTP 411 Length Required code.
Server error 412 The merchant website returned a HTTP 412 Precondition Failed code.
Server error 413 The merchant website returned a HTTP 413 Request Entity Too Large code.
Server error 414 The merchant website returned a HTTP 414 Request-URI Too long code.
Server error 415 The merchant website returned a HTTP 415 Unsupported Media Type code.
Server error 416 The merchant website returned a HTTP 416 Requested range unsatisfiable code.
Server error 417 The merchant website returned a HTTP 417 Expectation failed code.
Server error 419 The merchant website returned a HTTP 419 Authentication Timeout code.
Server error 421 The merchant website returned a HTTP 421 Misdirected Request code.
Server error 422 The merchant website returned a HTTP 422 Unprocessable Entity code.
Server error 423 The merchant website returned a HTTP 423 Locked code.
Server error 424 The merchant website returned a HTTP 424 Failed Dependency code.
Server error 425 The merchant website returned a HTTP 425 Too Early code.
Server error 426 The merchant website returned a HTTP 426 Upgrade Required code.
Server error 429 The merchant website returned a HTTP 431 Request Header Fields Too Large code.
Server error 431 The merchant website returned a HTTP 415 Unsupported Media Type code.
Server error 451 The merchant website returned a HTTP 451 Unavailable For Legal Reasons code.
Server error 500 The merchant website returned a HTTP 500 Internal Server Error code.

An application error has occurred on the level of the server hosting your shop. See the logs of your HTTP server (usually apache).

The issue can only be corrected with an intervention on your server.

Server error 501 The merchant website returned a HTTP 501 Not Implemented code.
Server error 502 The merchant website returned a HTTP 502 Bad Gateway / Proxy Error code.
Server error 503 The merchant website returned a HTTP 503 Service Unavailable code.
Server error 504 The merchant website returned a HTTP 504 Gateway Time-out code.

The merchant server has not accepted the call within the time limit of 10s.

Server error 505 The merchant website returned a HTTP 505 HTTP Version not supported code.

For more information on a notification, click the link Display the details or click the Event log tab and search for the line Notification URL call.

In order to help the merchant identify the source of the error, the gateway systematically analyses the 512 first characters returned by the merchant website and displays them in the Details column.

  • Example of a successfully processed notification:
  • Example of a failed notification:

If the payment gateway is unable to access the URL of your page, an e-mail alert will be sent to the shop administrator.

It contains:

  • The HTTP code of the encountered error
  • Parts of error analysis
  • Its consequences
  • Instructions to follow via the Merchant Back Office for resending the request to the URL specified in step 4.