Feature
Schedule & recover payments. Through one API.
Define future and recurring charges, receive a result for every scheduled attempt, and recover eligible failures through your configured payment paths.
You set the date and time of a charge. When the time comes, Orchestra runs it and returns the result.
Payment schedules
Define the dates. Orchestra triggers the charges.
Create one-time future charges, fixed installments, or recurring payments. Orchestra runs each charge automatically.
Define the schedule once: one-time, installments or monthly. Orchestra triggers each charge on its date, and you see the result of every one.
Contract status
Check any plan’s progress.
Scheduled payments run in the background. Check a contract’s progress at any time through the API: status, payments taken so far, last payment date and next due date.
Fallback order
Set the provider order. We follow it.
Name a primary PSP and any ordered fallback list. After a failure, Orchestra moves down the list until one succeeds or the list is exhausted.
If the primary provider fails, Orchestra moves to the next provider in your order. It stops at the first approval.
After an insufficient funds decline, a partner model picks the retry time with the best chance of funds being there. On some transactions, the payment can also be guaranteed.
Insufficient funds
Retry at a better time.
For eligible transactions, a partner model selects the retry time with the highest likelihood of available funds.
Some eligible transactions may also be guaranteed.
Teams that bill on a schedule
SaaS portfolio
Rebilling rules and timing are configured once and Orchestra runs the charges on schedule. Stored cards work with a new processor immediately, with no re-collection from subscribers.
Healthcare SaaS
Automated monthly billing for medical practices across currencies and payment methods, with failover to a backup processor when the primary one is down.
Invoicing platform
Recurring invoices charge cards stored in Orchestra’s token vault, on schedules the platform defines, through the processor it specifies.
Build it
Create a contract. Orchestra runs the schedule.
Tokenize the card once, then create a payment contract against a schedule template. Pause, resume, update or cancel it through the API.
curl -X POST https://api.orchestrasolutions.com/PaymentContract \
-H "Content-Type: application/json" \
-H "X-Api-Key: YOUR_API_KEY" \
-d '{
"templateId": "tmpl_monthly_standard",
"name": "Acme Corp monthly plan",
"tokenId": "token-from-previous-step",
"startDate": "2026-11-01",
"maxOccurrences": 12,
"chargeRequestData": {
"amount": 29.00,
"currency": "EUR",
"myRef": "sub-4821",
"orderDesc": "Standard plan, monthly",
"cardHolderName": "Jane Smith",
"expirationMonth": 12,
"expirationYear": 2027
}
}'Create a 12-payment monthly contract. From the scheduled payments guide.
Go deeper on recurring payments
More from the same API.
Related on this site
Test the lifecycle
Create a schedule. Test every result.
100 live requests every month, plus unlimited sandbox testing. No credit card required.
Sandbox unlimited testing | Live 100 requests / month