added

Withdrawal Status Updates

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

StatusMeaning
pendingThe withdrawal is waiting to be checked.
processingThe withdrawal is being processed.
payingThe funds are being sent.
doneThe withdrawal was completed successfully.
rejectedThe withdrawal was rejected.
failedThe withdrawal could not be completed.
cancelledThe withdrawal was cancelled.
unknownThe status is missing or isn’t recognized.

Internal Transfers

StatusMeaning
pendingThe transfer is waiting to be completed.
doneThe transfer was completed successfully.
rejectedThe transfer was rejected.
failedThe transfer could not be completed.
cancelledThe transfer was cancelled.
unknownThe 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 done as the successful final state.
  • Treat failed, rejected, and cancelled as unsuccessful final states.
  • Treat pending, processing, and paying as non-final states.
  • Handle unknown as a possible status.
  • Do not expect processing or paying for internal transfers.