feat: show failed destination swap

[gsteenkamp89]

closes FE-95

Morivation

In cases where the destination swap failed, we need to inform the user that they received the bridge token and it's amount.
This solution is a bit hacky since we rely on both the deposit/status endpoint for the initial status of the fill, then we use the /deposit endpoint for more detail, ie the amount received in the bridge token.
In future PR's we should consider removing reliance on the status endpoint altogether and simply use the more data-rich /deposit endpoint.

Examples

Failed swap (USDT => ACX)
Link

Success (USDC => USDT)
Link

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app-frontend-v3	Ready	Preview, Comment	Feb 5, 2026 3:45pm
sepolia-frontend-v3	Ready	Preview, Comment	Feb 5, 2026 3:45pm

[linear]

FE-95 Show destination swap failed on confirmation screen

[0xjorgen]

LGTM! Clean implementation for handling failed destination swaps. The actionsSucceeded === false check is correct per indexer logic.

nit: Line 303 in DepositTimesCard.tsx - the non-null assertion (finalOutputAmountUsd!) could be avoided by adding it to the conditional check above.

[0xjorgen]

will this crash if finalOutputAmountUsd is undefined?

[gsteenkamp89]

it might, good catch!

Found issues while testing

[0xjorgen]

I got this error when briding same assets

{
    "type": "AcrossApiError",
    "code": "INVALID_PARAM",
    "status": 400,
    "message": "Query param 'refundOnOrigin' must be 'true' for same-asset bridge swaps.",
    "param": "refundOnOrigin",
    "id": "lrbxq-1770280421988-eea295f2c127"
}

[0xjorgen]

I also get

{
    "error": "DepositNotFoundException",
    "message": "Deposit not found given the provided constraints"
}

when bridging from usdc(eth) to usdt(arb)

[gsteenkamp89]

I also get

{
    "error": "DepositNotFoundException",
    "message": "Deposit not found given the provided constraints"
}

when bridging from usdc(eth) to usdt(arb)

Is the error here that the deposit actually succeeded?

[gsteenkamp89]

I got this error when briding same assets

{
    "type": "AcrossApiError",
    "code": "INVALID_PARAM",
    "status": 400,
    "message": "Query param 'refundOnOrigin' must be 'true' for same-asset bridge swaps.",
    "param": "refundOnOrigin",
    "id": "lrbxq-1770280421988-eea295f2c127"
}

Ah I did not know this was a restriction 🤔

[0xjorgen]

Yeah, it feels like this should be handled on the api side. not client-side logic