Page cover
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Failed Transactions & Refunds

What causes swap failures, how refunds are handled by ESPs, and what information support needs from you

Most Husher swaps complete successfully. When issues do occur, this page explains why, what happens next, and how refunds are handled.

Husher does not custody funds. Refunds are processed by the Exchange Service Provider (ESP) involved in execution.

Husher cannot force refunds but will assist with communication between you and the responsible ESP.

Common Failure Causes

Failures typically occur due to one of the following:

  • Wrong network used when sending funds

  • Incorrect or expired deposit address

  • Deposit below the minimum required amount

  • Deposit outside the allowed time window (fixed-rate orders: typically 15 minutes)

  • Network congestion delaying confirmations beyond the expected window

  • ESP-side outages or liquidity issues

  • Compliance or risk flags applied by ESPs

  • Extreme market movement causing quote expiration

Husher itself does not execute trades or hold funds. The responsible party for each failure type is the relevant ESP or the blockchain network.

Refund Handling

Refund behavior depends on the cause:

Cause
Outcome

Wrong network or address

Usually irreversible. Some ESPs may attempt recovery for a fee if technically possible.

Under-minimum deposit or expired quote

Often refunded automatically, minus network fees.

Fixed-rate underpayment

Order cancelled; deposit refunded.

Fixed-rate overpayment

Promised output delivered; excess is not returned.

Provider-side failure

Full or partial refund initiated by the ESP, minus incurred network costs.

Compliance hold

Funds may be held pending review. Outcome depends on ESP policy.

Fixed-Rate Refund Scenarios

Fixed-rate orders provide price certainty by locking the exchange rate at order creation. Because of this guarantee, they follow stricter execution rules. If any of the conditions below are not met, the order is cancelled and refunded automatically by the execution provider.

Scenario
What happens

Deposit below the required amount

Order cancelled; deposit refunded. Partial deposits cannot execute at a locked rate.

Deposit after rate lock expiry (typically 15 minutes)

Order cancelled; deposit refunded automatically.

Deposit above the required amount

Swap executes at the locked rate. Only the promised output is delivered. Excess funds do not increase output and are not returned.

Important notes for fixed-rate orders:

  • Fixed-rate orders prioritize certainty over flexibility

  • Refunds are automatic and handled by ESPs

  • Network fees may still apply even on a refund

  • Always verify the deposit amount and send before the lock window closes

If flexibility matters more than certainty, use a Float-rate order instead.

Typical timelines

Case
Expected resolution time

Automatic returns

Minutes to a few hours

Manual ESP review

1 to 48 hours

Network recovery attempts

Days to weeks (if possible at all)

Compliance reviews

Variable

Most simple cases resolve without any intervention from the user.

What support needs from you

When contacting support, provide the following:

  • Input transaction hash (TXID)

  • Deposit address used

  • Approximate date and time

  • Screenshot of quote or error (if available)

  • Expected output wallet address or addresses

Do not resend funds unless instructed by official support.

Last updated