How ACI Worldwide builds resilience across a global payments infrastructure by leading with controls, proving value early, and earning operational trust before scaling.
Operational resilience is no longer an internal operations concern. It is a regulatory expectation, a board-level accountability, and a competitive differentiator in global payments. Frameworks like DORA and formal guidance from the Bank of England and European Banking Authority have made this explicit. The bar for how financial institutions and their critical service providers prepare for, withstand, and recover from disruption is higher than it has ever been. And it is not coming down.
Those of us who run payment processing infrastructure already know this. We live it. But there is a real gap between how resilience gets discussed in boardrooms and how it gets built inside production environments. This piece focuses on how that resilience actually gets built. At ACI Worldwide, our platforms support payment processing for financial institutions, billers, and merchants around the world. My team leads systems engineering practices focused on operational resilience across the environment. Over the past two years, we have evolved how we monitor, respond to, and recover from operational events across a complex, multi-product ecosystem.
Governance before automation
The instinct is always to automate first. Faster detection. Automated remediation. Fewer tickets. Everyone wants the efficiency story. We wanted it too.
But we led with controls. Deliberately.
Before putting any automation into production, we invested in visibility: dashboards, validation frameworks, and event correlation. We gave operational teams a clearer picture of system behavior without changing how systems were managed. This lets us strengthen governance and audit posture first, then layer in automation within well-defined guardrails.
When your platforms support the movement of payments globally, any change to how you detect and respond to events must strengthen your control posture — full stop. If it introduces new risk, it does not ship.
Complexity is not a failure. It is the reality of operating at scale.
ACI supports a broad portfolio of products serving banking, billing, and merchant segments worldwide. That portfolio grew organically over the decades through acquisition in response to the market. In response to the market. The diversity reflects how broad the payments ecosystem actually is.
That scale creates a specific challenge. Monitoring that works inside one product environment breaks down when events cross platforms. And at our scale, they always do.
So, we invested in connected visibility: correlating events across systems so anomalies surface in context, not isolation. That reduced the time between detection and informed response. In payments, that gap is where the difference between a managed event and a customer impact gets decided.
Start where risk and volume intersect
We did not try to transform everything at once. We first focused on batch processing, file validation, and event management. These shared services underpin money movement, settlement accuracy, and downstream reliability. When something breaks here, the impact is immediate.
Targeting these areas did two things: It stabilized processes the rest of the business depends on, and it proved this approach works.
One example: Our teams were manually tracking validation of recurring processes roughly every 15 minutes, every hour. Automating this tracking recovered significant daily capacity. Not theoretical capacity — real hours back in the hands of engineers who can now spend their time on work that actually requires their expertise.
Earning trust inside the organization
Any company that has run critical infrastructure for a long time has teams with deep institutional knowledge and strong opinions about how things should work. That expertise is an asset. It also means you cannot mandate a new way of operating and expect everyone to embrace it on day one.
We learned this firsthand. The most effective catalyst for adoption was not executive sponsorship or change management programming. It was proof. When one team saw that automating the triage of low-value alerts removed thousands of manual reviews per year and freed them to focus on problems that actually needed their judgment, the resistance faded. The questions changed. Other teams started coming to us. Where can we get this? What else can it do?
Operational teams that run payments infrastructure are right to be skeptical. The way to move them is not to argue. It is to prove value in a controlled environment and let the results speak.
Governance is not a gate. It is the foundation.
Every decision in this process has been filtered through one question: Does this strengthen or weaken our control posture?
We standardized how events are documented from detection through closure. We established baselines for expected system behavior, so deviations surface automatically instead of waiting for a threshold breach. We built procedures that support efficiency and audit compliance at the same time.
Customers never see this work — they should not have to. But this is the work that makes everything else possible. Strong governance gives you the confidence to automate, the ability to scale, and the credibility to stand in front of regulators, auditors, and the institutions that depend on you.
Principles for peers running payments infrastructure
For organizations working through a similar evolution, these are the principles that have guided us at ACI:
- Lead with governance. Controls, auditability, and standardized procedures come before automation. Always.
- Start where risk and volume intersect. Target the shared services with the highest operational risk and the broadest impact. Prove value there first.
- Earn trust through results. Experienced teams adopt new approaches when they see measurable impact in their own workflows. Proof beats process every time.
- Scale deliberately. Expand after results are validated and governance is confirmed. Discipline is not hesitation.
- Stay connected to the customer impact. Behind every batch file, every settlement validation, and every operational alert is a payment someone is waiting on. Operational resilience is the promise we make to the people and institutions who trust us to move their money reliably.
Operational resilience is not a finish line. It is how we run the business. At ACI, that discipline shapes how we govern change, scale automation, and deliver reliability across the payments ecosystem. We are not finished. No one at global scale ever is. The foundation is strong, and we build on it every quarter.
