This page consolidates error scenarios you may encounter when working with the endpoint: from basic HTTP responses to a classification of failed charge reasons. The document provides a response contract, as well as an error type mapping (EXTERNAL / BUSINESS), so you can interpret failures unambiguously and choose the correct way to present errors to the user.
{
"uuid": "8d911b21-b987-4006-a887-29558ff05b7e",
"code": 2107,
"message": "Race condition",
"traceId": "1d6973b1-8fcb-4dd8-8356-557a369a5ba0"
}{
"uuid": null,
"message": "Entity not found",
"code": 0,
"traceId": "9b29989bd9e957856aafe8b62b0910f1"
}{
"uuid": null,
"message": "Validation error",
"code": 0,
"traceId": "f075c9d5ac00263a85449bc27730e4ce",
"errors": [
{
"field": "item",
"title": "This collection should contain exactly 1 element."
}
]
}{
"uuid": null,
"code": 0,
"message": "Short exception description.",
"traceId": "082d86c339533af07c14252afcecc7bd"
}void / stop payment / cancel).