When a customer sends stablecoins on the wrong network, the blockchain does not reject the payment. The transfer completes on the network the customer chose, and the funds stay at the address the customer entered, on that network. What happens to those funds next depends mostly on the business that was meant to receive them.
For a business that accepts deposits, the outcome is decided before the customer sends, by three things: the networks it watches, who controls its address on each one, and where it sends a return. This guide is written for the payments and product teams at neobanks, card issuers, PSPs, remittance providers and other businesses that receive stablecoin deposits from their customers. After working through the cases, the guide ends by explaining how Rhino.fi handles them with its Smart Deposit Addresses , part of its Stablecoin Activation Stack .
A typical case starts when a customer withdraws 2,000 USDT from an exchange and sends it to a deposit address shown by their remittance app. The exchange asks which network to use and shows a different fee for each, so the customer usually picks the cheapest. Because the app only watches Ethereum and TRON, however, the deposit never appears, and what usually happens next is that the customer opens a support ticket. To the customer the money seems to have vanished, which is why the problem weighs so heavily on the experience of a payments app.
Quick Answer
A stablecoin sent on the wrong network is not rejected but arrives at the matching address on the network the sender chose. If the receiving business controls that address on that network and watches it, it can credit or return the funds; if nobody controls the address on that network, the funds cannot be moved.
Why do stablecoin payments end up on the wrong network?
The same stablecoin is issued on many networks, and the sender, not the receiver, chooses which one carries the payment. Tether lists USDT as issued on 13 networks , including Ethereum, TRON and Solana. Each network is a separate blockchain with its own record of who holds what, so a token on one does not exist on another. Not only that: on each network the same stablecoin has its own smart contract, so technically they are different tokens, even with the same ticker — which can often be confusing.
The network is chosen by the sender at the moment of sending, and an exchange’s withdrawal screen, as a rule, does not show which networks the receiving business supports.
Address formats then make the mistake easy within one family of networks. Ethereum and the EVM networks (Ethereum Virtual Machine), built to run Ethereum’s software, share one format: 42 characters starting with 0x. An address issued for Ethereum is therefore also a valid address on Arbitrum, Base, Polygon or BNB Chain, and a wallet will send to it on any of them.
Networks outside that family, by contrast, use other formats. A TRON address shown in a wallet, for example, is 34 characters starting with T, so a wallet will normally refuse an Ethereum address for a TRON transfer. Rhino.fi’s guide to USDT on TRON covers that network in more detail.
Where do the funds go after a wrong-network transfer?
Once the network has confirmed a transfer, it cannot be undone, so the funds always land somewhere. The outcome then turns on two questions: whether someone controls the receiving address on that network, usually through its private key (the secret number that authorises spending from an address), and whether anyone is watching it. Four cases cover most wrong deposits.
Case
Where the funds are
Who can move them
Another EVM network, same address
At the same address on the other network
Whoever holds the key to that address, if a key controls it
A network with a different address format
Usually still with the sender, because the wallet refuses the address
Nobody needs to, unless the transfer went through
The right network, a token the business does not accept
At the business’s address
The business, once it notices
An address the business no longer watches
At the business’s address
The business, once it notices
Another EVM network, same address
Most deposit addresses are controlled by a private key, and on EVM networks the same key controls the same address on every network, so whoever holds that key can move funds sent on the wrong one. To do so, they need a small amount of that network’s native coin to pay the transaction fees (gas), and before that someone has to notice the deposit. Rhino.fi, for example, detects and settles these deposits on every EVM network listed for the address, as its own section below explains.
The exception is a smart contract account, which is an address run by a program on the network instead of a single key. A multisignature wallet, which needs several approvals before it spends, is one example, and that kind of address works only on the networks where the contract has been set up. A telling case happened in June 2022: 20 million OP tokens (Optimism’s native token) were sent by the Optimism Foundation, on Optimism, to a multisignature address that the market maker Wintermute had set up on Ethereum but not yet on Optimism. An attacker set up a contract at that address on Optimism first and took control of the tokens.
A network with a different address format
Between networks with different formats, such as Ethereum and TRON or Ethereum and Solana, most wallets and exchanges check the address before sending and refuse one that does not fit. The common outcome is therefore a failed attempt, and the funds stay with the sender. Where a transfer does go through, the funds belong to whoever controls the destination address on that network.
The right network, a token the business does not accept
A customer can use the right address on the right network and still send a token the business does not accept, either a different stablecoin or another version of the same one. On several networks, USDT and USDC exist in more than one version, and each version has its own token contract (the program that records balances of that token), as Rhino.fi’s supported chains table shows network by network. Rhino.fi’s guide to stablecoin settlement explains how these token versions differ by chain, and Rhino.fi’s article on USDT vs USDC explains why two dollar tokens are not always worth exactly the same, that is, 1 dollar each.
The funds arrive at the business’s address, but a system that only watches the tokens it accepts does not see them reach the balance. Monitoring of unsupported tokens usually covers a selection of them on each network, so some of these deposits arrive without an alert. Rhino.fi, for example, sends the business a rejection event for the unsupported tokens it monitors on each network.
An address the business no longer watches
Customers reuse addresses, because they save them in an exchange’s address book and send to them months later, after the business has retired the address, changed provider or paused it. The deposit lands at an address the business still controls, but with nothing watching it, nobody credits it until the customer asks. Some infrastructure providers, such as Rhino.fi, monitor every deposit address they issue for years (seven in Rhino.fi’s case, and the period can be extended on request).
What does it cost to recover a wrong-network deposit?
When a deposit reaches the business’s own address, the customer loses access to the money and the business holds the key, so getting it back becomes the business’s operational work. That work runs in five steps, and each carries a cost.
Step
What it involves
Finding the deposit
Watching a network the business does not support, or searching after a ticket arrives
Working out whose it is
Seconds when each customer has their own address, and much longer when deposits share one
Confirming where to return it
Checking the destination, because the obvious one, the sending address, often belongs to an exchange
Moving it
Holding gas on a network the business may not otherwise use
Recording it
Keeping the ledger and the compliance record complete
In one example, a payments app holds every customer balance on Arbitrum. When a customer sends 500 USDC on Polygon to the address shown in the app, the funds sit at an address the app’s operator controls, but its system never reports them. Support escalates the ticket to engineering, and someone buys gas on Polygon to move the funds by hand.
The return address is the step that needs the most care. Deposits from exchanges usually come from a pooled wallet, an address the exchange uses to send many customers’ withdrawals, so funds sent back to it reach the exchange, not the customer’s account, and may never be credited. A return therefore needs an address the customer has shown they control.
Large exchanges handle the same problem for their own deposits, and Binance’s terms show what it involves. Binance’s self-service recovery collects its fee only if retrieval succeeds, estimates up to 30 working days for deposits on unsupported EVM networks and states that successful recovery is not guaranteed.
How can a business design deposits so a wrong network cannot cost funds?
Most wrong-network losses come from choices made before launch, and each has a fix. Seven design decisions either remove the case or turn it into routine work:
The business watches the major networks where its address is valid, including networks it does not advertise, which Rhino.fi’s stablecoin settlement guide also describes as the safer setup.
Each customer gets their own deposit address, so any deposit identifies who sent it.
Addresses are controlled by a key on every network the business watches, or the business confirms that a smart contract account exists on each network before it shows that address.
The network appears next to every address, and each network with a different format gets its own labelled address.
The business decides before launch what happens to a token it does not accept: convert it, return it or hold it for review.
Funds go back only to an address the customer has verified, never by default to the sending address, for the reason described earlier.
Every address the business has issued stays under watch for as long as a customer could still send to it.
How Rhino.fi handles a deposit on the wrong network
Rhino.fi gives each end customer Smart Deposit Addresses (SDAs), which are reusable deposit addresses that accept supported stablecoins and settle each deposit to the network, token and wallet the business chooses. Rhino.fi therefore handles wrong-network deposits in two ways: through how the address works, since one SDA covers every listed EVM network, and through a refund service for the deposits the address cannot settle.
Every EVM network on one address
On EVM networks, a single address covers the case described earlier:
One SDA works on every EVM network the business lists when it creates the address.
Rhino.fi’s documentation advises listing every EVM network that supports SDAs, even ones the business does not advertise.
When a customer sends on the wrong EVM network, Rhino.fi still detects the deposit and settles it to the business’s destination from its own liquidity, like any other deposit.
Its own address on each non-EVM network
Networks with other address formats are handled with separate addresses:
Networks such as TRON, Solana, Bitcoin and Stellar each get their own address.
Most integrations show customers three addresses: one for EVM networks, one for Solana and one for TRON.
On TRON, SDAs accept USDT only, since Circle stopped minting USDC on TRON in February 2024.
The supported chains table lists which networks and tokens SDAs accept.
Tokens and networks Rhino.fi does not support
Rhino.fi checks each deposit before it processes it, and a deposit that fails the checks follows a set path:
Rhino.fi processes a deposit when the token is supported on that network, the amount is within the business’s limits and the deposit passes anti-money laundering (AML) screening, which Rhino.fi runs through TRM Labs.
When Rhino.fi rejects a deposit, for example one below the minimum, it sends the business a webhook (an automatic message from Rhino.fi’s system to the business’s), and for unsupported tokens it sends this event for the ones it monitors, as described earlier.
Rhino.fi refunds deposits in an unsupported token or on an unsupported network to a verified address, and the business’s account manager arranges each refund.
A business can set a default refund address for each SDA, which Rhino.fi then offers as the refund destination, and the documentation advises setting it only where the customer controls that address.
Rhino.fi monitors each SDA for seven years, as described earlier.
What the refund costs
Refund processing is part of every Rhino.fi plan:
Refund processing is included in every plan on Rhino.fi’s pricing page .
In that page’s words: “We chase, recover and return those deposits, so you do not have to restrict what your users can send in order to keep your support queue manageable.”
The Scale plan adds priority refund resolution.
The same SDAs, with the same detection and refund rules, sit under Rhino.fi’s flows for payment service providers , neobanks and card issuers , banking-as-a-service providers and remittance providers . To check which networks and tokens your own flow needs, talk to the Rhino.fi team.
Sources
Rhino.fi documentation, Smart Deposit Addresses
Rhino.fi documentation, supported chains
Rhino.fi documentation, webhook events
Rhino.fi pricing
Rhino.fi, AML screening through TRM Labs: confirmed by Rhino.fi, November 2026
Rhino.fi blog, stablecoin settlement
Rhino.fi blog, USDT vs USDC
Rhino.fi blog, TRC-20 USDT
Tether, supported protocols
Circle, “Circle is Discontinuing Support for USDC on the TRON Blockchain”, 21 February 2024
ethereum.org, Ethereum accounts
TRON developer documentation, accounts
The Block, “Attacker snipes 20 million OP tokens intended for Wintermute loan”, 8 June 2022
Binance, self-service recovery FAQ