Kick-off or crunch point? Why the World Cup is a stress test for banking infrastructure

By Mahesh Paolini-Subramanya, CTO at BKN301

Mahesh Paolini-Subramanya, CTO at BKN301, explained why, as millions of fans move across borders, payment channels, and currencies, banks and FinTechs will need infrastructure that can keep pace with real-time, high-volume demand.

When people talk about preparing for the World Cup, the conversation usually focuses on the physical infrastructure: stadiums, transport, hotels, security, and ticketing. In short, the ‘visible’ aspects of a global sporting event.

But there is another layer of infrastructure that will be tested just as heavily, even if most fans will never see it: banking infrastructure.

Every card payment, mobile wallet transaction, ATM withdrawal, cross-border transfer, foreign exchange request, hotel booking, and merchant settlement depends on financial systems working reliably in the background. For the customer, the moment is a simple tap of a card, approval of a payment, or checking their balance. For the bank, that same action has to move through the core banking stack securely, accurately, and in real time.

The 2026 FIFA World Cup will be the largest edition of the tournament to date, with 48 teams and 104 matches across Canada, Mexico, and the United States. Financial activity will be spread across multiple markets, currencies, time zones, transport corridors, and digital channels, creating a very real test of how well banks can respond when demand becomes less predictable.

Where financial systems face matchday pressure

During a major global event, customer behaviour changes quickly. People spend in places they have never visited before, using merchants with which they have no history. They make purchases at odd times of day because of time zones and travel. They may switch between cards, wallets, and banking apps depending on what works best locally.

A modern banking system needs to interpret all of that quickly and accurately. Many traditional systems were built for a more predictable era, designed around stability and known transaction patterns. That does not make them ineffective, but it does mean that they’re not built for the kind of real-time, borderless demand customers now create.

Weaknesses in legacy banking layers may sit below the surface, but during a global event, they become much harder to hide. If a banking app slows down while a customer is travelling, trust is damaged quickly. If a legitimate transaction is blocked because fraud systems lack context, the customer blames the bank. In each case, the problem may begin in the infrastructure, but the customer experiences it as a failure of service.

Cloud alone will not get banks over the line

A common response to capacity challenges is to move more technology to the cloud. Cloud infrastructure has an important role to play, especially when demand rises quickly, but moving a legacy system to the cloud does not automatically make it ‘modern’, per se.

If the architecture underneath is still rigid, the bank will remain constrained. A monolithic system in the cloud can still be difficult to scale in specific areas. If fraud detection, customer notifications, and account services are all heavily dependent on the same core, then one area of pressure can still create problems elsewhere. The bank may gain capacity, but not necessarily flexibility.

For major events, flexibility matters as much as raw capacity, and it should be possible to adjust banking functions without putting the entire banking environment under strain. That is much harder when the architecture is tightly connected and difficult to change.

Building for stability, not just surges

For many banks, a practical route is modular, API-first infrastructure, allowing banks to separate key functions and scale them according to demand. Fraud detection can be enhanced without reworking the full core; FX capabilities can be expanded when international activity increases; and customer authentication can become more adaptive.

The answer is not always a full replacement of existing systems, which can be expensive, disruptive, and difficult to justify. A more realistic approach is to modernise in stages, using standardised connections between existing infrastructure, trusted third-party providers, and newer digital services.

This gives banks more room to modernise gradually by introducing new capabilities, testing services and scaling what works over time.

Major events expose how customer behaviour can change, and how difficult it is for banks to rely on systems built around predictable patterns. What looks like peak volatility during the World Cup may simply be an early sign of the demand banks will need to manage every day in the years ahead.

A glimpse of banking’s next demand curve

The World Cup is a useful case study because it concentrates banking pressures into a short, intense period; more people are moving, more money is moving, and more services are being used across borders at the same time.

If everything works as planned, most customers will not notice. If services fail, however, they’ll notice immediately.

For banks, the lesson is to build for a world where demand is increasingly mobile, digital, and unpredictable. That means moving away from reactive fixes and towards architecture that can adapt as customer behaviour changes.

Fans will remember the World Cup for what happens in the stadiums. For banks, the more important test will happen away from the pitch: whether people can move money and access services without having to think about the infrastructure beneath. In banking, that is often the best measure of success – the systems remain invisible because they are working as it should.