HomeGuidesAPI ReferenceChangelogPOS PaymentsOnline Payments
Home
Guides

Response Codes

HTTP Responses

HTTP Status CodeHTTP Status MessageNotes
200OKThe request was successfully processed and returned a response body.
201CreatedThe request was successfully processed and returns the newly created entity.
204No ContentThe request was successfully processed and the response does not contain a body.
400Bad RequestThe API understood the message, but it contained invalid or incorrect data in one or more fields. For the specific error you'll need to inspect the response body. This contains a message with an explanation what went wrong.
401UnauthorizedThe provided credentials are incorrect.
403ForbiddenYou have successfully authenticated, but are not allowed to access the requested resource.
404Not FoundThe requested resource does not exist.
409ConflictSome resources are dependent on other resources. Refunds for example are required to be linked to a transaction. The sum of all refunds must not exceed the original transaction amount. Doing so can result in a 409 being returned.
422Unprocessable EntityThe request body does not contain valid JSON.
429Too Many RequestsYou've made too many requests in a short amount of time.
500Internal Server ErrorThis error status is returned when something went wrong on our side.
503Service UnavailableOne or more services might not be available. This could indicate an issue with the payment method itself, or our systems.

Error response fields


FieldTypeDescription
IDStringThis ID is generated by our API to assist in traceability.
MessageStringContains the reason why an error was returned.