A single point of control: What most companies get wrong about unifying payments

Editor’s note: This guest post is by Mike Farrell, Senior Vice President of Global Enterprise Accounts at FreedomPay, a Nuvei partner. The ideas in this article are drawn from Episode 2 of the Everywhere Commerce podcast, “One customer, every channel.” Subscribe and listen to the full episode here.

When my five-year-old asks what I do, I tell her to think about going to a restaurant, hotel or theme park. At some point, you take out a card, tap, and carry on with your day.

To most people, it feels like nothing happened: you tap, you leave. But in those few seconds, dozens of systems may have to agree that the customer has the funds, that the transaction is legitimate, that the right payment method has been accepted and that the purchase can proceed. Behind a single tap may sit fraud checks, loyalty data, enterprise resource planning systems, acquirers, processors and more.

That is the gap between how payments feel and how they work. Customers see a simple action. Businesses are responsible for a complex web of systems that must work together in a precise moment, without creating friction or demanding attention.

It is often the most technically complex moment they manage. And it is the moment on which customers judge them most harshly when something goes wrong.

Unified does not mean single provider

Once businesses look beyond the terminal, the scale of the challenge becomes clearer. A single transaction may need to reach a fraud engine, check a loyalty platform, communicate with an ERP, pass through an acquirer and processor, and return an approval, all within seconds, with the customer seeing none of it.

Unified commerce does not mean forcing every one of those functions onto one platform or buying every capability from one provider. It means making the systems that matter behave as one at the precise moment a customer needs them to.

That distinction matters because "one provider for everything" is often confused with simplicity. In reality, it can create a different kind of complexity: dependency.

The appeal is understandable. One contract, one relationship and one company promising to solve the whole problem can make procurement easier and reduce the number of vendors an organization manages. But it can also create a single point of failure.

If that provider has an outage, your business has an outage. If it does not support a payment method that matters in a particular market or customer segment, you are constrained. If its commercial model changes midway through a contract, your negotiating position is limited. If its roadmap no longer matches your priorities, your payments strategy has to wait for someone else's.

Providers may point to 99.9% uptime as reassurance. But 99.9% availability still amounts to roughly eight hours and 46 minutes of downtime in a year. More importantly, a business does not get to choose when that downtime happens. It is unlikely to arrive at 3 a.m. on a quiet Tuesday. It is more likely to strike during a lunch rush, a holiday weekend or a packed game-day watch party.

Customers do not know, or care, what your uptime SLA says. But they do remember whether their payment went through.

Payments are a trust event

In many enterprises, payments still sit in the back office as a cost center, often close to treasury. The conversation therefore tends to focus on reducing processing costs.

And those costs are real, particularly at enterprise scale. But customers do not experience payments as a line item. They experience them as part of one continuous journey with your brand.

A business can invest millions in marketing, loyalty, personalization, experience design and conversion optimization. Yet a single failed payment can undermine all of it in seconds. The customer does not separate a declined transaction from the rest of their experience. They simply remember that the brand let them down when it mattered.  

At the moment of payment, a business is asking a customer to hand over financial information and trust that the transaction will be secure, accurate and effortless. The value at stake is much bigger than a processing fee.

That is why the right payments strategy cannot be based only on consolidation or cost reduction. It has to protect continuity, customer choice and the trust built through every other part of the brand experience.

The goal: a single point of orchestration

A single point of orchestration gives a business one place to manage, monitor and route payments across every channel, while retaining the freedom to select the best provider for each capability. It makes it possible to choose a fraud engine based on performance in a particular risk environment, a loyalty platform that supports the right customer experience and acquiring partners suited to local market reach, approval rates or commercial terms.

It also allows businesses to add payment methods where customers want to use them and to build redundancy into the payments environment, so transactions can be routed around disruption. This is purposeful choice governed through a single control layer, rather than a single solution in charge of all payment components.

At any high-volume moment, a provider outage can quickly become a customer experience problem. With a single point of orchestration, the business can reroute traffic, preserve continuity and keep the disruption invisible to the customer.

The tap will continue to feel seamless to customers, and that is exactly what good payments infrastructure should achieve.

But if I had to explain it to my daughter, I would put it this way: the best payment is the one you barely notice. Behind it is a business in control of everything that makes it work.

‍

Follow Everywhere Commerce everywhere you get your podcasts