FAQs
Frequently Asked Questions
Find answers to common questions about Corridorly's payment orchestration platform, from getting started to advanced integrations.
Getting Started
New to Corridorly? Start here
What is Corridorly?
How do I get started with Corridorly?
How long does implementation take?
Symphonies & Orchestration
Understanding workflow execution
What is a symphony?
What's the difference between marketplace and instance symphonies?
What happens if a symphony execution fails?
Payment Routing
Smart routing and provider selection
How does the smart router choose which payment provider to use?
Which payment providers are supported?
Can I customise routing logic or create my own rules?
API & Integration
Technical implementation questions
What programming languages and frameworks are supported?
What are the API rate limits?
How do I manage and rotate API keys?
How do I ensure requests are idempotent?
Security & Compliance
Data protection and regulatory compliance
How does Corridorly handle payment data?
How is my data secured?
Webhooks & Events
Real-time event notifications
How do I set up webhooks?
What webhook events are available?
What happens if my webhook endpoint is down?
Testing & Debugging
Troubleshooting and development
How do I test my integration before going live?
How do I debug failed symphony executions?
How long are execution logs retained?
Billing & Pricing
Costs and payment terms
How does Corridorly pricing work?
Does Corridorly charge transaction fees on top of provider fees?
Support & SLA
Help and service guarantees
What support channels are available?
What is Corridorly's uptime SLA?
What happens if there's a service incident?
Still have questions?
Can't find what you're looking for? Our support team is here to help.