auto_clearing = false).X-Action header must be gateway.payment.clearing.X-JWS-Signature: see Async API Overview.approved.amount the full payment amount is debited. With a smaller amount the rest is reversed automatically: it is listed in reverse_payments.auto_clearing = true) is debited at creation: to return the money use gateway.payment.refund.| Response | Meaning | Next step |
|---|---|---|
status = process_clearing | The clearing is accepted. | Get the final status with gateway.payment.status: the payment gets status success, clearing.cleared = true. If the response is lost, use gateway.request.status. |
{}, X-Request-Status: process | The result is not ready yet. | Repeat the request in a few seconds with the same X-Request-Id. |
400, status error and the error object.error.code and error.description.| HTTP | error.code | When | What to do |
|---|---|---|---|
400 | 110691 | Invalid payment status: clearing is possible only for a two-step payment in status approved (not cleared, not reversed, not waiting for 3DS). | Get the payment status with gateway.payment.status. |
400 | 110741 | The clearing amount exceeds the payment amount. | Pass amount not greater than the payment amount. |
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 missing or is not a UUID, amount is less than 0.01, 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 with the same X-Request-Id. |
500 | 10000 | Internal error in payment processing. | Repeat the request later with the same X-Request-Id. |