X-Request-Id.X-Action header must be gateway.request.status.X-JWS-Signature: see Async API Overview.X-Request-Status: process.404.X-Request-Id of this status request (any new UUID), id in the body (X-Request-Id of the checked request) and response.id (the payment).X-Request-Id is also safe: the operation is not performed again and the current state is returned.| Response | Meaning | Next step |
|---|---|---|
status = process | The checked request is still being processed: response holds the current state. | Repeat the request later. |
status = success | The checked request is processed: response holds the response of the original method. | Use response as the response to the original request. |
status = error | The checked request is rejected or declined: response holds the response with error. | See response.error. |
{}, X-Request-Status: process | The result is not ready yet. | Repeat the request in a few seconds. |
error.code and error.description.| HTTP | error.code | When | What to do |
|---|---|---|---|
404 | — | No request with this id was found for the merchant: it may never have been sent, may belong to another merchant, or its result is no longer kept. | Check id. If the result is no longer kept, get the payment state with gateway.payment.status by id or order_id. |
400 | 9400 | The body is not valid JSON. | Fix the request. |
401 | 9998 | The signature is invalid. | Check the signature: see Async API Overview. |
422 | 9403 | id is not a UUID or a required header is missing. The reason is in error.description. | Fix the request. |
500 | 9999 | Internal error at the gateway entry point. | Repeat the request later. |
500 | 10000 | Internal error in payment processing. | Repeat the request later. |