Klarna Docs - Error codes and messages for Order Management
API and SDKsSupport
Error codes and messages for Order Management

Check out our usual error messages and what they mean

HTTPS status codeError code
400NOT_FOUND
403XXX_NOT_ALLOWED
404NO_SUCH_XXX
404NOT_FOUND
409CONFLICT
413REQUEST_TOO_LARGE
422UNPROCESSABLE_ENTITY
422INVALID_ADDRESS
429TOO_MANY_REQUESTS
500INTERNAL_SERVER_ERROR
500UNEXPECTED_ERROR
502/503/504TEMPORARILY_UNAVAILABLE
Error messageDescriptionHandling error
[Refund xxxxxxx-xxxx-xxxxxxxxxxxxxxx cannot be found for order xxxxxxx-xxxx-xxxxxxxxxxxxxxx] This is an invalid request. Refer to the OpenAPI documentation to check validation rules.

CAPTURE_NOT_ALLOWED error is only present as response to capture request.

There are multiple reasons for this error to occur depending on these the customer may not get the products and the merchant won't get settled for the order. The customer might have to place the same order again.

Error messageDescriptionError handling
[Capture not allowed] The order might be cancelled or expired, or the captured amount might be higher than the remaining authorized amount.

CANCEL_NOT_ALLOWED error is only present as response to cancel request.

Error messageDescriptionError handling
[Order has previous captures. Cancel not possible] Once an order is captured, it can not be cancelled anymore. For more information, see our Escalation and retry policy.

NOT_ALLOWED error could be present in the following requests:

  • release_authorization
  • extend_authorization_time
  • update_authorization
  • update_order_customer_details
  • update_merchant_references

Depending on the operation this error can affect the customer communication, shipping details or authorization expire time.

Error messageDescriptionError handling
[Resulting authorization amount xxx cannot be less than the captured amount xxx for order. Order authorization cannot be updated] The capture amount must always be higher than the authorized amount. See our Escalation and retry policy.

REFUND_NOT_ALLOWED error is only present as response to refund request.

If the order has already been cancelled or fully refunded, the failed refund call doesn't have any impact on the customer. In cases where the attempted refunded amount is greater than the captured amount, the whole refund might fail, and customer's money be left with the merchant.

Error messageDescriptionError handling
[Order has no captures. Refund not possible] An order or value can only be refunded if it has been previously captured or partially captured.See our Escalation and retry policy.

NO_SUCH_ORDER error is only present as response to capture request.

Error messageDescriptionHandling error
[Order xxxxxxx-xxxx-xxxxxxxxxxxxxxx cannot be found] The requested resource (order, capture, or refund) could not be found. Check if their IDs are correct.Check if their IDs are correct.
Error messageDescriptionHandling error
[Capture could not be found. Shipping info cannot be added to capture xxxxxxx-xxxx-xxxxxxxxxxxxxxx] The requested resource (order, capture, or refund) could not be found. Check if their IDs are correct.

Error messageDescriptionHandling error
[Refund xxxxxxx-xxxx-xxxxxxxxxxxxxxx cannot be found for order xxxxxxx-xxxx-xxxxxxxxxxxxxxx] The requested resource (order, capture, or refund) could not be found. Check if their IDs are correct.
Error messageDescriptionHandling error
[] This request conflicts with the current state of the target resource. See our Escalation and retry policy.
Error messageDescriptionHandling error
[Request is too large] This request is too large.Refer to theOpenAPI documentationto see if the request is valid.
Error messageDescriptionHandling error
[The shipping and/or billing address is invalid] The service is unable to process this request. Refer to theOpenAPI documentationto see if the request is valid.
Error messageDescriptionHandling error
[The size of theshipping_info/shipping_companyvalue must be between 0 and 100]The service is unable to process this request.Refer to the OpenAPI documentation to see if the request is valid.
Error messageDescriptionHandling error
[Too many requests] We received too many requests in a given amount of time (rate limiting).For more information, see the Rate limit guide.
Error messageDescriptionHandling error
[Unexpected server error] An unexpected server error occurred.For more information, see our Escalation and retry policy.
Error messageDescriptionHandling error
[Temporarily unavailable] The service is temporarily unavailable. For more information, see our Escalation and retry policy.