Documentation Index
Fetch the complete documentation index at: https://docs.prudra.dev/llms.txt
Use this file to discover all available pages before exploring further.
Cross-chain transfers
Cross-chain transfers use the Li.Fi bridge aggregator to move tokens across EVM chains. Unlike direct or swap transfers that confirm in seconds, bridge transfers take 1–20 minutes to complete on the destination chain.How bridging works
Status lifecycle
A bridge transfer starts aspending and moves to confirmed when the destination chain confirms the transaction:
| Status | Meaning |
|---|---|
pending | Source chain confirmed, waiting for destination chain |
confirmed | Destination chain confirmed, tokens received |
failed | Bridge failed — funds returned to source wallet automatically |
Handling pending transfers
Thetransfer() call returns immediately when the source chain confirms. Poll or use webhooks to know when the bridge completes:
Using webhooks instead of polling
Register fortransfer.completed to avoid polling:
transfer.completed webhook payload:
Bridge failure handling
If the bridge fails (rare), Li.Fi automatically returns funds to the source wallet. Prudra fires atransfer.failed webhook:
Supported bridge routes
Bridge availability depends on Li.Fi liquidity for the specific token pair and chain pair. All chains in the managed wallets chain table can bridge USDC between each other.Related
- Transfer routing — when bridge route is selected
- Track status — monitoring transfer status
- Webhooks — setting up webhook endpoints

