Funding should stay simple in the UI. A trader selects the funding path, token, chain, and amount. Backend route generation, status polling, and transfer handling should stay out of the main copy unless user action is required.Documentation Index
Fetch the complete documentation index at: https://docs.polychads.app/llms.txt
Use this file to discover all available pages before exploring further.
Deposits
Deposits should support direct crypto transfer routes where available. The UI should show the selected asset, chain, destination address, and QR code only when the address is ready.Withdrawals
Withdrawals should ask for recipient address, amount, receive token, and receive chain. When the bridge route is available, the user confirms withdrawal. Internal bridge addresses and generated funding steps should not be presented as instructions for the user to manually complete.Status handling
| Status | UI expectation |
|---|---|
| Preparing | Brief inline progress. |
| Waiting | Only shown when user action is actually required. |
| Processing | Compact progress copy with no backend jargon. |
| Completed | Refresh balances and show confirmation. |
| Not available | Disable the action and explain the route or token issue. |