Get the answers to your pressing questions about Orchestra Solutions, and explore our glossary of key payment industry terms.
Yes. Pre-authorize before handover, then capture the rental amount and supported adjustments at return. Availability depends on provider support and authorization windows.
Using a payment processor is simple with Orchestra. You’ll have complete flexibility to customize how payments flow. Start by choosing your processor, set up validation rules, and link your business account. The process ensures your payment journeys are optimized while integrating seamlessly with your existing systems. For requesting the addition of a new payment processor to our list of supported processors, see the related FAQ below.
Yes. Select the property configuration for each transaction while your PMS keeps the same integration.
Yes. Your platform can select the merchant’s configured provider and merchant account for each transaction.
Yes. Keep one integration contract and apply client-specific provider and merchant configuration per project.
No. Start with one provider and keep the same Orchestra integration as requirements expand.
Supported providers can capture the required amount and release the remainder within their authorization rules.
Yes. Map each customer to the provider and merchant account they already use. Your product sends the same payment operation and receives one normalized response.
Yes. Each client project supplies its own provider and merchant account configuration, while the shared payment module stays the same.
Yes. Connect the merchant’s own provider account. Your platform keeps the same request and response contract.
Yes. The embedded form sends card data directly to Orchestra. Your PMS receives a reusable token for deposits, balances and supported later charges, and raw card data does not reach your servers.
Nothing in the payment integration. A new market changes the customer configuration; your product keeps sending the same payment operation and receiving the same normalized response.
Yes. Schedule the balance as a future charge on the stored token. Availability depends on the selected provider and payment method.
Where it is available and the merchant is eligible. Availability depends on market, merchant eligibility and configuration.
In Orchestra. Orchestra maintains provider credentials and tokens, so they stay outside your reusable payment core.
Yes. Create future or recurring charges, then update the schedule when a rental is extended, shortened or cancelled. Scheduling availability depends on provider and payment method support.
Absolutely not; we don’t touch your funds. Your customers’ money flows directly from them to the payment gateway you used and from there to the settlement account defined with the gateway. We focus on facilitating and securing your transactions, leaving the financial handling to your payment providers.
Orchestra retries each provider in your ordered fallback list until the payment succeeds or the list is exhausted.
Only that client’s configuration. The shared module keeps the same request and response contract.
Send an integration request. New integrations are added in under two weeks, at no cost, after a feasibility review.
Yes. Void the authorization when a rental is cancelled, or refund supported amounts after return, through the same API.
Send an integration request. New integrations are added in under two weeks, at no cost, after a feasibility review.
We support all currencies offered by the payment gateways integrated with our platform. If your gateway can handle it, Orchestra can, too. Multi-currency support has never been easier to manage.
Security is at the heart of what we do. We abide by all the major payment compliance frameworks. By offloading security concerns to us, you’ll stay protected without compromising on ease of use.
Of course. Whether you’re looking to replace an existing processor or add more options, Orchestra makes switching effortless. With our platform, you can test new gateways or payment methods without disrupting your current systems.
Yes. On each transaction your application chooses the payment provider, the merchant account and an ordered list of fallback providers, using whatever rules you like: transaction type, currency, the customer’s country or cost. Orchestra carries out that choice and works down the fallback list until a provider succeeds.
New integrations you request are added in under two weeks, at no cost, after a feasibility review of the provider’s API. Providers with unusual authentication or API patterns can take longer; we’ll give you a realistic timeline after reviewing their documentation.
No. New integrations are added to Orchestra at no additional cost. This includes development time, testing, and ongoing maintenance. You pay the same per-transaction rates regardless of which providers you use.
For technical integration, we work with publicly available APIs and documentation. For business relationships (negotiating rates, account setup), you’ll work directly with the provider. We can provide technical guidance for these conversations.
We monitor all integrated providers for API changes and handle updates automatically. Provider API maintenance is included in your Orchestra service – no action required from your development team.
We work with publicly available API documentation. For providers with private or partner-only APIs, you’ll need to facilitate introductions or provide access credentials for development.
Yes, but you’ll need to complete the provider’s application process independently. We can provide technical guidance for these applications, but business relationships are between you and the provider.
We monitor all integrations continuously and handle maintenance automatically. If a provider changes their API unexpectedly, we implement fixes and deploy updates without requiring changes to your code.
Any transaction call sent through the Orchestra API or Library, including authorizations, captures and refunds, whichever of the 130+ connected providers handles it.
New live transactions need Growth ($350/month + $0.03/request) once you pass 100 live requests a month on Starter.
No. Growth is billed monthly with no minimum contract. Start, scale or cancel as your volume changes.
Stored data is included for 3 months. After that, a monthly storage fee applies, depending on your volume. Contact sales for exact figures.
No. Sandbox and live are separate accounts. You choose the account type when you register, and it can’t be changed later: register a Sandbox account to build and test, then a separate live account when you go live.
Not for testing: the sandbox’s mock gateways need no merchant account. To process live payments, you need a merchant account with each provider you use. Your merchants can keep their own accounts with the payment providers they already use, and Orchestra connects to them through one API. Or Orchestra can onboard them to its white-label processing for cards, Apple Pay and Google Pay. PayPal and UPI merchants sign up with PayPal or UPI directly.
Yes. Routing is part of each request: your application sends the provider, the merchant account and the fallback order with every transaction. Change the logic that builds the request and the next transaction follows it, with no change on Orchestra’s side.
Run a transaction through Orchestra’s sandbox, or talk to us about your current processor setup.
Free to start • No credit card required