X-Action header must be gateway.payment.create.X-JWS-Signature: see Async API Overview.process.3ds.flow_type = F) there is no waiting_3ds step.approved is shown in Capture payment (clearing).| Response | Meaning | Next step |
|---|---|---|
status = process | The payment is accepted and is being processed. | Get the final status with gateway.payment.status. If the response is lost, use gateway.request.status. |
status = error | The payment is declined. | See «Errors» below. |
{}, X-Request-Status: process | The result is not ready yet. | Repeat the request in a few seconds with the same X-Request-Id. |
200, status error and the error object.error.code and error.description.| HTTP | error.code | When | What to do |
|---|---|---|---|
200 | Decline code, for example 10045 | The payment is declined. | Do not repeat the request with the same X-Request-Id: it returns the same result. |
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 | A required header or field is missing or invalid, for example X-Request-Id is not a UUID. The reason is in error.description. | Fix the request. |
500 | 9999 | Internal error at the gateway entry point. | Repeat the request later with the same X-Request-Id. |
500 | 10000 | Internal error in payment processing. | Repeat the request later with the same X-Request-Id. |