Skip to content

Order & Deposit Status

Displays all possible deposit statuses and their transitions, with visual diagrams for better understanding.

Order Status

Types Of Order Status

StatusDescription
CREATINGOrder is being created. This status only returned when using the Create Withdrawal Order (v2) endpoint.
PROCESSINGOrder is being processed.
PARTIALLY_FAILEDSome transactions within the batch failed.
MANUAL_APPROVALRequires KYT or amount exceeds manual approval threshold.
FAILEDOrder failed.
ORDER_SEND_OUTOrder has been sent out for execution.
FINISHEDOrder completed successfully.
CANCELEDOrder was canceled.
WAITING_FOR_APPROVALWithdrawal is pending approval internal checkers.
REJECTEDOrder has been rejected from approval.

Order Status Scenarios

If the Create Withdrawal Order (v2) endpoint is used, the order enters the CREATING state before PROCESSING. Example: CREATING → PROCESSING

Main flow

The standard successful withdrawal flow. Order is processed, sent to the blockchain, and completed.

PROCESSING → ORDER_SEND_OUT → FINISHED

Batch withdrawal (Partially Failed)

Occurs during batch withdrawals when some transactions in the batch succeed while others fail.

PROCESSING → ORDER_SEND_OUT → PARTIALLY_FAILED

Business Line Checker Approval Required

Triggered when an order requires approval from business line checkers.

Scenario A: Approved

WAITING_FOR_APPROVAL → PROCESSING → ORDER_SEND_OUT → FINISHED

Scenario B: Rejected

WAITING_FOR_APPROVAL → REJECTED

Manual approval required

Triggered when an order meets certain risk or policy conditions. The order pauses for manual review by our Cactus Team.

Scenario A: Approved

PROCESSING → MANUAL_APPROVAL → PROCESSING → ORDER_SEND_OUT → FINISHED

Scenario B: Rejected

PROCESSING → MANUAL_APPROVAL → REJECTED

Canceled

Only for EMV Compatible chain orders. Orders can be canceled when status is either PROCESSING or ORDER_SEND_OUT.

PROCESSING → ORDER_SEND_OUT → CANCELED


Deposit Status

Types Of Deposit Status

StatusDescription
UNCONFIRMEDBefore reaching security block height.
CONFIRMEDFinal confirmed status.
ROLLBACKEDReverted due to on-chain rollback.
ROLLBACKED_RBFRollback transactions caused by RBF
FROZENDeposit has been frozen.
FROZEN_REFUND_WAITING_ADDRESSThe transaction has been flagged by compliance and requires a refund address to proceed.
REFUNDEDThe frozen deposit has been successfully refunded.

Deposit Status Scenarios

Main flow

The standard successful deposit flow. Deposit is detected on the blockchain and confirmed after reaching the required block confirmations.

UNCONFIRMED → CONFIRMED

KYT frozen, released before security height

UNCONFIRMED → FROZEN → UNCONFIRMED → CONFIRMED

KYT frozen, released after security height

UNCONFIRMED → FROZEN → CONFIRMED

Deposit frozen and marked for refund

Deposit is flagged out and frozen. After review, it is determined that the deposit should be refunded. The system requires for a refund address and then completing the refund.

UNCONFIRMED → FROZEN → FROZEN_REFUND_WAITING_ADDRESS → REFUNDED

Rollback

Occurs when a blockchain rollback happen and invalidates the deposit transaction.

UNCONFIRMED → ROLLBACKED

Rollback after confirmation

In rare cases (e.g. a chain reorganization), a deposit can be rolled back after it has reached CONFIRMED. If the transaction is later re-included on-chain, the Cactus team will reach out to confirm the ROLLBACKED event has been processed on your side before a new deposit notification cycle begins.

UNCONFIRMED → CONFIRMED → ROLLBACKED \ \ UNCONFIRMED → CONFIRMED - when transaction is re-included on-chain (same transaction hash, different detail_id)

Please take this scenario fully into account when designing your business logic to prevent duplicate crediting. Note that the re-pushed deposit carries the same transaction hash (tx_id) but a different detail_id from the original deposit.

If you use a custom deposit confirmation height, a lower height increases the chance of this happening.