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
| Status | Meaning | Final? |
|---|---|---|
initiated | Created, waiting for the payer or for your transfer | No |
fund_processing | Local-currency payment made, being confirmed | No |
fund_deposited | Local currency received, converting | No |
asset_processing | Crypto being sent or converted | No |
fund_settled | Done. Local currency delivered | Yes ✓ |
asset_settled | Done. Crypto delivered | Yes ✓ |
fund_failed | Local-currency payment didn't arrive | Yes ✗ |
fund_deposit_failed | On-ramp: payment didn't arrive | Yes ✗ |
asset_settle_failed | Crypto couldn't be sent or converted | Yes ✗ |
Each flow guide shows which of these its orders pass through.
Act only on a final status. Releasing goods or crediting a user onfund_processingis the most damaging bug in payments — it works in testing and fails in production.
Updated 22 minutes ago
Did this page help you?