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:

ErrorDescription
HTTP 200: OKThe page is responding correctly but is missing the text OK in the body.
HTTP 301: Moved permanentlyThe page has moved permanently. Check your webhook endpoint is configured correctly in your MultiSafepay account and/or the API request.
HTTP 302: FoundThe page redirects to another location. Check your webhook endpoint is configured correctly in your MultiSafepay account and/or the API request.
HTTP 403: ForbiddenThe page appears to require a login. This often occurs in a testing environment. Either remove the login page, or add our IP ranges to your allow list. For a list of MultiSafepay IP addresses, email [email protected]
HTTP 404: Not foundThe page doesn't exist. Check that your webhook endpoint is configured correctly in your MultiSafepay account and/or the API request.
HTTP 500: Internal server errorThe webshop server is malfunctioning. Contact your server administrator or web developer to resolve this.
HTTP 503: Service not availableThe function that processes the notification isn't working. Contact your server administrator or web developer to resolve this.


πŸ’¬

Support

Email [email protected]

Top of page


Did this page help you?