A payment orchestration platform connects you to multiple payment providers through one integration and routes each transaction to the one most likely to approve it at the best cost. Whether you need one, and which kind, depends almost entirely on facts about your business instead of facts about the technology.
That is why generic buying advice fails here. A subscription business losing customers to failed renewals and a cross-border retailer trying to add local methods are solving different problems with the same category of product. This guide is organized around the questions that actually determine the answer, with examples from businesses that have been through it.
Key takeaways
Last reviewed: October 2026.
The figures below come from published Gr4vy case studies and are the specific outcomes each company reported. They are gathered here because they are the hardest numbers to find elsewhere in this category, where most published claims are projections rather than results.
| Outcome | Business | Context |
|---|---|---|
| 2.8% uplift in authorization rates within four months | Baby Bunting, retail, Australia | Dual-acquirer setup with failover routing |
| 27 days to complete full integration | FuturHealth, telehealth, United States | Dynamic routing across multiple PSPs with retry logic |
| 3 days to add a new payment method, down from three to six weeks | Ding, mobile top-up, 140+ countries | No-code rules, method varied by market |
| 180,000+ students supported | Mattilda, education payments, Latin America | White-label orchestration, bring-your-own-acquirer |
Results vary by business, market, and existing payment setup. Each is linked to its full case study in the relevant section below.
A payment orchestration platform sits between your checkout and your payment providers. It connects to your payment service providers, acquirers, payment methods, and fraud tools, then decides which provider handles each transaction according to rules you set.
It does not replace your existing providers. It coordinates them, which is why adopting orchestration does not mean abandoning the payment relationships you already have. For the full mechanics, see Gr4vy’s guide to payment orchestration.
The market has grown accordingly. Grand View Research valued the global payment orchestration platform market at USD 1,386.9 million in 2023, projecting USD 6,520.4 million by 2030 at a 24.7% compound annual growth rate.
Volume is the first question any advisor will ask, because it changes the answer more than anything else. The thresholds below reflect patterns across Gr4vy implementations rather than an industry standard, and they are rules of thumb instead of hard cutoffs.
Under roughly $100,000 per month. Orchestration is usually premature. A single well-chosen payment service provider covers the need, and the platform cost plus the configuration work will not pay for itself. The exception is a business already selling into several countries, where method coverage matters more than volume.
Mid-market, roughly $100,000 to several million per month. This is where the case starts to hold, and it usually arrives through a specific problem instead of a general ambition: a second market, a provider outage, approval rates that stopped improving, or a second PSP added for redundancy that now needs managing. At this stage the gains come from routing and recovery more than from scale economics.
Multi-million per month enterprise. Here small percentages are large numbers and the arithmetic does most of the work. A single point of authorization-rate improvement on $100 million of annual volume is roughly $1 million recovered. Enterprises also tend to have the specific problems orchestration solves best: multiple acquirers, several markets, and no unified view across them.
A useful calibration: the Australian retailer Baby Bunting secured a 2.8% uplift in authorization rates within the first four months of moving to a dual-acquirer setup with failover routing, as reported in its case study. On retail volume at that scale, a lift of that size is a material revenue line, which is why volume changes the calculation so sharply.
These are the two most common reasons businesses adopt orchestration, and they lead to different implementations.
If the problem is declined payments, the relevant capabilities are intelligent routing, retry logic, failover, and network tokenization. The mechanism is giving each transaction more than one chance to succeed and sending it to the provider most likely to approve it.
FuturHealth, a US telehealth business, is a clear example. Subscription healthcare makes a failed payment a potentially lost patient relationship. It implemented dynamic routing across multiple PSPs with built-in retry logic to recover transactions that would previously have failed, and completed the entire integration in 27 days, as documented in its case study. The 27-day figure matters as much as the outcome, because a decline problem is usually urgent.
If the problem is international method coverage, the relevant capabilities are breadth of connections, local acquiring, and the speed of adding a method once you decide you need it.
Ding, the international mobile top-up service operating across more than 140 countries, cut the time to integrate a new gateway or local payment method from three to six weeks down to three days. It used no-code rules to show different methods by market, prioritizing Pix in Brazil and PayPal in Germany, matching each market’s actual preference. The detail is in the Ding case study. For a business entering markets continuously, that difference determines whether local methods get launched at all.
Many businesses have both problems. The sequencing question is which one is costing more today.
B2C businesses gain most from authorization rates and method coverage; B2B businesses gain most from payment terms, bank rails, and reconciliation. The distinction changes which capabilities matter.
B2C businesses deal in high transaction counts at lower values, where authorization rates, checkout conversion, and local method coverage drive the return. Fractions of a percentage point compound across millions of transactions.
B2B businesses deal in fewer, larger transactions where the priorities shift to payment terms, invoicing, bank transfer and ACH support, reconciliation, and handling the longer settlement cycles that business customers expect. Card acceptance matters less, and the cost difference between cards and bank rails matters more.
Platform businesses serving other businesses are a third case, and the most complex. Mattilda, which provides collections management and payment processing for private schools across Latin America, needed to offer payments to the schools it serves under its own brand without becoming a payment facilitator and absorbing that compliance and risk burden. It used white-label orchestration to deploy dedicated payment environments per school, with a bring-your-own-acquirer model letting each institution keep its own acquiring relationships. Mattilda now supports more than 180,000 students, and the capability became a significant growth driver. The full account is in the Mattilda case study.
Woolworths Group followed a comparable path at larger scale, selecting Gr4vy to power the payments platform of Wpay, its payments business serving both its own brands and external businesses, as set out in the Wpay case study.
If you are a platform that wants to offer payments to your merchants, that is a different product requirement from a merchant optimizing its own checkout, and it should be an explicit part of your evaluation.
Subscription businesses usually have the strongest case for orchestration, because a failed renewal can end the customer relationship instead of losing a single sale. The problem is structurally different from one-time retail.
In one-time retail, a failed payment loses one sale. In subscriptions, a failed renewal can end the customer relationship entirely, which is why involuntary churn is the metric that matters. The relevant capabilities are retry and dunning logic, network tokens and account updater so stored credentials stay valid when cards are reissued, and routing that gives a renewal several chances to succeed.
Provider-agnostic vaulting matters here more than anywhere else. If your stored credentials are locked to one PSP, you cannot route a renewal elsewhere when that PSP declines it, and you cannot change providers without asking every customer to re-enter their card.
Setplex, an OTT streaming platform provider, operates exactly this model, where recurring billing across an international subscriber base determines revenue. It chose orchestration to support payment acceptance across its platform, as described in the Setplex case study.
Subscription detail matters too. Free trials create a first-charge conversion point where decline recovery is disproportionately valuable. Usage-based billing produces variable amounts that behave differently from fixed charges under issuer risk rules. Flat-rate monthly billing is the simplest case.
Physical goods bring shipping, fulfillment timing, and the gap between authorization and capture, plus returns and refunds, and the chargeback exposure that comes with delivery disputes. Merchants selling both online and in store face an additional problem: two disconnected payment setups, fragmented reporting, and inconsistent customer experience.
Trek, the bicycle manufacturer and retailer, addressed exactly that by unifying payments across its digital and physical retail operations instead of maintaining separate stacks, as described in the Trek case study. Any merchant with both channels faces the same split.
Digital goods such as SaaS, courses, and memberships have no fulfillment but higher fraud and chargeback risk, instant delivery that removes the authorization-to-capture window, and often a global customer base from day one, which pulls local payment methods forward in the priority list.
Marketplaces sit across both. Much Better Adventures, the UK adventure travel marketplace, selected Gr4vy to orchestrate payments and support global marketplace growth, where customers are in one market and suppliers and currencies in others.
If you already run two or more gateways, orchestration is almost certainly worth evaluating. If you run one and it works, it probably is not yet. This question reveals more about readiness than almost any other.
One gateway, working fine. Orchestration adds a layer you may not need yet. Revisit when a second market, a second provider, or an outage forces the question.
One gateway, not working well. Consider whether the problem is the provider or the architecture. Sometimes switching providers is the right answer and orchestration is premature, though orchestration does make future switching far less painful.
Two or more gateways already. This is the clearest signal. Businesses usually reach multi-PSP setups organically, adding a provider for redundancy or a new market, and each decision was reasonable in isolation. Together they produce fragmentation: different APIs, different reporting formats, different reconciliation timelines, and no single view of performance. That is the condition orchestration was built for.
Importantly, orchestration sits above your existing providers. Your contracts, merchant accounts, and acquiring relationships stay in place.
A card-first checkout works reasonably in the United States, where cards carry roughly two-thirds of payments. It works poorly in Germany, where PayPal and invoice payment lead and cards are fourth. It fails in Brazil, where Pix dominates, and across Southeast Asia, where cards reach under 15% of potential customers in most markets. Geography drives method requirements more than any other factor, and the differences are larger than most merchants expect.
Each new market typically means local payment methods, local acquiring for better approval rates, and local compliance. Gr4vy’s market guides cover the USA, Germany, Brazil, and Southeast Asia in detail.
If you sell into one country, method coverage is a minor consideration. If you sell into five, it is probably your primary one.
This is a question about who owns payments in your organization, and it is frequently decided by default rather than deliberately.
No-code, owned by a product or payments team. Routing rules, method configuration, and provider changes happen through a dashboard without engineering tickets. The advantage is speed: the people who understand the commercial problem can act on it directly. Ding’s ability to prioritize different methods per market came from exactly this, using no-code rules rather than a development cycle for each change.
API-first, owned by engineering. Deeper customization, logic that lives in your own codebase, and tighter integration with existing systems. The cost is that every payment change competes with other work in the engineering backlog.
Most serious platforms offer both, and the honest question is less which the platform supports and more which your organization will actually use. A no-code platform nobody is assigned to steer delivers very little, and an API-first setup in a company without payments engineering capacity becomes a bottleneck.
Pricing models vary: per transaction, tiered by volume, subscription, infrastructure-based, or a blend. The platform fee sits on top of your existing provider costs, so orchestration is an added cost justified by what it recovers.
The honest way to evaluate it is to model your own numbers instead of trusting a headline figure. Estimate the authorization-rate improvement you expect, the routing cost savings, the value of avoided downtime, and the engineering time returned, then compare that against the specific quoted cost at your volume. Watch for fees that scale punitively as you grow.
For the full set of evaluation criteria including neutrality, data portability, and reliability, see Gr4vy’s enterprise buyer’s guide.
The orchestration market includes Gr4vy, IXOPAY, Payrails, Primer and Spreedly, among others, listed alphabetically. We are not going to rank them here, because a vendor ranking its own category is of limited use to you, and because features and pricing change faster than any published comparison stays accurate.
What is more useful is knowing what to ask every provider you shortlist:
Ask the same questions of every provider, including us, and compare the answers instead of the marketing.
Three developments will shape payment decisions through 2027, and each is worth building toward instead of reacting to.
Agentic commerce. AI agents initiating purchases on consumers’ behalf require a payment stack that can identify, route, and control agent-initiated transactions separately from ordinary traffic. Consumer trust is lagging the technology, so this is a readiness question more than an urgent one, but the merchants positioned early will not be rebuilding under pressure.
Real-time payment rails. Canada’s Real-Time Rail launched in the fourth quarter of 2026 and will see its first full year of merchant-facing products in 2027, the EU’s instant payments mandate has taken effect, and Pix and UPI continue expanding. Account-to-account payments are becoming viable alternatives to cards in more markets each year, usually at materially lower cost.
Regulatory change. PSD3 and the Payment Services Regulation in Europe, BNPL regulation in multiple markets, and continuing data localization requirements all affect how payments must be handled. A payment stack that can absorb a rule change through configuration is worth more than one requiring an engineering project each time.
The common thread is that the method and rule set keeps moving, which argues for an architecture where adding or changing something is cheap.
What is a payment orchestration platform?
A payment orchestration platform connects a business to multiple payment service providers, acquirers, and payment methods through a single integration, then routes each transaction according to configurable rules. It sits above existing providers and coordinates them instead of replacing them, so a business can adopt orchestration while keeping its current payment relationships.
What transaction volume do you need for payment orchestration?
There is no fixed threshold, but under roughly $100,000 per month a single payment service provider usually suffices, unless the business already sells into several countries. The case strengthens through the mid-market and becomes compelling at multi-million monthly volumes, where a single percentage point of authorization improvement represents substantial revenue.
Does payment orchestration replace my payment gateway?
No. Orchestration is a coordinating layer that sits above gateways, PSPs, and acquirers, deciding which handles each transaction. Existing contracts, merchant accounts, and acquiring relationships remain in place, which is why orchestration can be adopted without renegotiating provider agreements.
How long does it take to implement payment orchestration?
It varies with the complexity of the existing setup and the number of providers and markets involved. As a documented reference point, FuturHealth completed its full integration in 27 days, as reported in its case study. The more useful question during evaluation is how much work falls on your own engineering team.
Is payment orchestration better for B2C or B2B?
Both, for different reasons. B2C businesses gain most from authorization rates, checkout conversion, and local method coverage across high transaction counts. B2B businesses gain more from payment terms, bank transfer and ACH support, reconciliation, and handling longer settlement cycles. Platform businesses serving other businesses have a third set of requirements centered on white-label and sub-merchant capability.
Can payment orchestration help with failed subscription payments?
Yes, and this is one of its strongest use cases. Retry logic, dunning, network tokens, and account updater keep stored credentials valid and give renewals several chances to succeed. Provider-agnostic vaulting matters particularly here, since credentials locked to one PSP cannot be routed elsewhere when that PSP declines.
Do I need engineers to run a payment orchestration platform?
For the initial integration, generally yes. For ongoing operation it depends on the platform and how you intend to work. No-code platforms let product or payments teams change routing rules and add methods through a dashboard, while API-first approaches keep that logic in your codebase. The real question is which model your organization will actually staff.
How much does payment orchestration cost?
Pricing varies by provider and model, including per-transaction, tiered, subscription, and infrastructure-based approaches, and it sits on top of existing provider costs. The case rests on offsetting that through authorization-rate gains, routing savings, reduced downtime, and lower engineering overhead, so the honest evaluation is to model your specific expected improvement against the specific quoted cost.
The question “which payment orchestration platform is best” has no useful answer, because the platforms converge on similar claims and the right choice depends on facts about your business instead of facts about them.
The questions that actually resolve it are the ones above: what you process, what is broken, who your customers are, what you sell, what you already run, where you sell, and who will own payments internally. A business losing subscription renewals needs different things from one entering three new markets, even though both are shopping for the same category of product.
The examples throughout this guide show how differently that plays out in practice. A retailer recovering 2.8% of authorizations, a telehealth business integrating in 27 days, a top-up service cutting method launches from weeks to days, and an education platform building a white-label payments business for 180,000 students were all solving genuinely different problems with the same category of infrastructure.
Gr4vy is a cloud-native payment orchestration platform connecting merchants to more than 400 payment providers and methods through a single integration, with each merchant running on a dedicated instance. To talk through which of the questions above apply to your business, get in touch with our team.
Credit cards lead Canadian payments at 43%, with Interac debit at 25% and e-Transfer rising.…
Credit cards lead Japanese e-commerce at 55%, but konbini cash takes a fifth of online…
Checkout used to be a destination. A final step where users reviewed their cart, entered…
PayPal leads German e-commerce at 28.7%, invoice payment second, and cards a distant fourth. Germany…
The partnership gives Gr4vy access to Unlimit’s acquiring and payment-method capabilities, supporting local acceptance and…
Debit cards dominate UK payments, with contactless at 39% and Faster Payments second overall. The…