Subscribe to get high-signal insights on how modern fintech is built.

opinion

The Banks' Answer to Stablecoins Is Working

A dollar payment crossed the Pacific on a Saturday. The banks in between were closed.

By Alex Kugell ·

The global financial system takes weekends off. Swift moves instructions in seconds, but the banks themselves (settlement systems, correspondent networks) close. A dollar that needs to cross the Pacific on a Saturday waits until Monday.

That constraint is starting to break.

Saturday, September 5

On a Saturday morning, DBS and Citi's New York office completed a cross-border dollar payment using tokenized deposits on the Swift Digital Ledger. It took minutes, on a day when every correspondent banking system in the traditional chain was closed.

Swift announced the ledger nine months earlier at Sibos with 30 banks in the design group. By July, 17 banks across six continents were piloting live transactions. By September, two of them had moved real dollars across the Pacific on a weekend.

Infrastructure this deep usually moves in years. Swift built the ledger in nine months and had a live cross-border payment two months after that.

Cross-Border USD Payment: Traditional vs. Swift Digital Ledger
Correspondent Chain
Fri 3pmDBS initiates
SatClosed
SunClosed
Mon 9amCiti processes
TueSettled
~2 business days
Swift Digital Ledger
Sat 9amDBS initiates
Swift Ledger validates
Sat 9amCiti receives
Minutes

Why a Saturday matters

Asia's outbound cross-border payments are projected to hit $24 trillion by 2033, nearly double the $13.5 trillion in 2025. Companies in e-commerce, digital services, and supply chain management operate around the clock across time zones.

When their treasury team can't move dollars on a weekend, cash sits idle and FX risk compounds with every hour.

A corporate treasurer managing liquidity across Singapore, London, and New York doesn't want faster weekday payments. They want payments that ignore the calendar.

The boogeyman

Banks built this because stablecoins made the status quo embarrassing.

USDC and USDT move dollars 24/7, globally, in minutes. They skip the correspondent chain entirely — born outside the banking system and usable by anyone with a wallet.

Banks watched stablecoins route around their entire infrastructure and decided to respond.

Citi, Goldman, and a group of major banks are already building their own stablecoin consortium. The Swift ledger is a different bet. Instead of competing with stablecoins directly, it lets banks upgrade the existing rails.

The regulatory and compliance infrastructure stays. The plumbing underneath gets faster.

The objections miss the frame

The objections to tokenized deposits are reasonable. Why not just upgrade the database? Why does the interbank layer need a blockchain?

"Upgrade the database" ignores the coordination problem. Cross-border payments are slow because multiple independent banks need to agree on a state change, and they keep different hours.

DBS closing for the weekend in Singapore doesn't mean Citi's systems in New York are ready to process. A shared ledger lets both sides see and validate the same transaction in real time. A database upgrade at one bank doesn't solve a problem that lives between banks.

"Why blockchain?" asks about the technology instead of the constraint. How do you coordinate real-time settlement across dozens of independent institutions without requiring them to trust a single operator with all the data?

A shared ledger with smart contracts is one answer. Not the only answer. But the one that lets Swift stay neutral infrastructure while adding a capability its members need.

Then why wouldn't a corporate treasurer just use stablecoins? Because a treasurer moving $200 million on a Saturday still needs their bank relationship, their credit lines, their compliance framework, and their FX desk. Tokenized deposits keep all of that intact. The deposit keeps its insurance and regulatory protection. It just becomes transferable at 2am on a Sunday.

The signal

Seventeen banks across six continents signed on within nine months. Two moved real dollars on a weekend within weeks of go-live.

The traditional settlement stack is already moving toward blockchain validation. DTCC, BlackRock, Visa, and Mastercard are validating blocks on Circle's Arc network. The Swift ledger sits on the other side of the same shift: existing financial infrastructure absorbing blockchain's useful properties while keeping the regulatory framework that makes institutional money move.

Stablecoins showed that always-on dollar movement is possible. Tokenized deposits are the bet that banks can do it too, without customers having to leave the banking system to get there.

Sources

Alex Kugell
Alex KugellAI/ML Engineer, Fintech Infrastructure

Writes Ledger Drift. Engineer building AI systems and financial infrastructure. Open source contributor to x402, ACK, and MPP – agentic payment protocols.

Frequently Asked Questions

Can banks settle cross-border payments on weekends now?
Yes. DBS and Citi moved real dollars across the Pacific on a Saturday in September 2026 using tokenized deposits, while every traditional correspondent banking system was closed. Seventeen banks across six continents were piloting live transactions by mid-2026, less than a year after Swift announced the platform.
Why did banks build tokenized deposits instead of just using stablecoins?
A corporate treasurer moving $200 million still needs bank credit lines, compliance frameworks, FX desks, and deposit insurance. Stablecoins route around the banking system entirely. Tokenized deposits upgrade the existing rails so that the deposit keeps its regulatory protections and institutional relationships but becomes transferable at 2am on a Sunday.
How fast did the Swift Digital Ledger go from concept to live transactions?
Swift announced the ledger at Sibos in late 2025 with 30 banks in the design group. By July 2026, 17 banks were piloting. By September, two had moved real dollars on a weekend. Infrastructure at this depth normally takes years, and Swift compressed it into roughly eleven months.
Why can't banks solve weekend settlement by upgrading their databases?
Cross-border payments are slow because multiple independent banks need to agree on a state change while keeping different hours. A database upgrade at one bank does not solve a coordination problem that lives between banks. A shared ledger lets both sides see and validate the same transaction simultaneously, regardless of whether either institution's traditional settlement systems are open.

Built by Trio, a fintech-native engineering partner helping teams build the next generation of financial technology and infrastructure.

Subscribe to Ledger Drift for high-signal insights into how modern fintech is built, from systems to code to teams.

Keep reading

fintechHow Payments Actually WorkA card tap takes two seconds to approve and three days to settle, and the gap is where payments actually happen.
anatomyHow Affirm Underwrites a Loan Before the Page LoadsA sub-second credit decision running on fourteen years of repayment data the bureaus never collected.
ai & mlRAG for Compliance Docs: What Actually WorksMost RAG pipelines are tuned for clean prose, but compliance documents have cross-references, nested definitions, and tables that break every default.
View more ›