server url error - FAILED_SERVER_XXX_ERROR
At the end of the payment, the payment gateway calls the Instant Payment Notification URL defined in the Merchant Back Office. This call only takes place if the notification rule is configured in the Merchant Back Office.
If the payment gateway cannot reach your IPN URL, you will receive an e-mail indicating a failure during the Instant Payment Notification call. This failed call has no effect on the payment, if it was finalized correctly (accepted or rejected).
Example of a warning e-mail
Hello, On 06/08/16 at 12:39:10 (GMT+1), we recorded the transaction ref. R -634823 of EUR 45.25 for the shop XXXXXXX. When calling your IPN URL http://your.shop/validation, we came across a technical problem with the error code: FAILED_SERVER_403_ERROR. For more information about this error code, refer to the FAQ: server-url-error Case 1: we were unable to contact your server (your merchant website is unavailable), case 2: the response timeout from your server was exceeded, case 3: your server returned an error message. You can find the encountered type of error in the transaction event log of your Merchant Back Office. The impact of this message: The payment has been finalized, successfully or not, by the payment gateway, however it is possible that your shop is not up to date. Do not call the tech support, we cannot interfere with your application. However, we recommend you to contact your webmaster to analyze the causes of this error and apply any required corrections. Once the problem is solved, you can manually retry the call to the IPN URL corresponding to this transaction in order to notify your applications. To do this,
|
Reminder
The call to the Instant Payment Notification is a POST HTTP or HTTPS request made from one server to another. The call includes the parameters linked to the payment as well as the vads_trans_status parameter that provides the transaction status.
Causes of an Instant Payment Notification failure
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.
- double click the transaction in question,
- Click on the Event log tab.
You will see the error type on the Instant Payment Notification URL call line.
The different error types and their resolution are presented below.
Most frequent errors
Contact your webmaster to analyze the causes of this type of error and make any necessary corrections.
| Type of error | Description |
|---|---|
| Server error 500 | The merchant website has returned an HTTP 500 Internal Server Error response status 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 by performing an action on your server. |
| Server error 504 | The merchant website has returned an HTTP 504 Gateway Time-out response status code. The merchant server has not accepted the call within the time limit of 10s. |
| Server error 401 | The merchant website has returned an HTTP 401 Unauthorized response status code. Make sure that the resource is not protected by an .htaccess file. |
| Server error 403 | The merchant website has returned an HTTP 403 Forbidden response status code. Make sure that the resource is not protected by an .htaccess file. |
| Server error 404 | The merchant website has returned an HTTP 404 Not Found response status code. Make sure that the URL is correctly specified in the rule configuration. Make sure that the file is present on your server. |
Error table
| 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 end of payment notification rule 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 has returned an HTTP 400 Bad Request response status code. |
| Server error 401 | The merchant website has returned an HTTP 401 Unauthorized response status code. Make sure that the resource is not protected by an .htaccess file. |
| Server error 402 | The merchant website has returned an HTTP 402 Payment Required response status code. |
| Server error 403 | The merchant website has returned an HTTP 403 Forbidden response status code. Make sure that the resource is not protected by an .htaccess file. |
| Server error 404 | The merchant website has returned an HTTP 404 Not Found response status 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 has returned an HTTP 405 Method Not Allowed response status code. |
| Server error 406 | The merchant website has returned an HTTP 406 Not Acceptable response status code. |
| Server error 407 | The merchant website has returned an HTTP 407 Proxy Authentication Required response status code. |
| Server error 408 | The merchant website has returned an HTTP 408 Request Time-out response status code. |
| Server error 409 | The merchant website has returned an HTTP 409 Conflict response status code. |
| Server error 410 | The merchant website has returned an HTTP 410 Gone response status code. |
| Server error 411 | The merchant website has returned an HTTP 411 Length Required response status code. |
| Server error 412 | The merchant website has returned an HTTP 412 Precondition Failed response status code. |
| Server error 413 | The merchant website has returned an HTTP 413 Request Too Large response status code. |
| Server error 414 | The merchant website has returned an HTTP 414 Request-URI Too Long response status code. |
| Server error 415 | The merchant website has returned an HTTP 415 Unsupported Media Type response status code. |
| Server error 500 | The merchant website has returned an HTTP 500 Internal Server Error response status 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 by performing an action on your server. |
| Server error 501 | The merchant website has returned an HTTP 501 Not Implemented response status code. |
| Server error 502 | The merchant website has returned an HTTP 502 Bad Gateway / Proxy Error response status code. |
| Server error 503 | The merchant website has returned an HTTP 503 Service Unavailable response status code. Make sure you are not in "maintenance" mode. |
| Server error 504 | The merchant website has returned an HTTP 504 Gateway Time-out response status code. The merchant server has not accepted the call within the time limit of 10s. |
| Server error 505 | The merchant website has returned an HTTP 505 HTTP Version Not Supported response status code. |
Manual notification retry
Once the potential issue is resolved, you can manually resend the notification URL corresponding to this transaction in order to notify your shop.
- sign in to the Merchant Back Office:
- find the transaction ref. xxxxxx,
- once the transaction is found, right-click on it and select "Send the Instant Payment Notification".
The gateway displays the result of this new call to the notification URL in real time.