Orchestra’s integration has two parts that work together. The Library captures payment in your checkout, so cardholder data never touches your servers. The API is what your backend calls after capture: charging stored tokens, refunds, captures, recurring billing. You are not choosing between them; most customers use both.
One integration, two working parts
Orchestra API
Orchestra API is a REST API for everything that happens after capture. Your backend sends transaction requests in our standardized format, we handle gateway-specific requirements, and you get consistent JSON responses regardless of which gateway processes the payment. Charge a stored token, capture an authorization, issue a refund, run recurring billing: all without your systems ever handling card details.
Orchestra Library
Orchestra Library is where payment is captured. Pre-built UI components handle card entry, digital wallets, and alternative payment methods in your checkout, with built-in 3D Secure and OTP authentication. Payment data travels from your customer to Orchestra and never touches your servers, keeping your business outside PCI-DSS scope.
Who does what
| Orchestra Library | Orchestra API | |
|---|---|---|
| Where it runs | In your checkout, client-side | From your backend, platform, or serverless environment |
| Role | Captures payment: cards, digital wallets, regional methods | Acts on captured payments: charges, captures, refunds, voids, recurring billing |
| Card data exposure | Travels from your customer to Orchestra; never touches your servers | Operates on stored tokens; no raw card needs to touch your systems |
| PCI DSS scope | Keeps your business out of scope | Adds none when charging stored tokens |
| 3D Secure/OTP | ✓ Built-in at capture | Handled at capture, carried through |
| Tokenization | ✓ Creates tokens (Orchestra or gateway) | ✓ Charges stored tokens |
| Gateway Failover | ✓ Automatic | ✓ Automatic |
| Gateway and Method Additions | No additional cost | No additional cost |
How they fit into your stack
Use the Orchestra API to:
- Charge stored tokens for recurring and subscription billing
- Capture, refund, or void transactions from your backend
- Run server-to-server flows such as no-show fees or delayed charges
Use the Orchestra Library to:
- Capture cards, wallets, and regional payment methods in your checkout
- Keep cardholder data off your servers and stay out of PCI DSS scope
- Handle 3D Secure and OTP authentication without building it
- Tokenize payment details for later charges through the API
The Library and the API share the same routing, failover, and gateway connections, and new gateways are added at no additional cost. A card stored in Orchestra’s vault is not tied to any one processor: a later charge can go through a different connected gateway. A card tokenized into a gateway’s own vault stays with that gateway. A typical setup captures payment once through the Library and runs everything after that through the API.
Free to start • No credit card required