Get payment status

Returns the current state of a payment by its ID (id) or by the merchant's order number (order_id).

The X-Action header must be gateway.payment.status.

Sign the request with X-JWS-Signature: see Async API Overview.

Child payments (refunds and reversals) can be requested by their own ID.

Payment status flow

Statuses are the values of status in the response.

Status	Meaning
`process`	The payment is being processed.
`waiting_3ds`	Waiting for 3DS authentication: redirect the client to `3ds.acs_url`.
`process_3ds`	3DS authentication result is being processed.
`approved`	Funds are held (two-step payment): clear or reverse the payment.
`process_clearing`	Clearing is being processed.
`reversed`	The hold is cancelled, funds are released.
`success`	The payment is completed, funds are debited.
`error`	The payment failed: see `error`.

Label	Meaning
create	The method `gateway.payment.create`.
3DS	The client must pass 3DS authentication at `3ds.acs_url`.
3DS done	The client has passed 3DS authentication.
one-step	`auto_clearing = true`.
two-step	`auto_clearing = false`.
declined	The payment is declined.
clearing	The method `gateway.payment.clearing`.
reverse	The method `gateway.payment.reverse`.
refund	The method `gateway.payment.refund`: the status stays `success`, refunds are listed in `refund_payments`.

A partial clearing reverses the rest automatically: it is listed in reverse_payments.

Result

Response	Meaning	Next step
The payment	The current state of the payment in `status`.	See «Payment status flow» above.
`{}`, `X-Request-Status: process`	The payment data is being prepared.	Repeat the request in a few seconds.

Errors

A declined payment is not an error of this request: it is returned with HTTP 200, status error and the error object.
The error is returned in error.code and error.description.

HTTP	`error.code`	When	What to do
`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`	Neither `id` nor `order_id` is passed, `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.

application/json

Headers

Bodyapplication/json

Since the API operates asynchronously, whenever the payment status is returned as process, you must continuously query the payment status until you receive a final status such as approved or success.

{
  "id": "01a1304b-4b7e-7ef7-8bd6-3cab7702d22e",
  "status": "approved",
  "amount": 100,
  "created_at": "2026-10-12T13:26:43.326981454Z",
  "order_id": "order_1001",
  "clearing": {
    "cleared": false,
    "amount": 0
  },
  "from": {
    "card": {
      "token": "af6ada05-5599-41aa-9b8c-227233e58f2e",
      "brand": "UNIONPAY"
    }
  },
  "additional": {
    "approval_code": "432914",
    "reference": "420101893936",
    "intreference": "5DF022F3C632F404"
  },
  "3ds": {
    "acs_url": "",
    "flow_type": "F"
  }
}

Payment status flow#

Result#

Errors#

Request

Responses

Payment status flow

Result

Errors