HTTP errors
HTTP response status codes don't necessarily originate from the MultiSafepay platform. They are generic errors you can encounter while browsing the web.
This table lists the most common HTTP error codes and descriptions:
| Error | Description |
|---|---|
| HTTP 204: No Content | The endpoint responds successfully but doesn't include the text OK in the response body. |
| HTTP 301: Moved Permanently | The endpoint has moved permanently. Check that your webhook endpoint is configured correctly in your MultiSafepay account and/or API request. |
| HTTP 302: Found | The endpoint redirects to another location. Check that your webhook endpoint is configured correctly in your MultiSafepay account and/or API request. |
| HTTP 400: Bad Request | The server can't process the request, for example because the request is malformed. Check your server logs and how the endpoint handles incoming requests. |
| HTTP 401: Unauthorized | The endpoint requires authentication or the provided authentication credentials aren't valid. Check the authentication configuration for the endpoint. |
| HTTP 403: Forbidden | The endpoint is blocking requests from MultiSafepay or requires authentication. Ensure that the endpoint is publicly accessible and that firewall, Cloudflare, or other security rules aren't blocking requests from MultiSafepay. |
| HTTP 404: Not Found | The endpoint doesn't exist. Check that your webhook endpoint is configured correctly in your MultiSafepay account and/or API request. |
| HTTP 405: Method Not Allowed | The endpoint doesn't accept the HTTP method used for the request. Check which HTTP methods your endpoint accepts. |
| HTTP 429: Too Many Requests | The server is rate limiting incoming requests. Check your rate-limit, firewall, or security configuration. |
| HTTP 500: Internal Server Error | An error occurred on your server while processing the request. Check your server logs or contact your server administrator or web developer. |
| HTTP 502: Bad Gateway | A gateway or proxy received an invalid response from the upstream server. Check your proxy, load balancer, and application server configuration. |
| HTTP 503: Service Unavailable | The server is temporarily unavailable or unable to process the request. Check your server or application availability. |
| HTTP 504: Gateway Timeout | A gateway or proxy didn't receive a response from the upstream server in time. Check your proxy, load balancer, and application server. |
| HTTP 599: Timeout | Your server didn't respond to MultiSafepay's notification request within 10 seconds. After 10 seconds, the request times out and the notification attempt is logged as HTTP 599. Check your server logs to determine why the endpoint isn't responding within the allowed time. For more information, see Webhook - Acknowledge the notification |
Support
Email [email protected]
Updated 3 days ago
Did this page help you?