A split payment can fund one cross-chain swap when the order explicitly accepts multiple deposits to its assigned address. Each transfer is detected and confirmed separately, then the service applies its rules for adding eligible amounts to the order.
- Send every part to the same order deposit address, on the same network and in the same asset.
- Wait for each transfer to meet the service’s confirmation rule; one confirmed part does not confirm the others.
- Splitting adds sender-side transaction fees and increases the chance that a part arrives late or falls outside the order’s terms.
One order address ties separate transfers together
A swap service needs a reliable way to associate incoming funds with the right order. A common design assigns the order a unique deposit address or, for Monero, a unique subaddress; the service’s wallet monitors that destination and credits detected transfers to the order.
On Monero, a block explorer cannot show a public address-to-amount transfer in the way an Ethereum explorer can. The recipient wallet scans transactions to detect outputs it controls. Monero’s wallet RPC reports incoming transfers with fields such as transaction ID, amount, height, and confirmation count, as documented by the Monero Project.
On an account-based chain such as Ethereum or TRON, a token transfer to the order address creates a distinct transaction record. The service can identify the recipient and token from the chain data, but its order system still needs to aggregate only transfers that meet the order’s asset, network, timing, and confirmation rules.
Each part has its own confirmation clock
Multiple deposits are not one larger on-chain payment: they are independent transactions, each with its own transaction ID and confirmation state. If you send 0.4 XMR and then 0.6 XMR to the same eligible order address, the service may credit a total of 1.0 XMR only after both transfers satisfy its policy.
As an illustrative timing reference, Monero targets a block about every two minutes, but block inclusion is not a guarantee that an operator will immediately treat a transfer as spendable. Ethereum distinguishes inclusion from later finality; the Ethereum documentation describes a transaction’s progression through inclusion, justification, and finalization. The service chooses what confirmation threshold it requires on each chain, so check the order’s stated rule before splitting.
For a live task, first verify that multiple deposits are allowed for that specific order. If so, send each part to the exact same deposit address, using the exact same network and token; a second order or a similar-looking address will not normally be combined with the first order.
Splitting changes the amount received and the failure cases
Budget by the amount that reaches the deposit address, not by the amount you intend to spend. Each Monero transaction pays its own network fee, and each Ethereum token transfer consumes gas; sending three parts therefore incurs three sender-side transactions rather than one. On Ethereum, the gas cost also depends on network demand and the transaction’s execution.
The tricky case is a partial payment near an order’s minimum or expiry. The first part can be recognized while the second is still pending, or the second can arrive after the service has stopped accepting funds for that order. If a transaction is replaced, dropped, or sent on the wrong network, the amount may not count as a valid deposit at all. The order’s own terms determine whether a late or incomplete amount is credited, refunded, or requires manual handling.
There is also a quote trade-off: a rate fixed for an order may have a time window, while a split payment can take longer to assemble and confirm. If the amount or timing changes the quote, adding a later part may not produce the same output estimate as sending the full amount together. For a task with funds arriving from several wallets, compare the extra transaction costs and timing risk with the convenience of staging deposits.
Use the order’s deposit rules before sending the first part
For a cross-chain swap, an XMR bridge routes the deposit on one chain and sends the exchanged asset to a compatible wallet on another. When you need multiple deposits for one swap, the useful question is whether that specific order aggregates them—not whether the receiving address can technically receive more than one transfer.
Check the accepted asset and network, whether partial deposits are supported, the confirmation threshold, and the order’s expiry before sending. Save each transaction ID and its amount so you can reconcile the parts in your own wallet history; for Monero, remember that public explorers do not reveal the amount and recipient details. The Monero Project’s payment guidance explains how wallet records and transaction proofs differ from public-chain inspection.
In short, multiple deposits can fund one swap only when the order’s rules bind them to the same order and accept their timing and combined amount. Use one assigned address, account for a separate fee and confirmation period for every part, and send the full amount together when the order does not clearly support aggregation.