Under the currently confirmed product architecture, the AllSwap application layer does not generate the one-time deposit address, hold its private key, or have a unilateral way to transfer, freeze, or pause funds at that address. It therefore cannot simply move a user's deposit as if it controlled a balance in a centralized account. This does not mean that the underlying settlement network has no control over funds or that the transaction is risk-free. After paying, compare the order details with the source-chain payment transaction hash and the final destination-chain receipt. If the order is refunded, verify the final refund received on-chain as well. Only when these records agree can you establish where the funds for that order actually went.
What does a one-time deposit address do in a swap?
A one-time deposit address is the payment endpoint for a specific swap. It allows the user's source-chain transfer to be matched to that order. AllSwap is a non-custodial cross-chain swap aggregator, not a centralized exchange that holds long-term user balances. You do not first top up a personal platform account and then trade from that account. Once an order is created, the underlying market-making and settlement networks execute the swap according to the specified assets, networks, amount, and recipient address.
However, “non-custodial” should not be interpreted to mean that no participant ever handles or controls the order's funds at any point. The underlying market-making network's settlement mechanism generates the one-time deposit address and returns it with the order. The AllSwap application layer displays and passes along the payment instructions, but it does not possess the address's private key or the unilateral ability to dispose of the funds. After payment, the assets enter the underlying settlement path. Until the destination assets or a refund have actually arrived, the individual transaction remains exposed to risks such as network congestion, liquidity changes, settlement-network failures, and manual processing.
The public information does not specify whether the underlying permissions are implemented through smart contracts, MPC, solvers, or another mechanism. You therefore should not infer that no participant can ever touch the funds. Nor should “non-custodial” be treated as proof of reserves, insurance, a guarantee of settlement, or a promise of zero risk. The AllSwap security overview explains the published product boundaries, but it does not replace on-chain verification of your own order.
How can I reduce the risk of an unclear fund trail before paying?
- Create the order only through an official entry point. Enter the AllSwap cross-chain swap interface yourself. Do not use a deposit address supplied in a search ad, private group message, or message from an unfamiliar support account.
- Check every payment instruction. Confirm that the source asset, source network, exact amount, one-time deposit address, and payment countdown all match the current order. If the page returns a
depositMemo(a payment memo or tag), enter it exactly. Do not invent one if the order does not provide it. - Pay only once and exactly as instructed. Do not treat the one-time address as a reusable top-up address. Do not underpay, overpay, split the payment into several transfers, or pay after the countdown expires. These transfers may not be matched automatically and may require manual investigation.
- Save complete order evidence first. At a minimum, record the order ID, deposit address, asset, network, amount, recipient address, refund address if one was entered, countdown, and redacted screenshots of the order page. Redaction should hide unrelated personal information, such as a name or account identifier, while leaving the order fields needed for verification visible.
How do I build an independently verifiable evidence trail after paying?
A transaction hash, or TxID, is the unique identifier of an on-chain transaction. A block explorer is a tool for reading the public records of a blockchain. Verify the transaction in this order:
- Verify the source-chain payment first. Copy the source-chain TxID from your wallet or exchange withdrawal record and open it in a trusted explorer for the correct network. Confirm that the transaction succeeded and gained confirmations, that the recipient equals the order's one-time deposit address, and that the token contract, amount, and memo, if applicable, are correct. Tokens with the same ticker are not necessarily the same asset, so check the actual network and token contract address.
- Compare it with the order status. A successful source-chain transaction proves only that assets moved from the paying address to the deposit address. By itself, it does not prove that the swap has completed or show where the final settlement will arrive. Also check whether the AllSwap order has moved from waiting for payment to processing, and confirm that its order ID, deposit address, and payment details match.
- Verify the destination-chain result last. After a successful swap, look up the destination-chain TxID in an explorer for the destination network. Check the transaction status, destination token contract, received amount, and recipient address. The swap is proven to have settled only when the destination-chain record matches the recipient address in the order.
- For a refund, verify the complete refund path. If the order included a refund address, confirm from the refund TxID that the asset, amount, and actual recipient correspond to that address. If no refund address was entered, the first refund TxID into AllSwap's fallback refund address proves only that the fallback address received the funds; it does not prove that the user has been refunded. The user must contact official support with verifiable proof of payment. After review and a manual refund by the platform, verify the final on-chain transaction showing that the refund actually reached the user. The refund evidence trail is complete only when this final receipt is consistent with the order and the approved claim. See the AllSwap refund guide for the follow-up process.
This method keeps a website status separate from evidence on a public ledger. Labels such as “processing,” “success,” or “refunded” are order statuses; they are not substitutes for on-chain settlement evidence. Likewise, the source-chain TxID proves only that the user paid the one-time deposit address. It does not by itself prove a successful swap. A successful order requires a source-chain payment record and the actual destination-chain receipt. An order with a specified refund address requires the source payment and the refund received at that address. If no refund address was specified, the final on-chain receipt from the platform's manual refund must also be verified.
Which problems require immediate contact with official support?
Do not pay the same address again if the source-chain transaction is successful and sufficiently confirmed but the order does not recognize it; if the order remains in processing for an unusually long time; if it shows success without a verifiable destination-chain receipt; if it shows a refund but no refund TxID can be found; or if the order enters FAILED. FAILED may mean that the order accepted the deposit but cannot complete settlement or refund automatically and needs manual handling. It does not promise that the funds will be refunded automatically or within a fixed period.
Save the order ID, one-time deposit address, source-chain TxID, destination-chain or refund TxID if available, payment time, assets, networks, and redacted screenshots. Contact official support at [email protected] or Telegram @allswapservice. You can also follow the steps for an AllSwap swap that has not arrived. Support does not need your private key, seed phrase, wallet password, verification code, or remote-access permission to investigate an order. Do not trust anyone who asks for these secrets or demands an additional “unfreezing fee.”