| Status | Description | |
|---|---|---|
awaiting_funds | Devdraft is waiting to receive funds from the customer before processing the transfer. This applies to incoming crypto deposits, wires, or ACH pushes. | |
in_review | A rare, temporary state triggered when transfer data needs further confirmation. Typically resolves in seconds; otherwise, Devdraft will reach out within 24 hours. | |
funds_received | Devdraft has received the funds and is preparing to move them on the customer’s behalf. | |
payment_submitted | Devdraft has initiated the payment and is awaiting confirmation. Time to completion depends on the payment rail: minutes (Crypto), hours (Wires), or days (ACH). | |
payment_processed | The transfer is complete and funds have been successfully delivered to the destination. | |
undeliverable | Devdraft was unable to deliver funds due to an issue like an invalid account or unsupported asset at the destination. | |
returned | The payment was sent but failed. Funds have returned to Devdraft and a refund to the sender is underway. | |
refunded | The payment was refunded Devdraft no longer has the funds. This means the payment was either sent back to the original sender, refunded based on the configured crypto return policy, or sent back to the originating Bridge wallet or Bridge prefunded account. | |
canceled | The transfer was canceled. This can only happen from the awaiting_funds state via the DELETE /v0/transfers/{transferID} endpoint. | |
error | A problem occurred that blocked processing. This typically requires manual review or developer action. |
- Please note that a transfer will always progress from
awaiting_funds→funds_received→payment_submitted→payment_processed. It can never go backwards. - States including
returned,refunded,undeliverable, orerrorindicate exception paths.