You can swap across chains straight into an exchange deposit if the final payment includes its required tag or memo. The receiving address identifies the exchange wallet; the reference tells it which customer to credit. A cross-chain service such as omnichain can handle the swap, provided its route supports that reference.
An exchange may need an address and a reference
An exchange often pools customer deposits in one wallet. A destination tag or memo is an extra number or text attached to a payment so the exchange can identify whose balance to update.
For example, an XRP deposit may show an XRPL address and a destination tag such as 789. The address points to the exchange’s wallet; the tag identifies your account in its records. Stellar deposits can use the same pattern with an account address and a memo.
The reference is not part of the address, and it is not optional when the exchange requires it. The XRP Ledger documentation explains that hosted accounts use destination tags to identify the customer or purpose of a payment. Stellar’s documentation describes exchanges using a shared account with a unique memo ID.
The final payment must carry the reference
In an omnichain swap, you send one asset on a source chain and receive another on a destination chain. The service routes the transaction between them. To credit an exchange deposit, the last payment must reach the exchange’s exact deposit address and include its required tag or memo.
Say you hold USDC on one network and want XRP credited to your exchange account. You need the exchange’s XRP deposit address and its XRP destination tag. The swap route must be able to send XRP on the XRP Ledger with that tag attached; knowing the address alone is not enough.
References are chain-specific payment data, not a universal field shared by every network. One network may call it a tag, another a memo, and another may not use one at all. So check that the route supports the reference on the destination chain, not merely that it can deliver the right token to an address.
If the route asks for a reference on the source deposit too, treat it as separate information. That source-side reference identifies your incoming payment to the swap service; it does not replace the reference required by the exchange receiving the final asset.
Verify the deposit details before you send
Use the exchange’s current deposit instructions to confirm the asset, network, address, and reference. Then check that the swap route names the same destination network and provides a place to pass the required tag or memo. If it cannot carry that data, choose a route that can or use a different deposit method.
For instance, if an exchange requests XRP on the XRP Ledger with tag 789, a route to XRP on another network is not equivalent. Nor is an XRP Ledger payment to the right address without tag 789. The exchange may not be able to credit either payment automatically.
Compare the quoted amount you will receive with the amount the exchange requires for deposit, if it sets a minimum. The total can reflect network transaction costs and the swap’s quoted rate. Review the final destination details before sending, since a missing or incorrect reference can delay crediting or require the exchange to trace the payment.
The key check is simple: confirm the destination asset and network, then make sure the final payment carries the exchange’s exact reference.