If you're reading this and still haven't signed up, click the subscribe button below!

Pssst. We also have a podcast… find that here on your favourite podcast player or here on YouTube 🙏

Welcome to the Tokenized newsletter, brought to you by the creators of the Tokenized Podcast. Written by Simon Taylor of Fintech Brainfood and Shwetabh Sameer of Molten Ventures.

We are the newsletter for institutions that need help preparing for a Tokenized future.

We run through the headlines every week, what it means for you and a market readout. Always with an institutional, business-focused perspective. 

Join us every week as we meet your Tokenization needs.

💬Simon's Market Readout: Swift's new shared ledger goes live with 17 banks, turning tokenized deposits into money that moves between institutions, not just within them. 

📰 Stories You Can't Miss: Standard Chartered, BNY and UBS each pull stablecoins closer to the bank relationship, from mint and redeem to cross-border payments; Ripple picks up a dual MiCA licence in Luxembourg but still needs a euro coin to make it count; and FinCEN draws the stablecoin KYC line at the issuer's door, leaving the peg's defense resting on who gets to redeem.

This newsletter is sponsored by M0!

Most stablecoin platforms give you one stack, one issuer, no choices.

M0 is modular. Choose your regulated issuer. Design how your stablecoin behaves. Change anything as your business evolves.

Your stablecoin, your stack, built around your business

Learn more at m0.org.

Swift has announced the launch of its blockchain-based shared ledger, the Swift Ledger. Belgium-based Swift works with over 11,500 banks around the world and runs something like five trillion in payments per day. It is truly massive. This launch with 17 banks includes UBS, BNP Paribas, BNY, Standard Chartered, Citi, HSBC, Lloyds and many others. The goal is to connect banks' existing in-house tokenized deposit systems and let them interoperate with other institutions, a practical application for swapping tokenized deposits between those banks, with Swift facilitating that through its ledger.

Really, though, you should think of this less as a ledger and more as an orchestration layer. The name is confusing for what it actually does. It's doing the orchestration between the actual ledger systems, the underlying tokenized deposit systems inside each bank. It's more like a Swift orchestrator, but that doesn't sound as exciting.

You might have HSBC's tokenized deposit service, JPMorgan's and Citi's, and I'm a corporate customer, and I want to move between accounts on all of those. Today I'm stuck inside those tokenized deposit systems. I can move money between any HSBC account 24/7, but I have to wait for Monday at 9:00 AM before I can move that transaction between the banks themselves. By connecting these tokenized deposit systems, I can move between any of the banks in this Swift Ledger.

But shout out here, this went from concept nine months ago to live, and it's working. That's quite an initiative to get this much done this quickly. It's activated, it's ready to go, and it means instant 24/7 money movement is entirely possible. This is the first use case, and it could do a lot, lot more. As a corporate, you reduce your compliance and funding risk over a weekend, and your banks can offer you something quite new.

Don't bet against the banks here. Don't bet against Swift. This is useful, this is meaningful, and there are banks leaning into this. Now let's see how this interoperates with everything Zelle and TCH are doing. There are probably going to be more tokenized deposit services and closed loops emerging, and how they start to interoperate with each other is where things start to get really interesting.

Until now, a corporate treasurer who wants direct access to USDC typically has to open a Circle relationship, stand up wallet operations, and bolt a crypto workflow onto a treasury stack built for fiat. In the space of a few days, three G-SIBs pulled stablecoins closer to the bank platform, each from a different starting point and to a different depth. Standard Chartered went furthest, letting eligible institutional clients reach USDC mint and redeem through their existing banking relationship, with one onboarding, one service line, and no direct Circle account. BNY and UBS moved in the same direction. The coin doesn't change. The front door does.

Key Points:

The Tokenized Take:

The interesting shift here is who owns the client relationship. The lazy read is that issuance lost and distribution won. That misreads it. Banks are working both sides at once. SoFi shipped SoFiUSD, Early Warning is building ZelleUSD, and Standard Chartered-backed Anchorpoint holds a Hong Kong license to issue HKDAP, even as Standard Chartered distributes USDC wherever the demand is dollar. Issuance and distribution are two different plays, and one bank can run both.

Circle keeps issuing USDC and earning on the reserves behind it. The banks keep the onboarding, the compliance workflow, the custody account, and the corporate relationship. Whoever holds that relationship prices its own service layer regardless of how the reserve yield is split, and decides what gets bundled next.

The product labels make the three moves sound more different than they are. Standard Chartered and BNY are both gateways into the same USDC mint/redeem lifecycle, but with different control points - SC at the banking relationship and BNY at custody and asset servicing. UBS is on a separate track, proving stablecoin rails can sit inside a corporate cross-border payment flow without the treasurer touching custody, issuance, or mint and redeem at all.

Geography is where this gets interesting for Standard Chartered. Its franchise runs through Asia, the Middle East, and Africa, corridors where correspondent banking is slow and dollar liquidity is hard to source. Mint and redeem is one piece of a money-movement stack, and the bank already has the FX leg, local-market reach, and a controlled path into regulated digital-asset custody through Zodia Custody. UBS holds the same advantage on the payments side. If either wires those pieces together, mint/redeem becomes transaction-banking revenue in the corridors where the edge is real, where banking cut-offs bite and correspondent chains still add days.

The open question is the economics, and there isn't much public detail yet. If Circle shares reserve income with banks that originate balances, USDC distribution becomes a partnership land grab, and this template spreads to any G-SIB with a transaction-banking book. If the reserve yield stays with Circle, banks chase value in the adjacent flows, FX spread, custody, and treasury fees, and adoption concentrates among institutions with a payments reason to bother. Watch which bank connects mint and redeem to real off-ramp coverage first. That is the move that turns a press release into a franchise.

Ripple can now run both legs of a regulated payment flow inside the EEA, the crypto-asset side and the fiat side, from one licensed base. Luxembourg's CSSF granted the full MiCA CASP on 6 July, and it pairs with the Luxembourg EMI licence Ripple already holds to cover collection, exchange and payout across the 30 EEA states. It arrived in a week when Binance suspended new EU services after its Greek licence route failed, and Revolut set an August cutoff for USDT on its own platform.  The field is sorting around Ripple - Binance stepping back from new EU business and Revolut dropping a stablecoin that has not cleared MiCA. 

Key Points:

The Tokenized Take:

MiCA opens the door for Ripple’s payment business, but it narrows the path for its dollar stablecoin. 

We covered Ripple's ~$4 billion acquisition run last November, when it bought Hidden Road for prime brokerage, Rail for stablecoin payments, Palisade for wallet-as-a-service (with a French custody licence), and GTreasury for corporate treasury software. That was the build phase. Luxembourg turns on the regulated parts of it. The CASP covers the crypto-asset services and the EMI covers the fiat and payment leg, which together let Ripple offer cross-border payments across the EEA from one licensed base. What the two licences don't do is carry the rest of the stack into Europe by default. Hidden Road's prime brokerage answers to MiFID II and EMIR. GTreasury is software, not a licensed activity. Palisade came with its own French custody licence, so how it sits under Ripple's Luxembourg entity depends on structure and scope.

The harder limit is denomination. RLUSD is a dollar coin, and MiCA is built to keep dollar coins from becoming a primary euro payment rail. Once a non-euro stablecoin is used heavily for payments inside a euro area, past a daily line of 1 million transactions and €200 million, its issuer has to pull back issuance. MiCA also keeps issuers from paying interest on balances. So the two things that make a dollar coin useful for treasury work, wide payment reach and yield on idle cash, are the two MiCA holds back.

That reshapes the US pitch we described last year, where corporates hold balances in RLUSD, pay from them, and earn on idle cash through Hidden Road, inside GTreasury. The yield there runs through prime structures that sit under MiFID II rather than through the token, and the pay-from-dollar-balances part meets the cap. What travels better is Ripple's original franchise, cross-border payments, where the coin is a bridge for a moment (fiat in, digital asset, fiat out) rather than a balance anyone parks. That transient use looks different from the domestic circulation the cap measures, though how regulators score it is not settled.

For Ripple, the euro problem has three possible answers. Circle brings live liquidity in USDC and EURC, and the euro token is the one that clears the payment cap here. Qivalis is a euro coin by design across 37 banks. Ripple brings the enterprise rails and the dual licence, but it still doesn’t have a euro stablecoin. So its euro route remains open - issue one itself, use EURC, or support someone else’s coin. Schuman’s EURØP is already live on XRP Ledger, showing the infrastructure route is real. Qivalis is the bigger bank-led euro coin to watch, and Ripple is not the named infrastructure partner today.  

So the open question for Ripple in Europe is which euro path it takes -  whether that's its own token, a bank's token on its rails, or EURC for the euro legs. Until that lands, Luxembourg gives Ripple a cross-border payments base in Europe rather than the vertical stack it built for the US.

The good news for anyone building on stablecoins is that the KYC line landed where the industry hoped. FinCEN and the four prudential regulators could have made every transfer a relationship with the issuer, and for now they declined. Identity attaches at the issuer's front door, the people it mints for, converts for, custodies for, and redeems dollars to directly. The token itself keeps moving between wallets, exchanges, and DeFi without creating a new customer file at the issuer. The catch is at the exit, and it's worth the two minutes.

Key Points:

The Tokenized Take:

The whole pitch for a stablecoin is that it settles at par, anywhere, on demand. This rule leaves the "anywhere" alone and puts a gate on the "on demand." A holder can move the token freely for its entire life, then hits an account-opening step the moment they want dollars back from the issuer. Identity must be collected before that account opens, even though verification can finish afterward.

That matters because of who defends the peg. A stablecoin holds its dollar because an arbitrageur can buy it below par and redeem at par, and that trade only works if redemption is open to the marginal buyer. Route redemption through the issuer's onboarded book and the arbitrage runs through a small room. FinCEN's own impact analysis puts the median issuer at around 100 primary-market customers a year, and doesn't expect the total across every issuer to top 300,000. In calm markets, pre-onboarded market makers absorb the flow and the friction is invisible. In a depeg, the marginal redeemer may be a stranger at the door.

None of this breaks the peg tomorrow, because the commercial gate already exists. Circle limits direct USDC redemption to eligible Circle Mint accounts today, and ordinary holders cash out on an exchange, not at the issuer. What the rule changes is the nature of the gate. A business choice can flex in a crisis, and an issuer that wanted to fast-track onboarding mid-depeg could. A federal baseline can't, short of the relief the agencies already hold. They can refine the account definition, or use their exemption authority, which lets a functional regulator with Treasury's sign-off exempt an issuer or an account type outright.

So the comment period turns on one question. Grant redemption-only relief and the marginal redeemer in a stress event faces lighter friction at the exit. Withhold it and the loop defending par is confined to firms already on the issuer's books, leaving everyone else's exit riding on secondary-market liquidity, which is thinnest exactly when the peg is under pressure.

Thanks so much for reading the Tokenized Newsletter!

Please share this edition or share it with your colleagues if you enjoyed it!

Disclaimers