Skip to main content
New to payment orchestration? Read Introduction to Payment Orchestration to understand how Orchestra works and whether it’s right for your integration.
Ready to start building? Follow the Quickstart to make your first API call in under 5 minutes.

​
Who Orchestra Is For

Orchestra is built for technology platforms that take payments for their own customers: vertical SaaS, booking and rental platforms, subscription and membership platforms, and commerce platforms. Each of your customers can bring its own payment provider. You store each customer’s provider credentials with us, and name the account to use on each transaction. When a customer asks for a provider we do not support yet, request the integration instead of building it yourself. See Serving Many Merchants. Orchestra also fits merchants who want a backup payment provider, and startups building for more than one market. Not a fit:
  • Holding or splitting funds. Orchestra never holds your money. Funds move directly between the payment provider and the merchant.
  • In-store card terminals. Orchestra handles online payments.
  • Cards that come from, or must go to, parties other than a payment provider, such as sending guest cards to hotels. Our sister product, PCI Booking, is built for that.

​
One Integration, Two Parts

1. Payments Library

JavaScript library that captures payment in your frontend: card entry, Google Pay, Apple Pay, and other APMs. Card data never touches your servers, so this is where you stay out of PCI scope.

2. REST API

Your backend’s interface for everything after capture: charges on stored tokens, authorize/capture, refunds, voids, recurring billing, and transaction status.
See how the Library and API work together.

​
What You Can Do

Process Payments

Accept cards, digital wallets, PayPal, and bank transfers. Authorize, capture, void, and refund through connected providers.

Store Payment Methods

Securely tokenize cards and digital wallets for repeat transactions without re-entering details.

Route Intelligently

Direct transactions to specific providers based on your business logic.

Failover Automatically

Configure backup providers to handle transactions when your primary fails.

​
How It Works

  1. Connect your payment providers - Add credentials for Stripe, Adyen, Worldpay, or any of our supported gateways
  2. Make API calls to Orchestra - Use a single, consistent API for all payment operations
  3. Orchestra routes to your providers - Transactions go to the gateway you specify (or failover to backups)
Need a payment gateway or method we don’t support? Request an integration - we add new providers at no cost.

​
AI Agent Integration

Building an AI agent or tool that needs to work with Orchestra? We publish machine-readable documentation following the llms.txt convention in two formats:

Introduction to Payment Orchestration

Understand what Orchestra does and how it works

Quickstart

Make your first charge in 5 minutes

API Reference

Full endpoint documentation

Get Help

Support channels and community