Skip to main content
Splyt Genesis

Crypto markets, protocols and policy

When a Cross-Chain Swap Needs a Manual Claim

A manual claim is a separate transaction that releases funds on the destination chain; learn how to check whether you need one and what to verify first.

The Splyt Genesis Desk

When a Cross-Chain Swap Needs a Manual Claim

A manual claim is one extra transaction you submit on the destination chain to receive funds from a cross-chain swap. It is needed only when that swap’s bridge or delivery process leaves a claim for you to complete.

A swap can confirm on the source chain while its funds are still moving or waiting on the destination chain. That gap is normal for some routes, so check the transaction’s status before trying anything again. If a swap has stalled before the bridge step, quickswap route choices after a stall cover a separate issue: choosing a route for the swap itself.

Why does a cross-chain swap need a manual claim?

A manual claim is needed when the bridge has delivered or made funds claimable on the destination chain, but has not completed the final release automatically. The claim transaction tells the destination chain to release those funds to the address set by the bridge.

Cross-chain swaps involve steps on two separate networks, so a successful source transaction does not prove that the destination delivery is complete. Depending on the route, the bridge may deliver the asset automatically, ask you to claim it after a wait, or handle a failed delivery through a retry or refund. The process varies by bridge.

How can you tell whether a claim is really required?

Check the swap’s status in the service you used and compare it with the source and destination transaction records. A source transaction marked successful confirms that the first step ran; it does not confirm that the destination asset reached your wallet.

Look for a clear status or button saying the funds are ready to claim. Then verify the destination network, token, amount, and receiving address shown for that transaction. If the status says a retry or refund is still in progress, wait for that process to finish instead of submitting a claim.

  • Source transaction successful: your original transfer step completed.
  • Destination transaction pending: delivery may still be in progress.
  • Claim available: the service says you can complete a destination transaction.
  • Refund pending: the bridge is returning funds through its recovery process.

What do you need before submitting a claim?

You need access to the wallet that controls the claim and enough of the destination chain’s native token to pay its transaction fee. The token being claimed may not pay that fee. For example, a token transfer can require the chain’s native currency for a separate claim transaction.

Use the swap service’s official transaction page or the bridge’s official claim flow, and match the transaction details before you sign. A claim is an on-chain instruction, not a way to cancel the original swap. If the details do not match your transfer, stop and check the service’s status or support guidance.

What happens after you claim?

The claim itself must be submitted and confirmed on the destination chain. Once confirmed, check your wallet on that network for the delivered token; the token or amount can differ from what you first sent if the route included a conversion before or after bridging.

If the claim fails, do not assume the funds are gone or repeat it with different details. Check whether the transaction failed on-chain, whether the claim remains available, and whether the bridge status changed. Watch the destination status next: a confirmed claim or a completed retry is the signal that delivery is finished.