Skip to main content
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 App       │
└────────┬────────┘
         │
         ▼
┌─────────────────┐
│  Orchestra API  │  ← Single integration point
└────────┬────────┘
         │
    ┌────┴────┐
    ▼         ▼
┌───────┐ ┌───────┐
│ Stripe│ │ Adyen │  ← Your connected providers
└───────┘ └───────┘
Your application makes API calls to Orchestra. Orchestra translates those calls to the appropriate provider format and routes the transaction.

​
What Orchestra Handles

Orchestra DoesYou Handle
Provider API translationBusiness logic (what to charge, when)
Credential managementCustomer data (accounts, orders)
Transaction routingUser interface
Token storageCompliance for your stored data
Failover executionProvider account setup

​
Transaction Flow

1

You make an API call

Your server sends a charge request to Orchestra with the amount, currency, and payment details.
2

Orchestra routes the transaction

Based on the paymentGatewayAccountName you specify, Orchestra sends the transaction to the appropriate provider.
3

Provider processes the payment

Stripe, Adyen, or whichever provider you specified processes the transaction with the card network and issuing bank.
4

Orchestra returns the result

You receive a standardized response with the transaction ID and status.

​
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:
  • “stripe-production” → Your Stripe live account
  • “stripe-test” → Your Stripe test account
  • “adyen-backup” → 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. Tokens are provider-agnostic—a card tokenized while routing through Stripe can later be charged through Adyen.

​
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

Orchestra provides both environments:
EnvironmentUseProvider Mode
SandboxDevelopment, testingConnect to provider test/sandbox accounts
ProductionLive transactionsConnect to provider live accounts
Sandbox transactions are simulated—no real money moves. The API behavior is identical to production.
Use separate API keys and Payment Gateway Accounts for sandbox and production. Don’t mix test credentials with live ones.

​
Next Steps

Architecture

Technical architecture details

Quickstart

Make your first API call