Payment orchestration and payment vaults are both part of payment processor strategy, but they solve different problems. Orchestration decides which processor handles a transaction and reroutes it when one processor underperforms or goes down. A vault stores a customer’s card so a business can charge it again without asking for details a second time. A business that wants better authorisation rates across processors may use payment orchestration, while a subscription business benefits from a payment vault to securely store and reuse customer’s payment details. Many businesses eventually need both.

Below, we’ll explain what payment orchestration and vaults do, the problems each solves, and how to figure out which one your business needs.

Key takeaways

• Payment orchestration routes transactions across multiple processors to improve authorisation rates, cut costs, and add failover when one processor experiences downtime.

• A payment vault stores card credentials securely so a business can charge a customer again without collecting their card details each time.

• Certain tools combine secure card storage with the ability to route that stored card to any third-party processor.

What is payment orchestration and what is a payment vault?

Payment orchestration is a layer that sits between checkout and the processors that move money. It decides which processor handles each transaction, based on rules a business sets or on routing logic that adapts using live performance data.

A payment vault is a system that stores a customer’s payment credentials—usually a card number, expiration date, and network token (a secure substitute for the card number that updates automatically if the card is reissued). This allows a business to charge that card again without asking the customer to type it in twice.

Whereas orchestration decides which processor handles a transaction, a vault stores a customer’s card number and enables the business to reuse it across its own systems.

What problems does payment orchestration solve?

Orchestration exists because relying on a single processor can create vulnerabilities a business will discover only when something breaks. If that processor experiences downtime, or its authorisation rates dip for a particular card network, each transaction routed through it is delayed with no fallback in place.

Three problems tend to push businesses towards orchestration:

• Authorisation rate gaps: Processors don’t perform identically across card networks, regions, or transaction types. A processor with strong Visa authorisation rates in the US might do meaningfully worse with Mastercard transactions in Brazil.

• Single point of failure: A processor outage stops every transaction that depends on it. A business that runs orchestration can reroute payments in real time to a second processor instead of pausing them until the first one recovers.

• Cost differences across processors: Interchange and processor fees vary by card network, transaction type, and region. Routing based on those differences saves more than accepting whatever a single contract dictates for every transaction, regardless of cost.

What does a payment vault add that orchestration can’t?

While orchestration can move a transaction to the processor that makes sense in real time, it doesn’t save the card used. If a business needs to charge the card next week, next month, or on a recurring schedule, that’s where a vault comes in.

If the business stores a card in a vault, that card can go to any processor the orchestration routes to rather than only the one that originally collected it. Without a vault, a card saved through one processor is often locked to that processor’s own tokenisation system. Moving it to a new processor means asking the customer to re-enter their details.

A vault separates the card from any single processor relationship. That makes it possible to add or switch processors later without disrupting subscriptions or saved payment methods.

When should a business prioritise a vault over an orchestration layer?

Not every business needs both a vault and an orchestration layer. Orchestration matters more when a business already has reliable card storage but is losing revenue to processor-specific issues. That could include outages, weak authorisation rates on certain card networks, or costs concentrated with one processor.

Here’s when a business should prioritise a vault:

• Reducing compliance scope is the immediate goal: Storing card data in-house, even briefly, pushes a business into a higher tier for Payment Card Industry (PCI) compliance. A vault removes that exposure by keeping the data with a compliant third party instead.

• Subscriptions or card-on-file payments are central: Any recurring charge depends on a stored card. Building that storage well, with network tokens that update automatically, can minimise failed renewals from reissued or expired cards.

• Authorisation rates are falling due to stale card data: Network tokenisation alone, separate from any routing decision, tends to lift authorisation rates. Updated card data reaches the processor before an outdated card number causes a decline.

Does your business need payment orchestration, a vault, or both?

The answer depends on which problem shows up first. A business that processes one-time payments through a single processor with solid authorisation rates might not need either. A business that runs subscriptions across multiple markets, with recurring failed payments and no fallback when a processor has downtime, likely needs both.

First, identify the point of failure. If declines cluster around expired or reissued cards or the business is trying to shrink its own PCI footprint, a vault is the more direct fix. If declines or costs vary by processor, region, or card network, orchestration addresses that more directly. Businesses that experience both problems at once, which is common once they’re operating across several markets with recurring revenue, tend to need a combination of solutions.

Stripe’s Vault and Forward API is built for companies that need this pairing: a business stores a card once, benefits from network tokenisation that keeps that card current, and then uses the API to send that card to whichever processor its own routing logic selects, without needing to maintain separate vault infrastructure for each processor relationship.

How Stripe Payments can help

Stripe Payments provides a unified, global payments solution that helps any business – from scaling startups to global enterprises – accept payments online, in person and around the world.

Stripe Payments can help you:

• Optimise your checkout experience: Create a frictionless customer experience and save thousands of engineering hours with prebuilt payment UIs, access to 125+ payment methods, and Link, a digital wallet built by Stripe.

• Expand to new markets faster: Reach customers worldwide and reduce the complexity and cost of multicurrency management with cross-border payment options, available in 195 countries across 135+ currencies.

• Unify payments in person and online: Build a unified commerce experience across online and in-person channels to personalise interactions, reward loyalty and grow revenue.

• Improve payment performance: Increase revenue with a range of customisable, easy-to-configure payment tools, including no-code fraud protection and advanced capabilities to improve authorisation rates.

• Move faster with a flexible, reliable platform for growth: Build on a platform designed to scale with you, with 99.999% historical uptime and industry-leading reliability.

Learn more about how Stripe Payments can power your online and in-person payments or get started today.