TL;DR
- Citi has processed live U.S. dollar transactions with First Abu Dhabi Bank and OCBC through Swift’s blockchain-based ledger.
- The pilot uses tokenized deposits to support round-the-clock payment commitments, while final settlement remains on established banking rails.
- This is not a public-crypto model. It is regulated commercial-bank money operating through shared-ledger technology.
- The financial-crime challenge is not simply screening a new payment rail. It is preserving context as payments move between tokenized and traditional systems.
- The future of compliance is digital-asset financial crime: a wider discipline that connects wallets, tokenized money, identities, payment instructions and conventional banking activity.
Citi’s live transactions on Swift’s blockchain-based ledger show that digital-asset payment infrastructure is moving into the core of cross-border banking.
That does not mean every bank is becoming a crypto company. It means the line between tokenized money, bank deposits and conventional payment rails is becoming less distinct. For financial-crime teams, the question is no longer whether to prepare for this shift. It is whether their controls and investigative processes can follow money across these connected systems.
What did Citi and Swift actually do?
On September 2, Citi announced that it had completed live transactions on Swift’s blockchain-based ledger with First Abu Dhabi Bank (FAB) and OCBC. Citi described itself as the first U.S. bank to conduct live native-ledger transactions. It expected similar transactions with DBS and UOB later in September as part of a controlled pilot running through December 2026.
The significance is in the model. The ledger allows participating banks to make payment commitments using tokenized deposits. A tokenized deposit is a digital representation of a commercial-bank deposit, rather than a privately issued stablecoin or a cryptocurrency such as Bitcoin.
The tokens remain tied to participating banks’ balance sheets. Swift’s ledger coordinates payment commitments and records the related interbank obligations. Final settlement remains separate and occurs through established correspondent-banking channels and other existing settlement systems.
FAB’s explanation of the live transaction
In other words, this is not a replacement of the banking system. It is an attempt to make parts of cross-border banking more continuous, interoperable and available outside traditional operating hours.
Why do tokenized deposits matter now?
Cross-border payments have long been shaped by cut-off times, different time zones, correspondent-bank chains and fragmented local payment systems.
A shared ledger does not remove every one of those challenges. It can, however, allow banks to coordinate and record payment commitments around the clock, even if final settlement happens later through existing rails.
Swift says its initial use case is designed to let banks support 24/7 cross-border payments with tokenized deposits while retaining the compliance, credit, risk and control standards built into current payment processing. Seventeen banks across six continents are preparing to pilot live transactions.
That is why this matters beyond one Citi pilot. Tokenized deposits are moving from isolated proofs of concept toward multi-bank payment workflows. They sit inside regulated institutions and connect to familiar banking processes, but they introduce new data structures, new transfer states and new points of handoff between systems.
The payment rail is changing and financial-crime questions are changing with it.
Why is “crypto compliance” too narrow?
“Crypto compliance” often brings to mind exchange screening, wallet-risk scoring and blockchain tracing. Those capabilities remain important, but they do not fully describe the problem financial institutions are now facing.
A cross-border payment may involve:
- A corporate customer and a traditional bank account
- A tokenized deposit held on a bank’s balance sheet
- A shared-ledger payment commitment
- Existing correspondent-banking settlement
- A conversion into another form of digital value
- A wallet, virtual-asset service provider or other third-party payment endpoint
Each part may create useful information. Yet information does not automatically travel with the payment.
A bank may be able to see its own customer, its own ledger entries and its own risk signals. Another institution may hold essential context about the counterparty, related activity or a possible investigative overlap. The challenge is joining that context quickly enough to inform an appropriate decision.
This is why the more useful category is digital-asset financial crime.
It reflects the convergence already underway between tokenized bank money, blockchain-based workflows, digital wallets and conventional payment rails. The concern is not the technology in isolation. It is the movement of value and the ability to understand the people, entities, instructions and risk signals around it.
What changes for financial-crime operations?
Always-on payment capability creates an operational reality: unusual activity will not wait for the next business day.
A 24/7 model requires teams to think beyond transaction monitoring alone. They need clear processes for holds, escalations, investigations, record preservation and cross-border coordination when a payment or payment commitment raises concern.
The practical questions become more specific:
- Can the institution associate a tokenized payment commitment with the relevant customer and beneficiary information?
- Can it distinguish a ledger record from final settlement and explain the status of funds at each point?
- Are sanctions, fraud and AML controls designed for activity that may occur outside traditional cut-off windows?
- Can teams retain a clear audit trail when value moves between the shared ledger, internal systems and correspondent-banking channels?
- When there is a match or a suspected link, can the institution establish whether the identifier has relevant investigative context elsewhere?
These are not theoretical design questions. They affect the speed and quality of response when fraud, sanctions evasion or money laundering concerns arise.
A payment that appears routine from one institution’s perspective may be part of a wider pattern visible only when additional data is considered. Conversely, an unusual tokenized-payment event is not proof of wrongdoing. It needs corroboration.
Why is there a contextual gap?
New payment technology often produces more data. More data can be useful, but it can also create more isolated signals.
A tokenized deposit record may show that a commitment was made. A transaction-monitoring system may flag a counterparty. A blockchain analytics tool may identify exposure to a relevant wallet. None of those signals, by itself, necessarily explains the full picture.
Financial-crime teams need to know what an identifier means in context.
Has it appeared in confirmed victim reports? Is another authorized organization examining related activity? Does a payment route connect to known infrastructure or a broader case? Is there enough verified information to support escalation, preservation or appropriate coordination?
That is the role of verified intelligence for financial crime.
Deconflict helps authorized financial institutions and law-enforcement agencies validate relevant investigative context around identifiers, without requiring them to surrender control of their own cases, evidence or internal decision-making.
The objective is not to treat every signal as a case. It is to help teams move from ambiguity to a better-informed action.
How should banks prepare?
Banks do not need to wait for universal adoption of tokenized deposits to begin preparing. The most valuable work is often foundational.
First, map the payment lifecycle. Identify where customer identity, beneficiary data, payment instructions, tokenized-deposit records, settlement records and third-party information sit across the process.
Second, define the control points. Decide where screening, monitoring, exception handling and human review should occur when payment commitments can be made around the clock.
Third, test the investigation path. A team should be able to answer: What happened? Who initiated it? What was committed? What settled? Which institutions and systems were involved? What evidence supports each conclusion?
Finally, build coordination into the design. Cross-border payments are already multi-party. Tokenized money makes that coordination challenge more immediate, not less.
The banks that treat financial-crime operations as an implementation requirement, rather than a later compliance check, will be better equipped to scale new payment models safely.
The next chapter of payment crime is already inside banking
Citi’s pilot is a concrete example of how digital-asset capabilities are becoming part of mainstream banking operations. The key lesson is not that conventional payments are being replaced by crypto. It is that multiple forms of regulated and digital value are beginning to operate together.
That changes the scope of financial-crime work.
Teams must be able to follow value across bank accounts, tokenized deposits, shared ledgers, correspondent networks and, where relevant, wallets and digital-asset services. Just as importantly, they must be able to connect those payment events to verified context before deciding what to do next.
The future of financial crime is not limited to one asset class or one rail. It is about understanding how they connect.
FAQs
What are tokenized deposits?
Tokenized deposits are digital representations of commercial-bank deposits. They are issued by banks and remain liabilities on the issuing banks’ balance sheets.
Did Citi settle payments entirely on Swift’s ledger?
No. The pilot used Swift’s ledger to coordinate payment commitments through tokenized deposits. Final interbank settlement remained on established banking channels.
Is Swift’s ledger a public blockchain?
No. Swift describes it as a shared blockchain-based ledger for participating financial institutions. It is designed to support regulated bank-issued tokenized deposits and existing settlement models.
How does this affect AML and fraud teams?
Teams will need to maintain customer, counterparty, payment and settlement context across both tokenized and traditional payment workflows. They also need clear processes for 24/7 monitoring, escalation and investigation.
What does this mean for banks?
It reinforces the need for verified intelligence for financial crime across connected payment environments. Deconflict helps authorized organizations determine whether relevant identifiers have verified investigative context beyond their individual systems.
