There is a revealing way to think about a cash machine. Nobody approaches one hoping to be surprised. The money should appear, the balance should be right, and the machine should remember what happened. That small, stubborn expectation helps explain ACI Worldwide, a payment-software business whose history begins long before anyone could tap a phone at a checkout.
- ACI builds the machinery banks, merchants and billers use to move money.
- Its Connetic platform aims to consolidate payment systems and fraud controls.
- A costly testing incident shows why operational boundaries still matter.
An ATM does not care about your pitch
ACI began in Omaha in 1975, writing software for Tandem’s NonStop computers. The attraction was practical: banks needed systems that kept running. Early ATM work led to BASE24, launched in 1982. Point-of-sale and branch applications followed. ACI learned to handle the instructions behind transactions, then extended its reach into clearing, settlement and fraud detection.
The company’s early international expansion had a wonderfully concrete beginning: an Australian bank became a customer in 1981. By 1986, ACI had 131 customers across 14 countries. The export was an answer to a recurring problem. Wherever a bank operated, a payment instruction had to survive the trip through complicated machinery.
That history helps explain its position today. ACI sells into institutions with existing systems, obligations and customers. Its expertise lies in connecting payment networks and keeping transaction operations working. The buyer is often trying to change an engine while the vehicle remains in service.
Three doors into the same problem
For a bank, ACI can provide card processing, account-to-account payments and connections to payment networks. For a merchant, its Payments Orchestration Platform coordinates acceptance across stores, websites and mobile channels. Being acquirer-agnostic means a merchant can work with different acquiring partners rather than organize everything around one provider.
For a biller, Speedpay handles the less celebratory side of spending: paying the utility, lender or insurer. Its services include digital bill presentation, payment collection and tools for managing payment operations. Miami-Dade County appears among its customer examples; Decathlon appears among the merchant platform’s. These are different jobs within the same portfolio.
The distinction matters when comparing competitors. A bank might consider FIS, Fiserv or Volante. A biller might consider Paymentus. ACI’s annual filing also identifies customers’ own technology departments as major competition. Sometimes the alternative is another vendor. Sometimes it is the system that already works well enough.
One instruction. Several jobs.
- 01ReceiveA payment request arrives
- 02CheckApply rules and fraud controls
- 03RouteReach the appropriate network
- 04RecordTrack status and exceptions
There is an advantage in that breadth: payment acceptance, fraud decisions and operational data can be considered together. There is also a purchasing challenge. A customer needs to distinguish the capabilities available across ACI’s portfolio from the ones included in a particular contract. A network on a product page is not automatically a network in your deployment.
The new idea is fewer handoffs
Connetic, introduced in May 2025, is ACI’s attempt to put bank payment capabilities and fraud prevention into a common cloud-native platform. The practical promise is fewer separate systems to connect and manage. It offers customer-managed deployment, managed services and software as a service. Buying a platform does not necessarily mean handing over its operation.
Two September 2026 announcements make that proposition tangible. Solaris went live with SEPA Instant on Connetic, completing the first phase of its modernization. FHLB Cincinnati announced a move to Connetic as a service, with Fedwire in scope. ACI runs the platform; the bank’s teams manage payment operations. Each implementation has a defined job.
“Our job is the platform. Theirs is the payments.”
Scotty Perkins, ACI Worldwide
On the FHLB Cincinnati arrangement, September 2026
That is a useful division to remember. ACI’s Microsoft collaboration, announced in 2023, supports Azure-hosted instant-payment connectivity. Cloud infrastructure supplies another operating option. It does not eliminate the need to decide who handles exceptions, monitors the service or answers when a payment goes astray.
The public strategy shows a shift toward consolidation, rather than evidence of a private conversion by management. ACI is asking customers to rethink systems that grew up separately. Its employer messaging similarly emphasizes collaboration and development. Those are stated ambitions; execution is what a bank ultimately buys.
The expensive part is getting it wrong
ACI paid $750 million in cash for Western Union’s U.S. Speedpay business in 2019, subject to customary adjustments. The purchase expanded its bill-payment reach. Its broader business earns money from software licenses, maintenance, cloud arrangements, services and transaction-related fees. In 2025, ACI reported $1.76 billion in revenue, including $1.21 billion classified as recurring.
Scale also magnifies mistakes. On April 23, 2021, testing on Speedpay used live mortgage-customer data. Test-generated payment files reached actual processing. Regulators described approximately $2.3 billion in unauthorized payment attempts affecting roughly 480,000 consumers. Most withdrawals failed to complete or were reversed, but some people lost access to money or incurred bank fees.
The CFPB imposed a $25 million penalty in June 2023. State regulators and attorneys general announced another $20 million in fines that October. The failure described in their findings began with information handling and inadequate separation between testing and real payment systems. Required safeguards included using synthetic data and segregating development work from consumer payments.
For anyone building financial software, the copyable practice is specific: rehearse failure without access to live money. Separate environments, restricted data and clear authorization are requirements to examine before admiring speed. A faster engine makes those decisions more consequential.
Start with one rail. Draw the boundary.
The practical lesson is an operational one. FHLB Cincinnati’s announced scope names a particular network. Solaris’s deployment names a first phase. For buyers, those examples suggest starting with a defined payment flow, an accountable operator and a test environment that cannot issue real instructions. Judge a platform by the handoffs it removes and the responsibilities it clarifies.
Centralization has a weaker case when migration and integration consume more than the complexity they remove. That is a buying judgment, not a promised outcome. ACI’s long history makes the question unusually clear: can you introduce something new while preserving the ordinary, essential confidence that the money will arrive correctly?