SWIFT vs stablecoins in cross-border payments: notes from my Merge Madrid panel
"It makes for a good panel title when you say stablecoins versus Swift," Carlos Jiménez of Rain said early on in our panel. Then he, and the rest of us on stage, spent the next 25 minutes explaining why the two aren't really competing.
At Merge Madrid, I joined Gonzalo Correia, who leads institutional and tokenization business across EMEA at Utila, and Carlos, Director of BD and Partnerships at Rain, to talk about the new architecture of cross-border settlement. Stablecoins move around $1.7 trillion today, mostly in dollars. SWIFT moves the equivalent of global GDP every few days.
Our short answer: stablecoins won't replace SWIFT. Stablecoins make cross-border payments faster and cheaper, while SWIFT and other trust structures answer who is behind a payment and whether it should go ahead. Stablecoin cross-border payments need both, and the work now is building that trust layer for on-chain value.
Two systems answering different questions
When we were asked whether this is really a battle, I split the problem in two. Stablecoins solve for how money moves across borders, and they do it far more efficiently than the web of correspondent banking relationships we have come to rely on. SWIFT, along with card networks and national payment systems, solves for the rest of the payment: who is behind the transaction, whether it can be authorized, and how that authorization is coordinated across every institution taking part.
Stablecoins can make some of those problems obsolete. They would still benefit from the trust structures that SWIFT and the banks around it have spent decades building. It's also why, when I introduced Notabene on stage, I described us as SWIFT for crypto.
Carlos made the same point from the card side. "You can't pay for a coffee with a Swift transaction," he said, but a stablecoin-backed card works anywhere Visa does, and the merchant never knows the difference. Many of Rain's partners use SWIFT as the on-ramp: fiat in, USDC or USDT, then spend over card networks.
Gonzalo framed it as a challenger pushing an incumbent to upgrade, pointing to SWIFT's own work on a permissioned ledger. In his view, users will eventually see an amount on a screen and never think about which rail carried it.
Tokenized deposits vs stablecoins: banks choose by use case
Utila works with banks building on both stablecoins and tokenized deposits, so Gonzalo was asked which one they want. His answer was that it depends on the flow. Cross-border payments lean toward stablecoins. Payments within a bank, and products built around the customer experience, lean toward tokenized deposits.
The two aren't interchangeable. A tokenized deposit has less interoperability, including with DeFi, which banks are also starting to explore for retail customers. Banks are analyzing both and picking per use case. In my fireside with Deborah zu Hohenlohe at the same event, we went deeper into how banks are capturing stablecoin payment volumes, and our solutions for banks page sets out how we support them.
What users and partners actually want
Carlos was clear that cardholders don't choose Rain's cards because they run on stablecoins. In high-inflation markets across South America, they want a dollar account. In Europe, they want a multi-currency card that spends dollars when they need dollars and euros when they need euros. Which euro stablecoin leads is still open, and less settled than in the US.
For Rain's partners, the draw is stablecoin settlement. A traditional card program can't settle on weekends or holidays. With stablecoins, settlement happens every day, which means better liquidity and less collateral to post.
Context can travel on-chain. Reliability is the work.
A SWIFT payment carries payment context and counterparty information with the value, structured in ISO 20022. I was asked whether that can happen on-chain, and I split my answer in two.
It can happen, and it already does at scale. The Notabene network recently passed $3 trillion in total transaction volume processed, all of it accompanied by transaction context and counterparty information. Whether it happens reliably enough today is a different question.
Part of the reason is that, as an industry, we severely underestimated the importance of transaction context. We solved for moving value efficiently and assumed the job was done, paying far less attention to the trust and context layers that real-economy payments depend on. Where that infrastructure was adopted, the main driver was an AML requirement, the Travel Rule, which requires institutions to exchange information about who is sending and receiving funds.
We are in a much better position than when I joined Notabene five years ago. Around 83% of jurisdictions now have Travel Rule requirements for digital assets, and with MiCA and the Transfer of Funds Regulation (TFR) fully in effect, institutions in Europe have a clear incentive to adopt this infrastructure (our EU hub covers both). The bigger issue, as I see it, is that we have treated this infrastructure as a way to meet a regulatory requirement, when it is the trust and context layer stablecoins need to work in the real economy.
Authorize before value moves
Carlos named trust as the deciding factor. Many people in financial services will choose SWIFT even at a higher cost because they trust the banking system. On the crypto side, the work is making the experience easier and more trustworthy, so that sending to the right chain and the right counterparty stops being a worry.
That connects directly to pre-transaction authorization. A couple of years ago, I was reading that Binance had reported recovering more than $4 billion in user deposits that had never been credited, often because customers sent an asset it didn't support. And that is only what was recovered. When the receiving institution can authorize or reject a transaction before value moves, much of that is prevented. The same layer lets businesses reconcile on-chain value with the payment context they need to book it. Notabene Transact runs that authorization step, using the open Transaction Authorization Protocol (TAP).
So why not just use SWIFT? Because it wasn't built around stablecoin infrastructure, and that gap is what we set out to cover five years ago. I do think SWIFT will try to play a role, and I expect several trust structures to coexist: SWIFT for banking, card networks for theirs, national payment systems, and the Notabene network as the native one for digital asset transactions. For banks that already run on SWIFT messaging, we now support ISO 20022 for stablecoin payments, so the two can meet.
Keep it simple, and build the whole stack
Carlos shared a line from a candidate Rain interviewed that week: "so many people in crypto are just overcomplicating things and creating our own problems." Bridging between chains and supporting one token but not another create friction. The more the industry standardizes, within reason, the faster institutions adopt.
Gonzalo described what institutions are discovering they need around a stablecoin payment. In the "stablecoin sandwich," funds may arrive as a stablecoin or pay out in fiat, which brings in a payout or pay-in partner. Add custody and wallet infrastructure, Travel Rule compliance, AML, orchestration, and accounting that connects to the core banking ledger. "It's a stack that they need to have. It's not only one thing," he said, and the banks Utila talks to increasingly see it that way. Notabene Flow for cross-border payments brings the compliance and authorization parts of that stack into the payment itself.
What we're watching
Gonzalo expects bank and financial market infrastructure adoption to accelerate over the next year or two. Carlos is watching which stablecoins lead in Europe, the UK and other markets, and how payments get embedded in agentic flows. I'm very bad at predictions, but I'm interested to see how far stablecoins grow into B2B cross-border payments.
I'm sharing clips from the panel on LinkedIn over the next two weeks. If your team is working through how to bring payment context and authorization to stablecoin flows, get in touch.
Notabene is the trust layer for global crypto money movement.
Notabene Flow — the first open stablecoin payments platform for businesses—and Notabene Transact—the world's largest Travel Rule-compliant transaction authorization platform for regulated institutions—are built on the Transaction Authorization Protocol (TAP), an open messaging standard that enables verified entities to transact securely.
The Notabene Network connects thousands of trusted counterparties, facilitating over $1.3T in transaction volume over the past 12 months across over 110 jurisdictions.
Subscribe to Notabene Blog
Subscribe to our product updates, news on crypto regulations and more
Request a demo
Notabene offers a demo for you to learn and understand how to use our products
Book demo
