Pillar 2 – Technology Alignment: Building a Payments Stack That Supports the Customer Journey

As digital transformation continues to reshape enterprise architecture, payments must be understood not as a peripheral but as a foundational component of the customer experience and the broader technology strategy. Yet in many organizations, payment technologies are still treated as a bolt-on – something to “enable” after the fact rather than intentionally design from the outset as a core element of the tech stack. Accommodating new payment methods becomes an exercise in how to enable needed capabilities with the least amount of work and cost, and the result is almost always misalignment with customer expectations and the long-term goals of the business. The takeaway: payments cannot be fully optimized unless they are fully integrated into how the organization builds, manages, and scales its technology environment.

Siloed systems create ripple effects across the enterprise.

One of the most common challenges retailers face is the tendency for payments decisions to be driven by a single part of the organization – often operations, finance, or IT – without considering how those choices will reverberate across other teams, channels, or customer experiences. These siloed decisions lead to fragmented systems that don’t communicate well with one another, introducing friction at every layer: integration headaches for engineering teams, data blind spots and limited visibility for analytics and fraud teams, and inconsistent experiences for customers moving across in-store, mobile, and digital channels.

Over time, companies patch these gaps by stitching together custom integrations or middleware to force systems to work together. Unfortunately, “Frankenstructure” architecture – built on custom connectors, duplicated payment logic, and multiple uncoordinated vendors – is typically unsustainable. It increases security risks, drives up maintenance costs, and hinders innovation by making even simple enhancements expensive and risky. As retailers expand into new markets, add new digital channels, or attempt to adopt emerging payment methods, the burden compounds. This challenge will become even more pronounced as agentic commerce technologies mature.

True integration requires intentional collaboration, not consensus.

The solution is to integrate customer-first payments strategy with enterprise tech planning. Be intentional about creating the payments environment you want to build within the context of the customer experience. (See Pillar 1).

Because payments connect groups across the organization, and each stakeholder has unique requirements, decisions made in isolation often shift problems unknowingly, downstream. A structured, cross-functional process and disciplined approach are essential to bringing everyone together to set goals and non-negotiables, understand tradeoffs, and align stakeholders around a shared direction across ecommerce, engineering, operations, finance, fraud, loyalty, and in-store teams. The objective is to choose technology that’s best for the business and in support of the customer.

Getting there requires stepping back and asking foundational questions, with all stakeholders contributing:

• What customer experience are we prioritizing, and where are we willing to accept compromise?
• What principles should guide payment decisions when tradeoffs arise?
• What technical, regulatory, and operational constraints are non-negotiable versus nice to have?

Without true collaboration between departments, as well as between in-store and mobile or online ordering, the payments solution will ultimately fall short of meeting the organization’s requirements. However, when all stakeholders are engaged, it’s possible to distill out a payment strategy that’s inclusive of all key goals – technology, cost, revenue, and customer experience.

Capabilities before costs.

It’s not uncommon for retailers to be overly influenced by cost. For example, a company might choose a point-of-sale technology that integrates with an existing acquirer or gateway because it’s less expensive. But this can lock everyone into that solution with negative repercussions down the line in the payment flow.  Remember that you can negotiate price; you cannot negotiate functionality. Retailers who select a lower-cost solution and try to push the provider to build custom features often find themselves with a system that cannot meet their needs – resulting in costly workarounds, unhappy teams, and degraded performance.

It’s generally best to start with functionality and capabilities that meet the agreed-upon requirements and then negotiate from there. Keep in mind that the right choice is unlikely to be just one solution; but it shouldn’t be too many either. Retailers can run into trouble when they end up at either extreme.

For example, a large, multi-brand retailer might run several lines of business, dozens of digital channels, multiple commerce platforms, several POS systems, two hardware providers, multiple payment gateways, and several fraud partners and other third-party solutions. While this decentralized, speed-first approach can accelerate time-to-market, it also creates vast technical misalignment, inconsistent customer experiences, and operational fragility. This approach could lead to short-term wins at the expense of long-term health.

On the other end of the spectrum, some retailers attempt to simplify by consolidating everything under a single provider. Take a sporting goods retailer with an all-in-one payments solution. This company found that while the architecture looked clean on paper, it left them with no flexibility to add enhancements, adapt to new customer needs, or negotiate better commercial terms. The tightly coupled system became a constraint, not an accelerator.

Again, the goal is rarely one provider or twenty – it is the right combination of partners and capabilities for the business’s long-term vision.

Future-proofing the tech stack requires architectural discipline.

To support growth and customer expectations, including emerging AI-driven experiences, teams must be willing to plan beyond today’s immediate needs and adopt payments architecture built for flexibility:

• Orchestration layers to streamline connections
• API-first designs to reduce friction
• Tokenization and identity frameworks for security
• Scalable platforms that evolve with changing customer expectations without requiring full rebuilds or costly overhauls

Decisions made today should reinforce – not constrain – the technology roadmap for the next five years, or companies will struggle to participate as technology shifts. When payments strategy is tightly aligned with enterprise technology strategy from the start, retailers gain the agility to enter new markets, adopt new methods, support emerging channels, and deliver unified experiences across every touchpoint. Instead of reacting to gaps or bolting on temporary fixes, they can innovate confidently and sustainably as they grow.

Stay Tuned for Pillar 3 – Risk Mitigation: Embedding Compliance & Security into Every Payments Decision

All six pillars will be released over the next couple months. Don’t want to wait for the full series?

Receive the full Payments Optimization Reimagined: From Cost to Strategy Whitepaper to your inbox now.

Access Now