Payment orchestration,
not a payment gateway.
OpenSwitch is a live payment orchestration platform for online merchants and marketplaces. Route payments across the providers you already use, manage fallback policies, and keep control of your payment strategy.
The control layer between your app and your providers
OpenSwitch sits between your checkout or marketplace payment flow and your connected providers. It applies configured routing and fallback policies while giving your team a consistent operational view.
Build only against verified interfaces
The public reference currently documents the implemented service health endpoint. Buyer payment APIs, authentication, events, SDKs, test environments, and support inventory will be published only after their contracts are approved.
- Verified endpoint paths and response schemas
- Clear publication status for unavailable interfaces
- No implied SDK, sandbox, or connector support
- Approved contracts replace examples before implementation
GET /api/healthzUnauthenticated health check returning {"status":"ok"}.
What the orchestration layer provides
Smart Routing
Apply routing policies across connected providers using factors such as geography, payment context, provider performance, and commercial priorities.
Failover & Retries
Configure fallback behavior for eligible failures so payment traffic is not dependent on a single provider.
Unified API
Use a consistent orchestration layer across supported providers, reducing provider-specific logic in your application.
Full Observability
Review payment and routing activity to understand how connected providers perform for your transaction mix.
Vendor Independence
Keep routing decisions under your control and reduce operational dependence on any one payment provider.
Connector Library
Connect supported payment providers based on your markets and payment needs. Available connectors are confirmed during solution design.
Gateway vs PSP vs Orchestration
Payment gateways abstract a single provider. PSPs process payments directly. OpenSwitch is neither — it's the routing and reliability layer that connects your application to multiple providers simultaneously.
| Capability | Gateway (Stripe, Paymob) | PSP | OpenSwitch |
|---|---|---|---|
| Abstraction layer | Single provider | Single provider | Multi-provider orchestration |
| Routing logic | None | None | Cost / success rate / geo rules |
| Failover | None | None | Automatic, configurable chains |
| Retry engine | None | None | Intelligent with decline analysis |
| Observability | Basic | Basic | Per-connector, full lifecycle |
| Vendor lock-in | Yes | Yes | None by design |
| You own the logic | No | No | Yes |
Connect the providers that fit your business
No public connector or payment-method inventory is currently approved. Support is confirmed in writing for each buyer and will be published here only after approval.
Build a payment strategy around your business.
Tell us about your payment volume, providers, markets, and integration needs. We’ll map where orchestration can add control and resilience.