Orders & Statuses

Every status an order can have, and what to do

An order isn't done when you create it. The create call means "accepted". What happened arrives later — by webhook, or when you check:

curl -X GET 'https://sandbox-api.transfi.com/v3/orders/OR-2509291454262384294' \
  -H 'Authorization: Basic YOUR_BASE64_CREDENTIALS' \
  -H 'mid: YOUR_MID'

→ Get Order · List Orders · Cancel Order

Statuses

StatusMeaningFinal?
initiatedCreated, waiting for the payer or for your transferNo
fund_processingLocal-currency payment made, being confirmedNo
fund_depositedLocal currency received, convertingNo
asset_processingCrypto being sent or convertedNo
fund_settledDone. Local currency deliveredYes ✓
asset_settledDone. Crypto deliveredYes ✓
fund_failedLocal-currency payment didn't arriveYes ✗
fund_deposit_failedOn-ramp: payment didn't arriveYes ✗
asset_settle_failedCrypto couldn't be sent or convertedYes ✗

Each flow guide shows which of these its orders pass through.

🛑

Act only on a final status. Releasing goods or crediting a user on fund_processing is the most damaging bug in payments — it works in testing and fails in production.

🛑

Don't retry a failed order. Create a new one with a new partnerId. Sending the same partnerId returns the original failed order.

📘

Cancelling. An order can be cancelled only before it's been processed — a payout still initiated, or an off-ramp still waiting for the crypto.


Did this page help you?