added
Withdrawal Status Updates
25 days ago by Oye Olalekan
What’s new
We’ve standardized withdrawal statuses across crypto withdrawals, fiat withdrawals, and internal transfers.
Withdrawal statuses now use lowercase values, with clearer and more consistent status names. Missing or unrecognized statuses are returned as unknown.
Impact
If your integration relies on withdrawal status values, update your implementation to handle the new lowercase values.
Internal transfers do not use the processing or paying statuses.
Changes
External Withdrawals
| Status | Meaning |
|---|---|
pending | The withdrawal is waiting to be checked. |
processing | The withdrawal is being processed. |
paying | The funds are being sent. |
done | The withdrawal was completed successfully. |
rejected | The withdrawal was rejected. |
failed | The withdrawal could not be completed. |
cancelled | The withdrawal was cancelled. |
unknown | The status is missing or isn’t recognized. |
Internal Transfers
| Status | Meaning |
|---|---|
pending | The transfer is waiting to be completed. |
done | The transfer was completed successfully. |
rejected | The transfer was rejected. |
failed | The transfer could not be completed. |
cancelled | The transfer was cancelled. |
unknown | The status is missing or isn’t recognized. |
Status filtering is now more consistent. For example, filtering by processing returns only withdrawals mapped to processing.
The submitted query value is still supported as an alias for done, but responses return done.
Existing query parameters and response fields remain unchanged.
Upgrade
- Compare withdrawal statuses using lowercase values.
- Treat
doneas the successful final state. - Treat
failed,rejected, andcancelledas unsuccessful final states. - Treat
pending,processing, andpayingas non-final states. - Handle
unknownas a possible status. - Do not expect
processingorpayingfor internal transfers.

