Earlier this year, I wrote about stablecoins as the next chapter in the evolution of money. They aren't a replacement for the currencies people already use. They're the form those currencies are starting to take as money moves online and across borders.
Since then, I've spent a lot of time with banks, payment providers, brokers, fintechs and exchanges. They're at very different stages and have very different business models, but they keep asking for the same thing. They want to move stablecoins, and they want to do it safely.
That request covers more than payments. It covers money coming in and going out: client deposits, withdrawals, merchant settlement, payouts, and treasury transfers. Every one of those flows ends at a wallet, and every one raises the same question.
My answer keeps coming back to one thing: verify the wallet. Every time, in both directions.
Every transfer starts with a simple question
Before any money moves, someone needs to know who is on the other side.
In traditional finance, that question was answered over decades. Bank accounts are tied to identities. Card networks built layers of authentication and dispute resolution. Trust is baked into the infrastructure, so most people never think about it.
Stablecoin money movement is newer, and that trust layer is still being built. A wallet address on its own tells you very little. It doesn't tell you who controls it, where they are, or whether the transfer should go ahead.
That's the gap wallet verification closes.
Money movement, not just payments
When most businesses think about stablecoin compliance, they think about payments coming in. Who is paying us? Is this person who they say they are? Should we accept these funds?
Those are the right questions, but they're only part of the picture. Money moves in many directions:
- In: customer payments, client deposits, account top-ups
- Out: withdrawals, payouts to sellers, creators and contractors, and merchant settlement
- Across: treasury transfers between an institution's own wallets and its counterparties
In my conversations, the outbound side is often where verification is least mature. Teams have invested heavily in onboarding checks and screening on the way in, while withdrawals and payouts still rely on an address someone typed in or pasted from somewhere else. As stablecoin volume grows, that imbalance won't hold. Verification has to cover every flow.
Onchain transfers are final, so verification has to come first
One of the great strengths of stablecoins is that they settle quickly and with finality. Funds arrive in minutes, not days, and there's no waiting for a batch to clear.
That strength also changes the order of operations. In a system built on finality, you can't rely on catching a problem after the fact. You can't claw back a withdrawal sent to the wrong wallet. The checks have to happen before the money moves.
This is why I think of wallet verification as infrastructure, not a compliance box to tick. It's what lets institutions get the speed of stablecoins without taking on risk they can't control.
What wallet verification actually means
Wallet verification confirms that the person sending or receiving funds controls the wallet involved.
That distinction matters. Control can be proven at the moment of the transaction, with a single click from the wallet the person already uses. It tells a business that the person in front of them can actually act on that wallet, not just that they've supplied an address. And because the address is confirmed from the wallet itself, nobody has to copy and paste anything.
This matters most when the sums are large. When someone is moving significant volume, verification also works as a deliberate check from the user's side. The request they sign names the platform asking for it, so the user is confirming that this wallet is going to be used with this specific platform, and not with a lookalike site or an unknown counterparty. The platform gets a record tying that wallet to its own service. The user gets a clear checkpoint before large amounts move.
Wallet verification works alongside existing identity checks rather than replacing them. A bank or broker may already know who its client is. Wallet verification connects that client to the wallet they're using, which closes the loop between identity and money movement.
At WalletConnect, we've built three further layers on top of that:
- Location and sanctions screening. We can check the IP address behind a wallet connection and screen the wallet against sanctions lists. That adds location-level insight for fraud prevention and restricted-region checks, which wallet data alone can't give you.
- An audit-ready record. Every verification captures proof of control, a timestamp, the chain and session details, and returns it to your systems.
- Configurable capture. The required fields adjust to each institution's compliance requirements.
We built these because the institutions we work with told us they needed more context about who they were moving money with, and a record they could stand behind.
Knowing what you're signing
Verifying the wallet tells you who is on the other side. The next question is whether the person signing understands what they're approving.
Too often, a wallet shows a user a string of raw transaction data and asks them to approve it. For large transfers, that's not good enough. WalletConnect Clear Signing shows the transaction in plain language before anyone signs: what's moving, how much, and where it's going. Users, and the custodians and approvers acting for institutions, can check it properly before approving.
Together, they cover both ends of the risk. Wallet verification confirms the right wallet. Clear Signing confirms the right action.
What it means in practice
The need is the same everywhere, but it looks different depending on who you are.
Banks and financial institutions. When a client asks to withdraw stablecoins to an external wallet, the bank needs to know that wallet belongs to the client before releasing funds. Treasury teams moving funds between the institution's wallets and its counterparties need the same assurance, along with a record that satisfies auditors and regulators. Wallet verification provides both, inside the compliance controls the bank already runs.
Payment service providers. PSPs move money on both sides of a transaction. On the way in, they need to screen the payer before the payment clears. On the way out, they need to confirm that merchant settlement goes to the right wallet. Verifying both sides is what allows a PSP to offer stablecoins to its merchants with confidence.
CFD brokers and trading platforms. Brokers increasingly let clients fund accounts and withdraw in stablecoins. Many need to show that withdrawals go back to a wallet the client actually controls, and to block access from restricted regions. Wallet verification, with IP screening built in, confirms both before funds move in either direction.
Fintechs and neobanks. When users top up an account from a wallet, or cash out to one, the fintech needs to connect that wallet to a known customer. Verification at the moment of deposit or withdrawal means users get credited quickly without opening a gap for fraud.
Marketplaces and platforms. Paying sellers, creators, and contractors around the world means sending funds to thousands of wallets the platform has never seen before. Verifying the destination before each payout means the money reaches the person who earned it.
Exchanges, iGaming and prediction markets. Withdrawals are the highest-risk moment. Confirming wallet control and location before funds leave protects the platform and its users, and helps meet the obligations that come with operating across jurisdictions.
What WalletConnect Wallet Verification looks like
Regulation is turning verification into a baseline
Regulators are moving in the same direction. In Europe, MiCA and the Travel Rule set clear expectations for how providers handle information about the parties to a transfer. Other markets are developing their own frameworks.
I see this as a positive. Clear rules give serious institutions the confidence to build, and they raise the bar for the whole industry. The providers who treat verification as a strength rather than a burden will be the ones regulators, partners, and customers trust most.
What WalletConnect Travel Rule capture looks like
Verification should be invisible to the user
None of this works if it adds friction. People expect moving money to be simple, and stablecoins should feel as easy as any other way to pay or get paid.
The best verification happens in the background, inside the flow the user is already in. They connect the wallet they already use, confirm, and move on. The institution gets the assurance it needs, and the user barely notices it happened.
That balance is the goal: strong verification that feels effortless.
What I expect next
Based on the conversations I'm having, I expect three things.
First, wallet verification will become standard across every stablecoin flow, in and out, in the same way identity checks became standard for opening an account.
Second, verification will become reusable. A user shouldn't have to prove control of the same wallet over and over. The industry will move toward verification that travels with the user, across the 700+ wallets and 80,000+ apps connected through networks like ours.
Third, trust will become the competitive edge. As stablecoin money movement grows, the institutions that can prove who they're paying and who's paying them will win the partnerships, the licences and the volume.
Every evolution of money has depended on trust, and stablecoins are no different. The technology to move value instantly is already here. The work now is making sure every transfer goes to, and comes from, the right place.
Verify the wallet. Both ways.
What is wallet verification?
Wallet verification confirms that the person sending or receiving funds controls the wallet involved before the money moves.
Why does wallet verification matter for withdrawals and payouts?
Onchain transfers are final. Verifying the destination wallet before funds leave confirms the money is going to the right person, because there's no way to reverse it afterwards.
Is wallet verification the same as KYC?
No. KYC confirms who a customer is. Wallet verification confirms that the customer controls the wallet they're using. The two work together.
Which businesses need wallet verification?
Any business moving stablecoins on behalf of customers: banks, PSPs, brokers and trading platforms, fintechs, marketplaces, exchanges and iGaming platforms.
How does WalletConnect verify wallets?
WalletConnect confirms wallet control with a single click from the user's own wallet. It screens the wallet and the IP address behind the connection against sanctions lists and restricted regions, and returns an audit-ready record to your systems.
What is Clear Signing?
Clear Signing shows a transaction in plain language before it's signed, including what's moving, how much, and where it's going, so users and institutional approvers know exactly what they're approving.