Skip to main content
Stablecoin Account API Publisher Disclaimer A withdrawal is an off-ramp: it sends cryptocurrency from your balance to an external address. The destination should be registered in your address book first — entries are risk-assessed at creation, and destinations that route through certain channels require Travel Rule data before a withdrawal is accepted.
Prerequisites
  • An API token sent as the x-auth-token header
  • Sufficient available_balance in the withdrawal currency
  • The destination address registered in the address book, with Travel Rule meta_data where required

Step 1: Estimate the network fee

Fees track network congestion, so fetch a fresh estimate right before the user confirms — see Supported assets and networks for the full response:
Block the flow if network_status is MAINTENANCE, and check the amount against the network’s min_withdraw_amount and withdraw_precision.

Step 2: Create the withdrawal

Call Create Withdraw with an idempotency key:
Response:
actual_amount is what arrives at the destination after fees. The fee actually charged can differ slightly from the Step 1 estimate.
When the destination routes to the Binance channel, the request is rejected with missing travel_rule_data for binance withdraw if the address book entry has no Travel Rule data. Backfill meta_data via Update Address Book first — see Travel Rule compliance.

Step 3: Track the withdrawal

Status updates arrive on the Withdrawal webhook: You can also poll Retrieve Withdraw with either the long or short order ID, or reconcile in bulk with List Withdraws. Completed orders include the on-chain transaction hash (txid) and completed_time.