Payment orchestration
Payment orchestration: what it is and how it works
The layer that sends each transaction to the processor you choose, retries a failure through your backups, and hands your app one consistent result.
Works with 130+ providers, including
Stripe
Worldpay
PayPal
Store each merchant’s PSP credentials in the Orchestra vault and refer to them by account name in your requests.
Route every payment to the processor you choose
Your application picks the provider and merchant account on each transaction, with an ordered fallback list behind it. Routing travels with the request, so a change applies to the next payment.
- By cost: the PSP you pay least for the transaction type
- By geography: EU cards to EU processors
- By merchant: each merchant through its own provider account
- Combined: any mix, with fallbacks behind it
One integration to Orchestra connects a merchant to Stripe, Adyen, Worldpay and the rest of the providers Orchestra supports.
Failover
When a gateway goes down, payments keep moving
When a provider fails or is unavailable, Orchestra tries the next provider in your list, with no action from the customer.
Sequential fallback
Orchestra works down your list until one provider succeeds or the list runs out.
Instant gateway switching
A failed or timed-out transaction retries on the next processor in your list.
Your fallback order
Decide which backup processors to try, and in what order, on each transaction.
Nothing extra for the customer
Fallback happens behind the scenes. The customer sees one result.
Global acceptance
Every market, one integration
Every market expects different payment options. Orchestra already connects the regional methods, so you launch without a regional build.
Global methods
Apple Pay, Google Pay, Stripe, Worldpay, Adyen and more.
Regional methods
Bank payments in the US, the EU, the UK and Israel, plus providers such as Shift4, CCV and Rapyd.
Country-specific methods
UPI in India, more local methods on request, and providers such as PesoPay and Fat Zebra.
Currency flexibility
Charge in any currency your chosen provider supports.
Local providers
Connect the regional processors your merchants already use.
Methods per transaction
Choose which payment methods the form shows on each transaction.
Shrink your PCI DSS scope
Card entry runs client-side in the Orchestra Library, so cardholder data never touches your servers. Your backend charges tokens through the API, which keeps your PCI DSS scope small. How much it is reduced depends on your implementation.
SAQ D for Service Providers
For software platforms, with most controls outsourced to Orchestra
SAQ A
For merchants buying directly, and for your platform’s merchants
Developers
One integration, two working parts
The JavaScript Library captures payment in your checkout. The REST API drives everything after capture. Both sit on the same routing and failover layer.
const response = await fetch('https://api.orchestrasolutions.com/PaymentGateway/charge', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-Api-Key': 'YOUR_API_KEY'
},
body: JSON.stringify({
amount: 25.00,
currency: 'USD',
paymentGatewayAccountName: 'stripeProduction',
fallbackUpgs: [
{ paymentGatewayAccountName: 'adyenBackup' },
{ paymentGatewayAccountName: 'worldpayTertiary' }
],
card: {
cardNumber: '@nQGywsQE9gbURtrXEjTZwtWqeMdK9nsO',
cardHolderName: 'Jane Smith',
expirationMonth: 12,
expirationYear: 2027
}
})
});
const result = await response.json();REST API
Charges on stored tokens, captures, refunds and recurring billing from your backend.
JavaScript Library
Pre-built components for cards, Apple Pay and Google Pay. Card data stays off your servers.
Open sandbox
Test immediately, no approval needed. The sandbox mirrors production.
How the routing works
A direct integration ties your revenue to one processor. An orchestration layer gives every payment a way through.
One processor
Direct integration
- A decline is a lost sale, with no retry
- An outage on your processor is an outage on your revenue
- A second processor means a second hand-built integration
- Routing between processors is logic you build for each integration
Orchestrated routing
With Orchestra
- A decline retries through a backup processor automatically
- An outage fails over to a working processor instead of blocking checkout
- New processors connect through the integration you already have
- Routing is a few fields on each request, not a separate build
Free to start • No credit card required
What orchestration changes
Every transaction gets a backup, and one integration covers every processor you choose.
What you get
130+
providers through one integration
Under 2 weeks
to add a provider you request, at no cost
1
response format, with decline reasons normalized
SAQ A
for your platform’s merchants
Questions and answers
Does Orchestra ever hold my funds directly?
Absolutely not; we don’t touch your funds. Your customers’ money flows directly from them to the payment gateway you used and from there to the settlement account defined with the gateway. We focus on facilitating and securing your transactions, leaving the financial handling to your payment providers.
What currencies does Orchestra support?
We support all currencies offered by the payment gateways integrated with our platform. If your gateway can handle it, Orchestra can, too. Multi-currency support has never been easier to manage.
Can Orchestra help me switch payment processors?
Of course. Whether you’re looking to replace an existing processor or add more options, Orchestra makes switching effortless. With our platform, you can test new gateways or payment methods without disrupting your current systems.
Does Orchestra support payment routing?
Yes. On each transaction your application chooses the payment provider, the merchant account and an ordered list of fallback providers, using whatever rules you like: transaction type, currency, the customer’s country or cost. Orchestra carries out that choice and works down the fallback list until a provider succeeds.
How long do new integrations take?
New integrations you request are added in under two weeks, at no cost, after a feasibility review of the provider’s API. Providers with unusual authentication or API patterns can take longer; we’ll give you a realistic timeline after reviewing their documentation.
What if a provider changes their API?
We monitor all integrated providers for API changes and handle updates automatically. Provider API maintenance is included in your Orchestra service – no action required from your development team.