OpenSwitch

OpenSwitch is a payment-orchestration API for teams that operate with more than one payment service provider (PSP). It suits fintechs, marketplaces and SaaS businesses that need shared payment operations rather than another processor. Its strongest case is flexible routing and recovery across PSPs, while teams wanting fund custody or a conventional checkout processor should look elsewhere.

Overview

OpenSwitch puts payments, refunds, disputes, mandates and webhooks behind one common API schema across enabled connectors. That reduces the need to maintain separate PSP integrations and gives operations teams one place to apply routing and inspect outcomes. It remains an orchestration layer: the PSPs process transactions, and settlement goes directly between those PSPs and customers’ bank accounts. Businesses seeking a service that receives or holds funds will need a different product.

Key features

Routing, retries and failover

Rules can choose a connector by cost, authorization success rate, currency, card BIN, geography or a custom expression. Configurable retry policies and fallback chains can reroute soft declines. This is useful when a business has meaningful volume across providers and wants to tune approval rates or cost; it is more infrastructure than a small merchant with one PSP needs.

Unified API and vault

The shared schema covers core payment operations, so applications can keep one integration while connector choices change underneath. OpenSwitch also describes a network-token-aware vault whose tokens can be moved between PSPs that the customer controls. That portability can reduce dependence on one provider, but it does not remove the need to manage those PSP relationships and credentials.

Observability and connectors

Per-connector latency, authorization rates and decline reasons help teams identify where payment performance is being lost. Events can be exported through webhooks or S3 for downstream analysis. The connector directory lists 18 integrations, including Stripe, Adyen, Checkout.com, Braintree, Paymob, Klarna, PayPal and Razorpay. OpenSwitch says its connector framework is inherited from Hyperswitch, with new connectors added through a connector trait, which favors engineering teams able to extend the system themselves.

Developer and security controls

Documentation covers REST and JSON, an npm SDK, a Docker image and a self-hosted Rust binary. Requests use bearer keys with restricted scopes, while webhooks are HMAC-signed and protected against replay. Enterprise adds mTLS and a SOC 2 / PCI evidence pack. These controls are a sensible baseline for payment infrastructure, but the higher-assurance options sit behind the Enterprise tier.

Pricing

Open Source is the practical choice for teams with the capacity to run infrastructure and accept community support; unlimited transactions remove a usage ceiling, but hosting and operational work remain yours. Cloud shifts that work to OpenSwitch and adds a stated SLA and managed upgrades, making it better for teams that prefer a hosted control plane. Its charge is tied to orchestrated requests and starts at volume tiers from 1M requests per month, so high-throughput buyers should model request volume carefully. Enterprise is for organizations requiring isolated deployment, bespoke connectors, contractual SLAs and dedicated response; its annual contract and custom pricing make it unsuitable for a small or exploratory implementation.

Platforms

OpenSwitch is offered through an API and as self-hosted software. The developer materials provide Docker and a Rust binary, while the npm SDK supports JavaScript-based clients. There is no listed native mobile or browser application.

Who it's for

Fintechs, marketplaces and SaaS teams coordinating several PSPs are the natural audience. Routing by geography or currency can support varied payment footprints, and marketplace payouts, recurring payments and tokenization are supported capabilities. A company using one PSP with straightforward payment flows will gain less from the orchestration layer and may prefer a direct PSP integration.

Pros and cons

Pros

• Rules based on cost, performance, payment data and geography give multi-PSP teams precise control over traffic.
• Retries and fallback chains provide a defined response to soft declines instead of forcing every application to build its own recovery logic.
• One API spans payments, refunds, disputes, mandates and webhooks, with portable vault tokens across customer-controlled PSPs.
• Self-hosted Open Source supports unlimited transactions and the connector framework can be extended.

Cons

• It does not custody or settle funds, so it cannot replace a processor or acquiring relationship.
• Self-hosting requires the team to operate the system, while community support is the only support tier on Open Source.
• Enterprise-only isolation, custom connectors, contractual SLAs and 24/7 support raise the bar for regulated or mission-critical deployments.
• Cloud billing is based on orchestrated requests, which may complicate forecasting for very high-volume traffic.

Alternatives

Choose Payment Orchestration Platforms to compare the wider category. Juspay Hyperswitch is worth considering if you want 90+ integrations and self-managed hosting with a free community edition across API, web and mobile platforms. PayOrc fits a smaller operation that can start with one PSP and a free tier capped at USD 5k monthly TPV, then move to its USD 25.00-per-month Growth plan for up to USD 100k and five PSPs. BridgerPay suits teams wanting a web-based option with a free-forever plan limited to 200 transactions per month, one user, one checkout and two connections. Orchestra is a better fit when the immediate need is sandbox testing, with unlimited test transactions and 130+ provider sandboxes. PayServ Multi-PSP Platform offers a free test environment with one PSP sandbox connection and 500 test transactions per month. BR-DGE, CellPoint Digital and MoneyHash are paid alternatives for teams evaluating other multi-platform payment products.

Verdict

Choose OpenSwitch when your engineering team needs one programmable layer over several PSPs, with rule-based routing, retry recovery and connector-level visibility. Its free self-hosted plan and broad API make it especially compelling for technically capable fintech, marketplace and SaaS operators. Look elsewhere if you need the platform to hold or settle money, a turnkey single-PSP checkout, or enterprise isolation and dedicated support without an annual custom contract.