Abandoned conversion

abandoned is the terminal state a conversion reaches when 7 days pass in standby with no applicable /liquidate or cancellation. Resolution is manual, conducted by BlendFi's team off-platform.

When it happens

When standby_expires_at < now() (i.e., standby_at + 7 days in the past) with the conversion still in standby, an internal sweep transitions the conversion to abandoned and fires conversion.abandoned.

What this means operationally

• The conversion is terminal. There is no exit transition. The operation will not settle via API.
• The USDT deposit remains in BlendFi's custody. The window for automatic decision is over.
• Resolution is off-platform. BlendFi's team evaluates case by case. Possible outcomes include refund to the end customer, in coordination with the partner, as regulation and the commercial agreement permit for the case.
• The lock is released. The end customer can start a new offramp conversion.

What you do

Open a ticket with BlendFi support citing the conversion_id. The channel and SLA agreed in your commercial relationship continue to apply. BlendFi conducts the investigation and returns with the proposed resolution.

How to avoid

The best mitigation is not to leave conversions in standby for too long. Recommendations:

• React to conversion.standby in the synchronous webhook flow. The vast majority of cases resolve with /liquidate.
• Keep a sweep over GET /v1/conversions?status=standby filtering by old standby_at, especially if the integration depends on webhooks that may miss delivery.
• Agree internally on a decision SLA shorter than 7 days to force resolution before the limit.

Next steps

• Standby and manual liquidation: the path that avoids abandoned.
• Per-user, per-type lock: how the lock releases when the conversion ends.