Cancellation

POST /v1/conversions/:id/cancel ends a conversion before any deposit arrives. It is the clean exit from awaiting_deposit.

When it is valid

Only in status='awaiting_deposit'. In any other state, the call fails with a validation error.

What the call does

1. Transitions the conversion to canceled (terminal).
2. Releases the limit reservation for the end customer.
3. Releases the (user_id, transaction_type) lock. The end customer is free to start a new offramp conversion.

The response is the updated conversion.

What the call does not do

• Does not recover deposited USDT. If a deposit arrived (even partial), the conversion has already transitioned to funded or standby, and cancel is no longer valid.
• Does not cancel a conversion in standby. Standby has its own path: liquidate, or wait it out.

Decision: cancel or liquidate?

Want to stop a conversion? No deposit arrived → cancel. Deposit arrived → liquidate (in standby) or wait for automatic settlement (in funded).

If you are not sure of the current state, read first with GET /v1/conversions/:id.

Next step

• Standby and manual liquidation: for conversions that already received a deposit.