How Orchestra Works

Orchestra is a payment orchestration layer that sits between your application and your payment providers. It provides a unified API while routing transactions to the providers you choose.

​

The Problem Orchestra Solves

Without Orchestra, integrating multiple payment providers means:

• Writing and maintaining separate integrations for each provider
• Handling different APIs, data formats, and authentication methods
• Building your own failover logic when a provider goes down
• Re-integrating when you want to add or switch providers

Orchestra handles all of this with a single integration.

​

Where Orchestra Fits

Your application makes API calls to Orchestra. Orchestra translates those calls to the appropriate provider format and routes the transaction.

​

What Orchestra Handles

​

Transaction Flow

​

Key Concepts

​

Payment Gateway Accounts

A Payment Gateway Account is your connection to a specific provider. You create one for each provider account you want to use:

• “stripeProduction” → Your Stripe live account
• “stripeTest” → Your Stripe test account
• “adyenBackup” → Your Adyen account for failover

When making API calls, you specify which account to use by name.

​

Tokens

Orchestra’s tokenization stores card details securely and gives you a token reference. Cards stored in Orchestra’s vault are provider-agnostic: a card tokenized with Orchestra can be charged through any of your gateways. A gateway token, issued by a PSP through gateway tokenization, works only with the PSP that issued it.

​

Routing

You control routing by specifying the paymentGatewayAccountName in each request. This lets you:

• Use different providers for different markets
• Route high-value transactions to preferred providers
• Implement A/B testing across providers

​

Sandbox vs Production

Sandbox and live are separate Orchestra accounts, chosen when you register: Sandbox transactions are simulated. No real money moves. The API behavior is identical to production.

​

Related Guides