Plan two transfers: one small test, then the treasury amount after the test arrives. You are moving funds between different blockchains, which keep separate records. A test checks that the destination, asset, and route work for your specific task.
If your test also needs to convert the asset, Biswap provides a cross-chain bridge and swap service; use swap tokens across chains with Biswap for that combined task. The test should match the real transfer’s source network, destination network, and token pair. Otherwise, it checks a different route.
Choose a test amount that can show a real result
Send the smallest amount that can complete the route and appear clearly in the destination wallet. There is no universal safe test amount: route minimums and fixed network charges vary. Check those costs before sending, and keep the test small enough that a failed transfer would not disrupt your budget.
For example, say the treasury plans to move $10,000 in a stablecoin, a token designed to keep a steady value. A $20 test might be enough for one route, while another route may need more to cover fixed charges or meet its minimum. Treat that figure as an example, not a Biswap limit.
Keep the test and main transfer as similar as possible. Use the same wallet, destination address, token, and route. If you change any of them, the test no longer checks that part of the planned move.
Check both sides before repeating the transfer
First, confirm the test left the source wallet. Then check the destination wallet for the expected token and amount. A submitted transaction alone does not prove the funds arrived: a cross-chain route can involve a source transaction followed by a separate destination action.
Compare the received amount with the estimate, allowing for the charges shown before the transfer. If you swapped tokens, also check that the destination token is the one the treasury needs. Similar names can refer to different assets, so confirm the asset’s network and identity in the wallet or your team’s records.
Suppose the test arrives but the amount is lower than expected. Pause and compare the estimate with the received amount before sending the balance. A small difference may reflect charges or price movement; a wrong token or destination means the setup needs fixing first.
Send the main amount only after the test passes
Record the source transaction, destination receipt, token, and received amount for your treasury records. Once those match the plan, send the remaining balance using the same details. Biswap is relevant when the task requires moving funds across networks and swapping them in one flow; the test helps confirm that exact combination before the larger amount follows.
If the test fails or remains pending, do not submit another transfer just to see if it works. Check the transaction status and route instructions, then resolve the issue before retrying. This avoids duplicate transfers when the first one is still processing.
Should I test with the same token I plan to send?
Yes. Use the same source token and, if swapping, the same destination token. A test with a different asset may use a different route or have different costs. It cannot confirm that the treasury’s planned token will arrive as expected.
Can I send the main amount while the test is pending?
Wait until you can verify the test at the destination. Pending means you do not yet know whether the funds arrived or what amount was received. Sending again too soon can create a second transfer while the first is still underway.
What if the test arrives but the main transfer gets a different estimate?
Review the new estimate before sending. Prices, available liquidity, and network charges can change between transfers. A successful test confirms the setup worked at that time; it does not guarantee the same received amount later.
Decision rule: send the main balance only when a small test using the same route arrives as the correct asset in the correct wallet.