Verified use case
What happened?
DBS announced a Treasury Tokens pilot with Ant International in August 2024, connecting its permissioned ledger and payment engine with Ant's Whale treasury platform. The October 2024 Token Services release described ongoing intragroup transfers, and DBS's 2024 annual report identified Ant as an early user. The evidence supports a corporate banking workflow; it does not establish universal cross-bank availability or independently quantified savings.
Context before technology
Background
DBS announced the Treasury Tokens pilot on August 13, 2024. Its release describes a collaboration with Ant International for multi-currency treasury and liquidity management across group entities, using the bank's permissioned blockchain and an integration with Ant's Whale platform.
The buyer problem is liquidity coordination. A corporate group may have money in the wrong account or entity when another part of the business needs it. Banking windows and fragmented records can make that harder to manage. A new technical transfer path is useful only if it preserves account authority, ownership and the evidence finance teams need.
In October 2024, DBS introduced Token Services as a broader suite and described Treasury Tokens as supporting ongoing Ant intragroup transfers. Its 2024 annual report subsequently identified Ant as an early user. These records provide a progression beyond the pilot announcement without requiring FluidRWA to invent transaction counts or savings.
This case focuses on bank-to-corporate treasury integration. It is distinct from the existing Kinexys repo and Shopify merchant-checkout cases: it concerns movement and visibility of group liquidity, not securities financing or a customer's purchase. The categories overlap technologically, but the operating obligations differ.
Roles and records
How does the operating model work?
1. Define the corporate entity and account map
The disclosed use is intragroup treasury. FluidRWA recommends starting with legal entities, account owners, approved currencies and authority limits. A group dashboard should not obscure the fact that balances may belong to different entities with different obligations.
2. Connect bank and treasury infrastructure
DBS's pilot announcement describes an EVM-compatible permissioned ledger linked to its core payment engine and Ant's Whale platform. Permissioned access and bank control are intentional features. EVM compatibility does not make the service open to anonymous wallets or every public network.
3. Execute a supported liquidity instruction
The bank describes around-the-clock multi-currency intragroup settlement. For buyers, the key test is the exact supported instruction: source account, destination account, amount, currency and required approvals. A general 24/7 service description is not proof that every external rail has the same availability.
4. Reconcile the result and handle exceptions
FluidRWA recommends matching the treasury instruction to the bank's final state and the group's accounting records. Tests should include insufficient funds, a held destination and an ambiguous acknowledgement. These are proposed buyer tests, not publicly confirmed details of Ant's confidential control environment.
Core infrastructure
- DBS permissioned EVM-compatible blockchain
- Core bank payment engine
- Ant International Whale integration
- Corporate account and legal-entity controls
- Intragroup liquidity workflow
- Treasury records and reconciliation
Confirmed milestones
How did the use case develop?
- 01
August 13, 2024
Ant pilot announced
DBS announced Treasury Tokens with Ant International and integration with the Whale treasury platform.
- 02
October 18, 2024
Token Services introduced
DBS's broader suite announcement described ongoing Ant intragroup transfers supported by Treasury Tokens.
- 03
2024 annual report
Client use recorded
The Institutional Banking section names Ant as an early user of multi-currency treasury and liquidity management.
- 04
2025 public bank profile
Continued service description
DBS's public profile described the corporate intragroup use after the original pilot. No new client-level volume figure is asserted.
- 05
October 12, 2026
Research cut-off
The launch records, annual report and subsequent bank description were rechecked. This review date does not imply a newly announced 2026 deployment.
Evidence of adoption
What outcomes are publicly confirmed?
Ant International use disclosed
DBS's annual report identifies an early user. This is stronger evidence than an unnamed hypothetical workflow, but remains bank-reported.
Supported workflow described
DBS describes around-the-clock intragroup treasury operation. This is not an independently tested uptime figure or universal rail availability.
Client-level savings and volumes
The reviewed primary records did not establish audited Ant transaction volumes, capital released or a quantified cost reduction.
Metrics are attributed to their reporting organization and date. They are not forecasts, endorsements or guarantees of equivalent results.
Current position
What are the latest confirmed updates?
- The evidence reviewed supports progression from pilot to ongoing use, rather than only a future intention. The chronology is retained so the original pilot is not mislabeled as a broad commercial rollout.
- DBS Token Services includes other named solutions such as Conditional Payments and Programmable Rewards. Their features and results are not attributed to the Ant treasury use case.
- No verified 2026 Ant-specific volume or savings disclosure was established in this research. Buyers should ask for current deployment evidence rather than treat the review date as a new performance milestone.
What buyers can learn
Why did this use case progress?
- FluidRWA interpretation: connecting the service to an existing treasury platform gives operations teams a defined workflow rather than a separate token dashboard.
- A bank-controlled environment can make account and permission responsibilities clearer, while concentrating dependency on that bank's access, service rules and recovery processes.
- A named corporate use case lets buyers ask specific integration questions. It does not remove the need to validate a different company's currencies, markets and legal entities.
- The progression from pilot to reported ongoing use is meaningful evidence, but mature procurement still needs support terms, exportability, recovery drills and client-specific acceptance criteria.
Limits of the evidence
- The evidence is authored by DBS. FluidRWA has not independently audited Ant's operations, savings or service reliability.
- No automatic equivalence to a CBDC, unrestricted stablecoin or universally transferable deposit claim is asserted.
- The stated multi-currency treasury model must not be generalized to all external counterparties or banking markets.
- Technology does not remove bank credit exposure, treasury governance, currency risk or jurisdiction-specific constraints.
Questions to take into procurement
- Which bank account, legal entity and currency does each ledger balance represent?
- What is the legal effect of a ledger transfer relative to the bank's books?
- Which counterparties, markets and payment rails are actually supported?
- How do failures, holds and reversals appear in treasury records?
- What specific savings and reliability evidence can the bank provide for our configuration?
Relevant FluidRWA directories
Common questions
Is Treasury Tokens an unrestricted stablecoin?
The reviewed DBS material describes a permissioned institutional banking service connected to its payment engine. It should not be presented as an unrestricted public-chain payment token.
Was Ant's involvement only an announcement?
The August 2024 release describes a pilot. The October release states that it supports ongoing intragroup transfers, and DBS's 2024 annual report identifies Ant as an early user. These are bank-reported disclosures, not an independent client audit.
Does 24/7 operation remove every currency cutoff?
No universal claim is justified. DBS describes the supported intragroup workflow. Actual markets, accounts, liquidity, external payment rails and contractual conditions must be checked for a proposed deployment.
Research record
FluidRWA reviewed the following public records. Company names are presented as plain text and are not outbound promotional links.
- DBS: Treasury Tokens pilot with Ant International, August 13, 2024. https://www.dbs.com/newsroom/DBS_launches_blockchain_powered_Treasury_Tokens_pilot_with_Ant_International_for_247_treasury_and_liquidity_management
- DBS: Token Services launch and ongoing intragroup transfer description, October 18, 2024. https://www.dbs.com/newsroom/DBS_rolls_out_blockchain_powered_banking_for_institutions_with_DBS_Token_Services_marks_new_milestone_in_financial_services
- DBS Annual Report 2024: Institutional Banking, early-adopter disclosure. https://www.dbs.com/annualreports/2024/institutional-banking.html
- DBS: public 2025 bank profile discussing Token Services, reviewed October 12, 2026. https://www.dbs.com/about-us/who-we-are/awards-accolades/a-world-first/euromoney-worlds-best-bank-2025
Independent research summary, not legal, investment or regulatory advice. Public statements may be updated after the research cut-off.
Last updated
Questions about your project? contact@fluidrwa.com