Your business became the integration layer.
Nobody decided this. But somewhere between your customer having dollars and you having spendable money, a job appeared — and it landed on whoever in your office knows the most about crypto.
Here is the thing that catches people. USDT on Tron and USDT on Ethereum are different tokens. Not different denominations of one token, not different accounts at one bank — different, non-interchangeable assets that happen to share a name and a price. The same is true of USDC on Base and USDC on Solana. You cannot send one to an address expecting the other. There is no clearing house that reconciles them for you overnight.
To a business receiving foreign revenue, this is invisible until the day it is not.
The moment it becomes your problem
A Lagos software agency invoices a US client $40,000. The client’s finance team pays in USDC, because their treasury sits in USDC and a wire takes four days. They send it on Base, because that is where their treasury is and it costs them almost nothing.
The agency’s Nigerian settlement partner accepts USDT on Tron. Perhaps also USDT on Ethereum. Not USDC on Base.
The money has arrived. It is real, it is theirs, it is worth $40,000, and it cannot be turned into money you can spend.
Nothing failed. No error was returned. The payment worked exactly as instructed, and the money is stranded anyway.
What happens next is worse than the problem
Somebody at the agency now has to work out that USDC on Base and USDT on Tron are not the same asset — which is not obvious to a non-crypto person, and there is nothing on screen telling them. Then find a route between them. Then acquire gas on a chain they hold nothing on. Then choose, without knowing the difference, between an issuer-native path and a bridge that mints a wrapped token.
Then execute it correctly, first time, with $40,000 and no undo. Sending to the wrong chain is not reversible. There is no support line.
The alternative is asking the client to send it again, which means explaining chains to your customer while the first $40,000 sits where nobody can reach it. That conversation costs more than the payment.
Why the gap is widening, not closing
Nigerian off-ramps each support two or three chains. That is not laziness. Every chain a desk adds means an indexer, a confirmation policy of its own, reorg handling, a hot wallet, gas management and a new way to lose money at three in the morning. Two or three is a rational number to stop at.
Meanwhile corporate treasuries keep diversifying. Base did not exist in 2022. Solana’s share of stablecoin activity has grown fast. Tron still carries the largest share of USDT transfer volume, which is exactly why Nigerian desks concentrate there. The payer’s options keep widening; the receiver’s do not.
That gap is a product. Whether it is a large enough product is a different question, and an uncomfortable one.
What we think the answer looks like
The receiving business should never have to know any of this. One permanent account identity, given to customers once. They pay through whatever supported rail they already use. We detect the payment, screen the sender, match it to the invoice you were expecting, route it through approved infrastructure, convert it and settle in your own currency — with a record of exactly what happened and what each step cost.
The account is the identity. The addresses underneath are infrastructure, and infrastructure is ours to worry about.
One caveat we will keep repeating: this only ever means a defined set of supported assets and networks. Not “any chain”. Nobody can honestly promise that, and the payment page should never offer a rail that would fail.