.avif)
If you’re comparing a payment vault with a payment orchestration platform, you’re likely looking for a solution that will give you payment processor independence, portable tokens, and more flexibility over how you process and optimize your payments.
A standalone vault can give you portable payment tokens. But portability is only one part of the equation when building a high-performing payment stack. To turn that portability into better payment performance, your team still needs to build and run routing, authentication, retries, fallbacks, monitoring and reconciliation.
In other words, you need an orchestration platform.
You could attempt to build that functionality yourself. Or you can use a specialist payment orchestration platform that combines a processor-agnostic vault with the infrastructure to connect providers, control routing, and optimize payments, without requiring you to build and maintain every component yourself.
This article explains what each model gives you, what a vault-only approach still leaves you to build, and when payment orchestration is likely to be the better fit.
Primer gives you processor-independent vaulting, orchestration and wider payments infrastructure in one platform. Need advice? Talk to our payment experts and we’ll help you work through the options.
What’s the difference between a payment vault and payment orchestration?
While often spoken about in the same conversations, the functionality and benefits of a payment vault and a payment orchestration platform are very different.
Let’s start by looking at a payment vault.
What is a payment vault?
A payment vault securely stores a customer's payment credentials, replacing the sensitive card data with a token. The primary reason you would likely want to use a vault is that it significantly reduces your company’s PCI DSS compliance burden as you aren’t required to handle or manage your customer’s raw card data.
Many payment service providers offer their own token vaults to support saved-card and recurring payment experiences, as more and more companies look to reduce their compliance requirements, which aside from being incredibly complex, are also costly to manage.
The trade-off is that processor-issued tokens typically only work with that processor. If you want to move payment volume to another PSP, or build a sophisticated multi-processor routing strategy, you will either need to migrate credentials or sometimes force your customers to enter their payment details again, creating a negative customer experience.
Processor-agnostic token vaults solve this problem by storing payment credentials independently of any one processor. You get the same compliance benefits of tokenization, plus the flexibility to use stored credentials across multiple processors. This reduces processor lock-in and makes it easier to adapt your payment strategy as your business evolves.
What is a payment orchestration platform?
Payment orchestration lets you manage the providers involved in processing payments through a single platform. These include payment service providers, payment methods, fraud prevention providers, and other services in your payment flow.
It securely stores and tokenizes card data, reducing PCI DSS scope and allowing you to use stored credentials across connected processors.
You can then control how each transaction is handled: route payments by location or payment method, retry failed transactions, and send payments to a fallback provider when needed.
While you can build these capabilities yourself, doing so becomes incredibly complex and resource-intensive (more on that later).
Instead, more and more businesses are choosing to use specialist platforms like Primer, so they can focus on optimizing their payment strategy rather than maintaining the infrastructure behind it.
We discuss the trade-offs between build vs. buy in this article.
Payment vault vs payment orchestration: the key differences
The vault is the credential layer. Orchestration is the layer you use to build and run your payment strategy.
Should you use a payment vault or payment orchestration?
We speak with many merchants weighing this decision. But it is often framed as the wrong question. The better question is what you need your payments infrastructure to do.
The sections below break down the key considerations one-by-one in the order you need to ask them.
Question 1: Should you use a payment vault?
For most merchants, the answer is yes.
A token vault keeps raw card data out of your systems, reducing your PCI DSS scope and the cost and complexity of managing sensitive payment data yourself. Depending on how you capture and process payments, this can also affect which Self-Assessment Questionnaire (SAQ) applies to your business.
There are cases where merchants choose to handle card data directly. But they are rare, and they come with significant security, compliance, and operational responsibility.
The more useful question is: are you simply looking to reduce PCI DSS scope, or do you also want to improve payment performance?
If the answer is the latter, a standalone vault is only part of the solution. It gives you portable payment credentials, but not the tools to route transactions, manage retries and fallbacks, or optimize performance across providers.
Question 2: Should you use a PSP vault or a processor-agnostic vault?
The next question is what type of vault you need.
If you use one PSP and expect that to remain the case, using its vault can be an acceptable option. It is simple, familiar, and works for straightforward payment flows.
But if you want to use multiple processors, introduce redundancy, or keep your payment strategy flexible, a processor-agnostic vault is the stronger choice. It keeps credentials independent of a single PSP, so your stored payment data does not become the thing that limits your options.
Question 3: Should you use payment orchestration?
If you plan to use more than one PSP, payment orchestration is the obvious next step. It gives you the control layer to decide how payments move across your providers: where to route transactions, when to retry them, and what happens when a processor underperforms or goes down.
But the real question is not whether you need orchestration. It is whether you want to build and operate it yourself, or use a specialist platform.
Question 4: Should you build payment orchestration or use a specialist platform?
Building payment orchestration in-house means taking responsibility for more than routing. You need to build and maintain every PSP integration, wallet flow, retry and fallback strategy, authentication requirement, data mapping, monitoring tool, and processor update.
You also need to keep up with scheme mandates, manage PSP-specific 3DS implementations, and maintain the infrastructure required to optimize authorization rates over time.
There is also latency to consider. A vault-only setup can require multiple round trips between your backend and separate services for rules, payload creation, 3DS, network tokenization, and fallbacks. Each step can add delay and complexity to the payment flow for your customers.
Building in-house can make sense if payments infrastructure is a genuine strategic advantage for your business and you have the specialist team to operate it for the long term.
For most businesses, a specialist platform is the more practical choice. It gives you the infrastructure to connect providers, manage payment logic, support PSP-agnostic 3DS, and optimize performance, without building and maintaining every component yourself.
You retain control of your payment strategy, while the platform handles the complexity underneath it.
Our VP Product, Theo Spyrides has spoken a lot more on this topic here.
The case for using a payment orchestration platform
If you speak to some processor-agnostic vault providers, they will likely warn you against using a payment orchestration platform.
Their argument is simple: an orchestration platform costs more than a vault-only solution, gives you less control over your payment strategy, and will eventually limit you as your business scales.
It is a compelling argument. It is also incomplete.
Here’s what it misses.
Using a payment orchestration platform doesn’t cost more
A vault-only solution may have a lower platform fee. But that does not make it the lower-cost option.
A vault stores and tokenizes payment credentials. You still need to build and operate the infrastructure around it: PSP integrations, routing logic, retries, fallbacks, 3D Secure, network tokenization, monitoring, analytics, and reconciliation.
That work has a cost. It requires engineering time to build, payments expertise to optimize, and ongoing investment to keep every part of the stack working as processors, payment methods, and card scheme requirements change.
The right comparison is not the cost of a vault against the cost of an orchestration platform. It is the total cost of building and operating your own payment infrastructure against the cost of using specialist infrastructure.
Using a payment orchestration platform doesn’t mean giving up control
You should never give up control of your payment strategy.
You should choose which PSPs you use, decide how to distribute payment volume, and define the routing, retry, and fallback logic that supports your commercial goals.
A good payment orchestration platform gives you the tools to make those decisions. It does not make them for you.
With Primer, you can store credentials in a centralized, processor-agnostic vault while using Workflows to build and adapt your payment logic. You can add providers, change routes, test strategies, and respond to changes in performance without rebuilding your underlying infrastructure.
The alternative is not more control. It is more responsibility for building and maintaining the technology required to execute your strategy.
If you pick the right payment orchestration provider you won’t outgrow it
The question is not whether you will outgrow payment orchestration. It is whether you choose a platform that can grow with you.
Your business will add PSPs, expand into new markets, support more payment methods, and develop more sophisticated payment strategies. Your orchestration platform needs to evolve with you.
Look for a partner that gives you the flexibility to add and manage providers, adapt payment logic, test new strategies, and maintain visibility as your payment stack becomes more complex. You should not be constrained by prebuilt rules or forced to rebuild your infrastructure when your requirements change.
Payment infrastructure built for the full lifecycle
Primer is a Unified Payments Infrastructure platform that brings vaulting, orchestration, payment intelligence, and money movement together in one platform.
Our centralized vault keeps payment credentials independent of the PSP that first captured them. Workflows lets your team control how transactions move across providers with configurable routing, retries, fallbacks, 3D Secure, and network tokenization.
Primer also supports the work that happens after authorization. Observability, Reconciliation, Costs Overview, and Global Accounts help you understand payment performance through settlement, control payment costs, and manage money across currencies.
AI Companion sits across the platform, bringing together transaction, authorization, settlement, and cost data. It helps you identify performance changes, investigate what is driving them, and decide where to act next.
Merchants such as GetYourGuide, Conforama, and Dabble use Primer to give their payments teams the control and flexibility they need to make payments a lever for growth.
Vault or orchestration? Decide what you actually want to build
As we’ve explored in this article, the right question is not vault versus orchestration.
It is how much of your payment infrastructure you want to build and operate yourself, and how much you want to leave to specialist infrastructure so your team can focus on your core business.
That decision comes down to where your business creates the most value. For most businesses, the advantage comes from what they can do with payments, not from building and maintaining everything required to make them work.
See how Primer works for yourself: book a demo and talk to our payment experts
FAQs
What’s the difference between a payment vault and a payment gateway?
A payment vault stores and tokenizes payment details. A payment gateway transmits payment data between your checkout and the processor or acquirer. A payment orchestration layer can sit above both, helping you connect providers, route payments, apply retry logic and manage fraud prevention.
Can payment orchestration improve authorization rates?
It can improve authorization and approval rates when the routing and retry logic are designed well. Smart routing can send a transaction to the acquirer that performs best for a market, card type or issuing bank, while failover can recover eligible transactions when the first processor can’t complete them.
Is a token vault enough for recurring payments?
A token vault securely stores credentials for recurring payments and subscription billing, but you may also need account updater services, network tokens, retry logic, failover and rules for deciding which processor handles each payment.
Do you need orchestration to offer local and alternative payment methods?
No. You can integrate them directly. Orchestration becomes useful when you want to add and manage methods across several markets without maintaining every connection separately.
Does payment orchestration remove PCI compliance requirements?
No. PCI-compliant checkout and vaulting can reduce how much raw card data your systems handle and therefore reduce your PCI scope. Your exact responsibilities depend on how payment details are captured and which systems interact with cardholder data.
%20(1).png)
