Resources / Blog /

How to Build a Flexible Payment Stack Without Starting Over

Discover how IXOPAY and Kiwi.com approach payment infrastructure modernization, from avoiding provider lock-in and using payment data to improve performance to building a flexible payment stack that can evolve without costly rebuilds.

Every time you enter a new market or introduce a local payment method, your payment infrastructure takes on another dependency. What started as a straightforward integration can quickly become a complex engineering project involving multiple providers, fraud systems, and reporting tools.

Meanwhile, customer buying journeys keep evolving. They move between devices and channels, expecting to pay wherever and however they choose. IXOPAY calls this fluid commerce. Supporting it means adapting your payment infrastructure while keeping existing transactions running reliably.

So how do you make your payment stack adaptable, without turning every business decision into another costly rebuild?

In IXOPAY’s webinar, Fluid Commerce: Designing Payments for Continued Change, Jill Willard, CTO at IXOPAY, and Marcel Mabhena, FinTech Payments Director at Kiwi.com, share their perspectives on building payment infrastructure that can evolve with your business.

Separate payment capabilities before they become dependencies

Jill Willard recommends starting with two fundamental software design principles: abstraction and encapsulation. The idea is to separate individual payment capabilities and hide their underlying complexity, so changes to one component don’t force changes across the entire infrastructure.

Start by making three deliberate decisions:

  • Identify your core payment capabilities: Determine which functions are essential to your business and its payment requirements.
  • Separate requirements from implementation: Define what each capability needs to achieve, without tying those requirements to a particular technical solution or provider.
  • Decide what to own and what to outsource: Establish which capabilities your team needs to control directly and which can be delivered by external providers.

Payment credentials offer a useful example. If your PSP also stores your payment tokens, switching providers could mean migrating millions of credentials before you can move your processing elsewhere. Jill describes this as a lock-in mechanism. An independent vault will keep credential storage separate from transaction processing, giving you more freedom to change providers.

‍

Don’t let payment tokens and orchestration limit your options

Payment credentials can become one of the hardest dependencies to unwind. When your PSP stores your payment tokens, switching providers can mean migrating the credentials associated with potentially millions of customers. A provider may offer tokenization at no apparent cost, but as Jill points out, those tokens can become a lock-in mechanism.

An independent tokenization vault keeps credential storage separate from transaction processing. This means you can change your PSP without making a migration of millions of stored credentials a prerequisite. You can also use those credentials with your preferred orchestration provider or connect them to other payment capabilities independently.

‍

‍

Orchestrator Lock-In

Orchestration can create a similar dependency. Suppose you want to introduce a payment method your orchestrator doesn’t support. Can you build the integration yourself and connect it to your preferred payment provider, or must you wait for the orchestrator to develop it? The same applies to 3DS. If your requirements change, can you run authentication outside the orchestration platform?

Jill recommends asking these questions before committing to a provider. An orchestrator should give you access to the capabilities you need without preventing you from making independent decisions. As she explains, merchants should have the option to take control when a provider cannot accommodate a particular requirement.

Before choosing a provider, establish whether you can take your payment credentials with you, introduce integrations independently, and bypass the orchestration platform when necessary. These decisions determine how much flexibility you’ll retain as your payment requirements evolve.

‍

Use payment data to find opportunities hiding in your infrastructure

Kiwi.com recognized that its payment data could reveal opportunities to improve processing performance and control costs. Marcel Mabena explains that the company stores transaction data centrally, including BIN information, customer location, IP addresses and currencies. It uses this data to build performance metrics and:

  • Compare providers: Track authorization and fraud rates across providers to identify performance patterns and opportunities to improve payment routing.
  • Recover failed transactions: Cascade payments to another acquirer when the initial attempt is declined, or try another fraud provider when a decision is unfavorable.
  • Audit processing fees: Compare provider charges with agreed and expected fees.
  • Recover overcharges: Identify discrepancies in acquirer reports. Marcel confirms this analysis helped Kiwi.com recover substantial overcharged fees over the previous couple of years.

Consistent data across providers gives you visibility into the performance and cost of your entire payment operation.

‍

‍

Build, buy or outsource? Start with the control you need

The build-versus-buy decision starts with a more fundamental question: which payment capabilities do you need to control, and which can you delegate?

Jill recommends outsourcing functions such as compliance management, sensitive payment data storage, and payment data normalization – provided you retain the ability to make independent decisions. You might use a specialist vault to store payment credentials, while keeping the option to introduce another PSP without rebuilding your processing infrastructure.

Marcel suggests starting with your customers. Identify where they are, which payment methods they prefer and what regional requirements you need to support. This will help determine where external providers can meet your needs and where internal development makes more sense.

When evaluating potential partners, consider two questions:

  • Current requirements: Can the provider support the payment methods and regional capabilities you need today?
  • Future flexibility: If your requirements change, can you introduce new integrations independently, or will you have to wait for the provider?

Modernize your payment stack one component at a time

Replacing an entire payment stack carries significant operational risk when your business processes transactions around the clock. Kiwi.com experienced this firsthand: before rebuilding its infrastructure, payment incidents could last two to four hours and cost over $500k.

Jill recommends a more controlled approach, comparing payment infrastructure modernization to unpicking a sweater. Find a seam, remove one section, replace it, and gradually work through the rest. This allows you to isolate individual components and modernize them without disrupting the entire payment operation.

Kiwi.com followed a similar path, progressively rebuilding its internal payment services over two years. 

Marcel also discusses how to measure the commercial impact of payment infrastructure changes, from processing costs and authorization rates to adoption of new payment methods. One example from Kiwi.com illustrates how a new integration can achieve 30–40% adoption within its first week.

Give your payment infrastructure room to evolve

The real test comes when the business wants to move in a direction its payment architecture wasn’t designed to support. You should be able to make that move without turning it into another two-year engineering project.

Watch IXOPAY’s webinar to hear Jill and Marcel discuss how to make that possible.

‍

Mary Ann Felts, Senior Product Marketing Manager

Mary Ann Felts

Senior Product Marketing Manager

Mary Ann Felts is a product marketing leader with experience across fintech, SaaS, and technology. As Senior Product Marketing Manager at IXOPAY, she leads marketing for payment orchestration, translating complex technical concepts into clear positioning, compelling content, and effective go-to-market strategies. She is passionate about using customer insight and storytelling to help businesses understand emerging trends in payments, AI, and agentic commerce.

Let's Connect

Ready to optimize your payments with IXOPAY? Reach out to learn how we can help transform your business's payment processes.

Request a Demo