ACI Worldwide said on 22 September 2026 that it is adding routing for Swift ledger transactions to ACI Connetic, its cloud-native payments hub, so that banks can process tokenized deposit payments with the same controls, workflows and reconciliation they use for card, wire and instant payments. The Nasdaq-listed payments software company timed the announcement for Sibos, the banking industry’s annual conference, where it planned live demonstrations on 30 September.

The pitch is that banks should not have to build a second payments operation for digital assets, and ACI is betting they will pay for software that spares them the effort. On that point ACI is right.

What the Swift ledger is for

Swift announced its blockchain-based shared ledger at Sibos in 2025, developed with Consensys, as a way for banks to move tokenized deposits across borders on a common record rather than through chains of correspondent accounts. The ledger is meant to run around the clock, which the existing correspondent model does not.

According to ACI’s release, Swift has since confirmed the Swift ledger is ready for initial use, with 17 banks on six continents piloting use cases. That is a real network forming, though still a small one next to the more than 11,000 institutions connected to Swift’s messaging network. Fintechbits reported on one of those early participants in its piece on Citi’s live Swift ledger pilot.

The operational problem ACI is targeting

ACI’s release is unusually candid about where tokenized deposits sit inside banks. Getting one payment through, it says, “still means running it as a project, with a dedicated team, processes built outside normal payment operations, and manual steps.” That setup works at pilot volume and breaks at production volume.

Anyone who has watched a bank run a blockchain pilot will recognise the description. The payment itself might settle in seconds, but the sanctions screening, fraud checks, liquidity management, exception handling and reconciliation all happen in a side process staffed by people seconded from the innovation team. None of it scales, and none of it passes an audit without a lot of manual evidence gathering.

ACI Connetic is supposed to fold Swift ledger transactions into the bank’s normal flow. The hub picks a clearing and settlement path for each payment using rules set by the bank and its customers, weighing speed, cost, availability and customer expectations. In principle a corporate payment could go over the Swift ledger at 2am on a Sunday and over a conventional rail on a Tuesday morning, with the same controls applied to both and one record for operations staff to reconcile.

Why Swift ledger support matters for ACI

ACI sells into the same core payments market as Fiserv, FIS, Finastra, Volante and a long list of cloud-native newcomers. Most banks will not replace a payments hub to get tokenized deposit support. They will favour whichever vendor they already run, provided that vendor offers it. Announcing Swift ledger routing early lets ACI tell its existing banks they do not need a separate digital-asset platform, and gives prospects one more reason to choose Connetic over a rival.

This is the second Connetic announcement Fintechbits has covered in a short span, after the financial messaging update in September. ACI is positioning Connetic as the product that carries its account-to-account strategy, and it is adding capabilities at a steady clip to make that case to banks.

What the announcement leaves out

The release is written in the future tense. ACI Connetic “will support” payments orchestrated through the Swift ledger, and the capability “will allow” banks to process tokenized deposits. There is no availability date, no named bank customer and no indication of whether any of the 17 pilot banks runs Connetic.

That matters because liquidity, more than routing, is the hard part of tokenized deposit payments. A bank sending tokenized deposits across the Swift ledger at weekends needs funded balances on the ledger at weekends, and it needs its treasury systems to see those balances in real time. The release says nothing about treasury integration, and routing software cannot solve a funding problem on its own.

There is also a question about volume. Seventeen banks piloting use cases is not a market that justifies large vendor investment by itself. ACI is building ahead of demand, which is sensible for a vendor of its size, but banks should read this as a roadmap signal rather than a product they can deploy.

Our view

ACI has the right idea. Tokenized deposits will only reach production scale if banks can operate them with the people and controls they already have, and a payments hub is the natural place to do that. Most tokenization announcements talk about the ledger. This one talks about the back office, which is where pilots usually stall.

It is still an announcement of intent. Until a bank is running live Swift ledger payments through Connetic, with volumes it is willing to disclose, the claim that banks can avoid a parallel operation is untested. For more detail on how the product works, ACI points readers to its Connetic product page.

What to watch

The signal to look for is the first bank that says, on the record, that it routes Swift ledger payments through ACI Connetic in production. The second number to track is the Swift ledger participant count. If it stays near the 17 pilot banks through 2027, ACI will have built well ahead of demand. If it climbs into the hundreds, Connetic support becomes something banks ask for in every payments hub tender.