Integration Request
Don’t See Your Payment Provider? We’ll Add It.
Orchestra adds new integrations based on customer demand. Submit your request and we’ll evaluate feasibility and provide a timeline.
No integration fees or additional cost • 2-4 week timeline
We Build What You Need
Payment landscapes evolve rapidly. New providers launch in emerging markets, existing providers add payment methods, and regulatory changes create opportunities for specialized processors.
Rather than limit Orchestra to a fixed provider list, we continuously expand based on real customer needs. This approach ensures you never have to compromise your market expansion plans due to payment infrastructure limitations.
How Integration Requests Work
Request Submission
Complete the form below with provider details, your business case, and technical requirements. Include API documentation if available.
Technical Evaluation
Our engineering team reviews the provider’s API, authentication methods, and compliance requirements. We identify any technical constraints or special considerations.
Development & Testing
We build the integration in our staging environment, test all payment flows, and verify webhook reliability. This typically takes 2-4 weeks for standard REST APIs.
Production Deployment
The integration becomes available to you automatically. No code changes required on your end – you’ll receive notification when it’s ready to use.
Request Form
What We Need to Evaluate Your Request
Provider name and region – Official company name and primary markets
Payment methods supported – Cards, bank transfers, wallets, alternative methods
Technical details – API documentation, webhook specifications, authentication methods
Timeline requirements – When you need this integration live
Technical Details
Orchestra maintains consistent standards across all payment provider integrations
Our Integration Architecture
Unified Transaction Handling: Unified transaction handling including all communication, encryption and signature verification done in the background. Payment status updates, refund notifications, and other transaction operations follow the same format regardless of provider.
Unified Response Format: All provider integrations return identical JSON structures, regardless of the provider’s native API format. This eliminates provider-specific code in your implementation.
Standardized Error Handling: HTTP status codes, error messages, and retry logic work consistently across all providers. Your error handling code doesn’t change when you add new providers.
Security Consistency: All providers use the same authentication flow through Orchestra, even if they have different native authentication methods.
What We Can’t Integrate
Some limitations exist based on technical or business constraints:
- Lack programmatic APIs – Providers that support only their built-in forms or do not offer APIs to pass card details
- Require proprietary hardware – Systems dependent on specific terminals, card readers, or point-of-sale devices
- Have geographic restrictions – Providers that won’t work with our infrastructure location or compliance framework
If your provider falls into these categories, we’ll suggest alternative approaches or compatible providers.
Frequently Asked Questions
Common Questions About Integration Requests
How long do new integrations take?
Most standard payment providers can be integrated within 2-4 weeks. Complex providers with unique authentication or unusual API patterns may take 4-6 weeks. We’ll give you a realistic timeline after reviewing their documentation.
Do you charge for custom integrations?
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.
Do you work directly with the payment provider?
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.
What if a provider changes their API?
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.
What information do you need to integrate with a new payment provider?
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.
Can you integrate providers that require pre-approval?
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.
Do integrations work with both Orchestra API and Library?
Most integrations support both implementation methods. However, some providers with complex authentication flows may initially launch with API-only support, with Library support added later. For the differences between the two here: API vs Library.
What happens if a provider integration breaks?
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.
Ready to Expand Your Payment Options?
Submit your integration request and we’ll respond within 2 business days with a feasibility assessment and a development timeline.