Payment Orchestration

Payment orchestration is a technology layer that connects multiple PSPs, acquirers, and payment methods through a single integration, routing every transaction to the provider best suited to handle it. The orchestrator does not authorise payments, move money, or own a merchant account — its role is to coordinate the providers that do. (Gr4vy, 2026-06-10)

What it does — five core jobs

According to Gr4vy's 2026 guide, a payment orchestrator performs five functions:

Process the transaction request and apply pre-routing logic
Route the transaction to the optimal provider
Handle failover when a provider declines or times out
Vault credentials in a provider-agnostic store so tokens work across all PSPs
Consolidate reporting across every provider into a single dashboard

PYMNTS (February 2026) describes it as "a control layer that sits between merchants and a multilayered payments ecosystem," handling transaction routing, connectivity to multiple providers, Network Tokenisation|tokenization, reconciliation, and performance analytics.

Routing strategies

Smart routing (initial)

Smart routing selects the optimal PSP for each transaction before it is submitted, based on variables including card BIN range, issuing country, card type, transaction amount, and time of day. Rule-based routing configures this logic in a dashboard; AI-native platforms learn it from transaction history.

Gr4vy (2026) states smart routing typically lifts authorisation rates by 2–3 percentage points in most deployments, with more fragmented multi-PSP estates seeing larger gains.
PaymentBrief (May 2026) puts the range at 1–4 percentage points, noting "one auth rate point moves significant revenue at volume."
r/payments practitioners A/B-tested Primer smart routing vs manual rules for 90 days; ML outperformed manual rules by 1.8% overall, "with biggest gains in decline recovery routing, not initial routing decisions." (2026-04)
A senior routing engineer in r/payments (April 2026, 287 upvotes) identifies where ML routing earns its keep vs manual rules: (1) recovery routing after a soft decline, (2) time-of-day routing when PSP auth rates vary by hour, (3) new markets without historical intuition. For simple BIN/card-type routing, manual rules "have zero model latency."

Baby Bunting (Australia's largest specialty baby retailer) implemented Gr4vy with a dual-acquirer setup and failover routing rules, achieving a 2.8% authorisation rate uplift within the first four months; this contributed to 10% YoY sales growth including record online sales surpassing $120 million. (Gr4vy case study, published 2024-12-03 — pre-2026 but the only independently attributed retail case study retrieved)

Cascading retries (decline recovery)

Cascading routes a soft-declined transaction to a secondary PSP without the customer seeing a failure. This is distinct from initial routing — it operates reactively on failed authorisation attempts.

r/payments practitioners (2026-04) report that cascading retry logic alone recovers 3–4% of would-be failed transactions without ML.
One r/ecommerce merchant reports a 7.9% authorisation rate improvement (87.2% → 95.1%) across UK, DE, and FR from cascading retry logic alone. "Soft decline recovery is where the biggest gains came from, not initial routing optimisation." (r/ecommerce, February 2026, 198 upvotes)

Critical implementation rules (r/payments, November 2025):

Source dates from 2025-11 — included because no newer dedicated thread on retry mechanics was found.

Hard declines (Do Not Honour, stolen card) must never be retried — triggering repeat attempts tanks fraud scores
Only soft declines should cascade to a secondary PSP
Idempotency keys at order level are non-negotiable before implementing cascading — duplicate events can create double-fulfilled orders (r/ecommerce, May 2026, 187 upvotes)
Retry timing: a 3-second delay produced the best soft-decline recovery rate (41% recovered); immediate retry yielded only 28% ("issuer bank systems need a moment"); 30-second delay recovered 38% but too many customers had abandoned
UX: show a "processing" spinner during silent retry — "Customer sees 'processing' then success" vs "declined then succeeded" which prompts customers to call their bank

Failover / redundancy

A secondary benefit distinct from optimised routing: automatic failover to a backup PSP when the primary experiences an outage or latency spike.

An r/ecommerce merchant (May 2026) reports: "When Stripe had their partial EU outage in March 2026 we automatically failed over to Adyen with zero customer impact. That alone justified the orchestration layer for us." (112 upvotes)

Authorisation rate benchmarks

Vendor-reported authorisation rate improvement figures diverge significantly. Gr4vy (2026) states 2–3 percentage points typical, 14% recoverable share of failed-payment revenue. PaymentBrief (May 2026) puts the range at 1–4 points. IXOPAY (Money20/20 2025, vendor claim) cites an average 15% improvement. SiGMA panel (February 2026) cites a practitioner range of 0.5–20%. The high figures reflect specific configurations (MCC realignment, multi-acquirer cascading in high-delta markets) rather than baseline smart routing. The Gr4vy 14% "recoverable failed revenue" figure has no independent corroboration. No independent third-party benchmarks (Forrester, Gartner, McKinsey) were found — all figures originate from vendor content or vendor case studies.

Country-level granularity matters: r/ecommerce practitioners (April 2026) note "the blended number hides the story" — one merchant reports UK cards improved 3%, German cards 9%, French cards 6% (167 upvotes).

Italy consistently cited as the highest-gain European market for local acquirer routing:

r/ecommerce (May 2026, 234 upvotes): "The delta in Italy between our global PSP and Nexi was 8.3% in Q1 2026"
r/fintech (separately corroborated, 134 upvotes): "+7.2% auth rates on Italian cards with Nexi via Spreedly"
r/payments (January 2026): domestic debit routing in Italy, Germany, Poland is "structural, not something Stripe ML can train away" — local acquirers connect differently to the card networks

One r/ecommerce merchant (6-month update, May 2026, 521 upvotes) reports switching from Stripe-only to multi-PSP via Primer: overall auth rate +5.4%, with +9.1% in FR and IT specifically, recovering ~€95k/month at a platform fee of €2,800/month plus 3 weeks of engineer time.

Volume thresholds and ROI

There is active debate on the minimum GMV threshold at which orchestration becomes economically justified. Community consensus is broadly €10–15M, but no single figure is authoritative.

PaymentBrief (May 2026): recommend evaluating only when processing above ~$5M/month or when needing PSP redundancy, vault portability, or intelligent routing
r/ecommerce (March 2026, 112 upvotes): "Don't. Spend that energy on conversion rate optimisation, checkout UX... Come back to orchestration at €8-10M."
r/fintech (March 2026, 267 upvotes): "The tipping point seems to be around $15-20M annual payment volume... Two years ago it made sense at €50M+. Vendors have brought costs down enough that the math works at €10-15M." (threshold declining)
At €3.5M GMV: one r/ecommerce merchant reports positive but marginal ROI (€8k/month recovered, €1,800/month platform fee, 6 weeks engineer time) — "If we were doing €5M+ the case would be clearer." (May 2026)
PaymentBrief: "orchestration adds overhead without proportional benefit with a single PSP"

Vendor landscape

All vendors below charge 2–8 basis points (0.02–0.08%) on volume processed through the orchestration layer; at $10M/month, 5bps = $5,000/month. (PaymentBrief, May 2026) (as-of 2026-05)

Pricing figures from PaymentBrief May 2026 — volatile; verify before acting on.

Vendor	Founded	Positioning	Community signal
Spreedly	2009	PSP-agnostic vaulting, 120+ gateway integrations, broadest connector coverage	"Most established" but "feels like 2018 tooling" (r/fintech, 189 upvotes)
Primer	2020, London	No-code visual workflow builder, developer-friendly	Praised for DX; support SLA gaps noted (312 upvotes). 4 hours to diagnose routing misconfiguration.
Gr4vy	2020	Cloud-native, dedicated single-tenant instance per merchant, data residency guarantees	Praised for vault portability — 94% payment method retention through PSP migration (241 upvotes)
Payrails	Berlin	Payment operating system: orchestration + routing + retries + vaulting + analytics + reconciliation + payouts	$53M raised, backed by a16z and General Catalyst
IXOPAY	—	Enterprise smart dynamic routing	Vendor claim: average 15% auth rate improvement (low confidence; Money20/20 2025)
Corefy	—	White-label infrastructure for payment institutions	€2,500–€6,000/month flat fee (as-of date unknown)
BR-DGE	UK	Single integration across multiple PSPs	FTT Payments 2024 speaker
Yuno	—	AI-driven routing	Vendor claim: 8% average auth rate uplift (as-of 2026)

PaymentBrief (May 2026) characterises the three independent leaders: Spreedly for connector breadth; Primer for no-code workflow accessibility; Gr4vy for cloud-native dedicated-instance deployment and data residency.

PSP-native alternatives (the "do you need a standalone orchestrator?" debate)

"The 'Stripe is good enough' argument breaks down the moment you need Adyen AND Stripe AND a local acquirer. The orchestration layer is the glue." (r/payments, 198 upvotes, January 2026) VS "Stripe's Adaptive Acceptance uses ML to recover declined transactions and added 2-3% auth rate recovery without any orchestration layer. For many merchants that's good enough." (r/payments, 234 upvotes, January 2026). Community broadly resolves this as US-centric = Stripe fine; cross-border Europe/APAC = orchestration net positive.

Stripe Orchestration (previewed Sessions 2025): allows merchants to route transactions to their processor of choice, with cross-PSP visibility through a single Stripe Dashboard and unified dispute management. GA status unconfirmed as of this research. Roadmap includes A/B testing across PSPs and bring-your-own processor integrations. (Stripe Blog, 2025-05)

Adyen (April 2026): published a nuanced editorial arguing that orchestration's value depends heavily on the problem being solved — for high-volume digital businesses it provides genuine resilience insurance, but for others "redistributes rather than reduces risk, adding operational complexity and fragmenting data." (Adyen Knowledge Hub, 2026-04-27)

Adyen Intelligent Money Movement (launched April 2026): unifies payments, liquidity management, and payouts on a single platform. Adyen holds its own banking licences across the US, UK, and Europe, enabling direct connections to payment rails and card schemes. (Adyen Press, 2026-04-09)

Architecture decisions

Multi-tenant vs dedicated instance

Gr4vy (2026) claims to be the only orchestration platform built on dedicated single-tenant cloud instances (AWS, GCP, or Azure), where each merchant's orchestration layer, vault, dashboard, and routing logic runs on isolated infrastructure. This enables data residency requirements for markets where payment data cannot leave the country.

"Only" claim is vendor-made and independently unverifiable. PaymentBrief (May 2026) corroborates the data residency use case but notes Gr4vy's model "requires strong cloud infrastructure capability on the operator's side and carries higher implementation complexity and cost."

Build vs buy

An r/fintech engineer (June 2026, 267 upvotes) advises against building in-house routing: "We have 3 engineers maintaining our routing layer and it still breaks in ways we don't catch immediately. The orchestration vendors have already solved problems we didn't know we had. The build cost looks cheap at the start; the maintenance cost is invisible until it isn't." Recommendation: do not build unless at Shopify/Amazon scale with a dedicated payments engineering team.

Network tokenisation

Network Tokenisation is described in r/fintech (June 2026) as "the hidden gem of 2026." Primer and Gr4vy both provide native Visa VTS and Mastercard MDES network token support. One practitioner reports +3.1% authorisation rate from switching to network tokens alone, without routing changes. "Issuers can see the device binding; network tokens get better auth rates than PANs."

Vault portability

Vault Portability is cited as the killer feature "nobody talks about enough": PSP-agnostic token vaulting means stored payment methods remain portable when switching PSPs. One Gr4vy customer reports retaining 94% of stored payment methods through a migration from Braintree. "With Stripe or Adyen you lose the stored cards when you switch — customers have to re-enter." (r/fintech, June 2026, 241 upvotes)

Platform-specific: Shopify

On Shopify Plus, using a third-party orchestration layer typically means losing:

Shopify Payments → triggering a 0.15% additional transaction fee (Shopify Plus rate) that offsets auth rate gains
Shop Pay → anecdotally 5–10% better checkout conversion for returning customers (r/shopify, February 2026, 145 upvotes)

r/shopify practitioners note headless Shopify (Hydrogen or custom frontend) has significantly more integration flexibility than the native Shopify theme checkout. (February 2026)

Operational complexity

Reconciliation

When running 3 PSPs and an orchestration layer, finance teams have 4 data sources to reconcile. r/fintech (April 2026, 112 upvotes): "We had to build a proper data pipeline to normalise payment events across all of them. Budget for that engineering work."

New single point of failure

The orchestration layer itself becomes a new single point of failure: if it goes down, payments fail even if all PSPs are live. r/fintech practitioners (June 2026, 198 upvotes) advise getting contractual uptime SLAs and reviewing vendor incident history. Gr4vy's own 2026 guide also flags this as a risk.

Negotiating leverage

Having an orchestration layer creates commercial leverage with PSPs. r/fintech (April 2026, 198 upvotes): "We got Stripe to cut our processing fees by 12bps just by having that credible alternative."

What payment orchestration does not solve

Gr4vy (2026) explicitly states orchestration does not:

Negotiate PSP contracts (the leverage only converts to better rates if someone acts on it)
Eliminate the need for someone to own payments operations
Fix a checkout with other UX problems upstream of payment submission
Eliminate the new single point of failure it introduces

2026 trends

Agentic commerce

The most significant near-term shift cited in 2026 sources is Agentic Commerce — AI agents initiating and completing purchases on behalf of consumers inside conversational interfaces. The payments infrastructure required for agent-driven transactions differs from infrastructure for human checkouts.

Gr4vy (June 2026): claims to be the first orchestration platform to launch a dedicated Agentic Developer Kit (self-claim; "first" independently unverifiable)
Adyen Agentic (announced June 2026): a suite of modular APIs with three layers — Agentic Feed, Agentic Cart, Agentic Payments — providing a single integration that translates across conversational AI commerce channels, protocols (UCP, AP2, ACP), and payment methods. Early ecosystem partners include American Express, Mastercard, Salesforce, Visa, ESW, Sézane, and SharkNinja. (Adyen Press, 2026-06-16)
Stripe Sessions 2026: announced the Machine Payments Protocol (MPP, co-authored with Tempo), Shared Payment Tokens (SPTs) enabling Mastercard Agent Pay and Visa Intelligent Commerce, and an Agentic Commerce Suite for platforms. Forrester characterised this as Stripe "rearchitecting payments for an agentic AI economy." (Stripe Blog, 2026)

AI-native routing

The 2026 market is bifurcating between traditional rule-based orchestration platforms (merchant configures routing in dashboards) and AI-native platforms (merchant describes desired outcome; system determines routing). Category leaders are migrating toward the latter. (FyscalTech, 2026)

Framing is shifting from orchestration as "a necessary but largely invisible layer to a strategic revenue driver." (PYMNTS, February 2026)

Composable payments

IXOPAY introduced a "composable payments" model at Money20/20 Europe 2025: merchants select modular components aligned with a specific business goal — revenue growth, risk mitigation, or cost optimisation — rather than committing to a single monolithic stack.

IXOPAY noted at Money20/20 Europe 2025 that digital-first companies now launch globally from day one, compressing the revenue milestone at which comprehensive payment orchestration becomes necessary from ~$1B down to $10–50M. (as-of 2025; stale-risk)

IXOPAY figures cited from Money20/20 Europe 2025 content — vendor-sourced, pre-2026.

Regulatory context

PSD3 / PSR: The European Commission published PSD3 and PSR proposals in June 2023. The EBA has up to 50 new mandates (security, prudential, authorisation, consumer protection) to deliver under PSD3, PSR, and FIDA proposals by 2027, shaping how orchestration layers handle 3D Secure 2 (3DS2)|SCA, open banking, and consumer data. (EBA Work Programme 2026, January 2026)
EBA No-Action Letter: The PSD2/MiCA No-Action Letter transition period ended 2 March 2026, addressing authorisation processes and coordination between payment services and crypto-asset frameworks — relevant to orchestration layers routing to crypto/stablecoin rails. (EBA, 2026-02-12)
FIDA (Financial Data Access): mentioned in EBA 2026 work programme as a third regulatory pillar alongside PSD3/PSR — not yet covered in this vault.

Market size

Market research firms quote materially different figures. CAGR estimates range from 13.2% to 31.56% for the same forecast period. 2026 base market size estimates range from $2.65B (Research and Markets) to $10.4B (another). Wide variance reflects differing scope definitions (platform software only vs processed volume share). No single figure should be cited without flagging its source and methodology.

Directional signal: the market is growing rapidly, driven by expansion of cross-border retailing and multi-PSP adoption. Around half of online merchants now use more than one payment provider (as-of 2026-06). (Gr4vy, 2026-06-10)

Key terms

Term	Meaning
PSP	Payment Service Provider (e.g. Stripe, Adyen, Checkout.com)
Acquirer	Bank or institution that processes card transactions on behalf of merchants
BIN routing	Routing based on the Bank Identification Number (first 6–8 digits of card number)
Cascading	Automatically routing a declined transaction to a secondary PSP
Hard decline	A final issuer decline (Do Not Honour, stolen card) — never retry
Soft decline	A temporary or correctable decline — eligible for cascading retry
Token vault	Storage of payment credentials in a PSP-agnostic format
Network Tokenisation	Card credentials replaced with scheme-issued tokens (Visa VTS, MC MDES), improving auth rates
Vault Portability	Ability to migrate stored payment methods between PSPs without losing tokens
Adaptive Acceptance	Stripe's native ML-based retry and optimisation layer — a PSP-native alternative to standalone orchestration
Smart Retries	Automated retry logic applied to soft-declined payments
Machine Payments Protocol	Stripe's 2026 standard for agent-initiated payment flows
Shared Payment Tokens	SPTs enabling cross-agent, cross-scheme payment token interoperability

Benchmarks (as-of 2026-07-08)

Metric	Range	Source	Confidence
Typical smart routing auth rate uplift	1–4 pp	PaymentBrief (May 2026), Gr4vy (June 2026)	med
Cascading retry recovery (soft declines)	3–4%	r/payments (April 2026)	med
Network tokenisation uplift (standalone)	~3.1 pp	r/fintech (June 2026)	low (single reported case)
Optimal retry delay (soft declines)	3 seconds	r/payments (Nov 2025, stale-risk)	low (single A/B test)
Min GMV threshold (community consensus)	€10–15M/yr	r/fintech, r/ecommerce (2026)	med
Auth rate delta Italy (global vs local acquirer)	7–9 pp	r/ecommerce, r/fintech (2026)	med
Orchestration layer pricing	2–8 bps	PaymentBrief (May 2026)	med
Vault portability retention rate	~94%	r/fintech (June 2026, single case)	low
Market CAGR (conflicting estimates)	13–32%	Multiple research firms (2026)	low (contradiction)

What practitioners report

r/fintech (April 2026, 612 upvotes) on PSP lock-in and localisation: "if you're doing >€5M in payments volume and operating cross-border, you're almost certainly leaving money on the table by being mono-PSP. The auth rate difference between a global PSP and local acquirer on domestic transactions in markets like DACH or Italy can be 4–10%."

r/fintech (June 2026, 267 upvotes) on build vs buy: "Would not recommend [building in-house] unless you're at Shopify/Amazon scale and have a dedicated payments engineering team... The build cost looks cheap at the start; the maintenance cost is invisible until it isn't."

r/fintech (March 2026, 145 upvotes) specifically on fashion: "Fashion brands with European ambitions basically have to think about orchestration. Our customer base shops from DE, FR, IT, NL, ES and each market has meaningful auth rate differences with local vs global acquirers."