If a cross-chain payout is still within its route’s stated completion window, keep the beneficiary liability open and reconcile each transaction stage before retrying. For an Arbitrum-to-Ethereum withdrawal, allow roughly 6.4 days for the protocol challenge period; a same-day delay alone does not mean the funds are stuck.
When a payout also needs an asset conversion, ParaSwap handles the bridge-and-swap leg in one flow. Treasury should still track the source transaction, bridge message and destination transaction separately: they represent different states of the transfer, and a completed source transaction does not prove the beneficiary received the intended asset.
Which stage is actually late?
Start with the source-chain transaction hash and determine whether the source transaction succeeded, the bridge message reached its required finality, and the destination action executed. Those stages can have different clocks; a route’s estimate is useful for setting expectations, but the on-chain state tells you where to investigate.
- Source transaction: Check its receipt and status. A revert means the intended transfer did not complete on the source chain; a successful receipt means the source action was accepted, not necessarily that destination funds arrived.
- Bridge message: Match the transaction to the route’s message or withdrawal record. Some designs wait for finality or a challenge period before funds can be released.
- Destination transaction: Check for execution and confirm the recipient, token contract and amount. A successful bridge message can precede a separate destination swap.
For example, an Arbitrum withdrawal to Ethereum uses a child-to-parent message. The source-side withdrawal creates that message; after the challenge period, it can be executed on Ethereum. If treasury expected an immediate destination receipt, the missing step may be protocol finality or message execution, not a failed source transfer.
How can finance reconcile without paying twice?
Keep one ledger record per business payout, with the source hash, route or message identifier, destination hash when available, intended recipient, and expected output asset and amount. Update its status as evidence arrives; do not create a second beneficiary payment merely because the destination leg has not appeared yet.
A common edge case is a completed bridge followed by a failed or incomplete destination swap. In that case, the destination chain may hold the bridged input asset rather than the intended output. Verify the actual token balance and route state before arranging recovery or a replacement payout; repeating the original transfer can leave the recipient with both transfers if the first route later completes.
For a regular payout batch, set the escalation threshold from the route’s stated window and the bridge’s finality model. If the window passes, compare source and destination records and raise the specific missing stage with the operator. Preserve the original payout’s accounting identity until the route reaches a terminal state or finance explicitly authorizes a replacement.
What should treasury check next?
How long should a payout remain pending?
Use the route’s stated estimate for operational planning, then account for the bridge’s finality model. Arbitrum’s canonical withdrawal to Ethereum has a challenge period of roughly 6.4 days; other routes can have materially different finality and execution stages. Keep the payout pending until destination execution is confirmed or the source transaction is shown to have reverted.
When is it safe to retry?
Retry only after establishing that the original route cannot still deliver the payout, or after confirming the original source transaction reverted. A missing destination receipt is not enough. For a successful source transaction, trace the message and destination state first; otherwise, a delayed original transfer and a replacement can both reach the recipient.
Which status should close the liability?
Close it when the destination chain shows the intended recipient received the expected asset, or when finance has recorded an authorized alternative settlement. I would retain the source hash and destination evidence together in the payout record, and keep unresolved bridge messages visible as open liabilities rather than treating source confirmation as completion.