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.
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.
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
- Connect your payment providers - Add credentials for Stripe, Adyen, Worldpay, or any of our supported gateways
- Make API calls to Orchestra - Use a single, consistent API for all payment operations
- Orchestra routes to your providers - Transactions go to the gateway you specify (or failover to backups)
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:Quick Links
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