Hyperswitch is an open-source payment switch from Juspay that sits between a business and its payment processors. It connects one integration to more than 270 processors and acquirers across 50-plus countries, then routes each transaction, vaults the card data, and reconciles the money behind a single API, serving merchants and platforms that want that payment logic under their own control.[1]
Quick verdict
Merchants operating across several processors or countries will get the most from Hyperswitch, because its switch routes each payment, retries declines, and unifies vault, 3DS, reconciliation, and payouts behind one integration. The price of that independence is engineering ownership: production setup runs through APIs, SDKs, and self-hosted infrastructure. Managed tiers are quote-based rather than a published monthly figure, and Hyperswitch never settles money itself. If you can own payments as code under Apache-2.0, choose Hyperswitch; if onboarding must stay developer-light, evaluate a hosted proprietary orchestrator outside this catalogue instead.[1][2][3]
Key features
One integration reaching 270-plus processors: a single API and SDK set connects processors and acquirers across 50-plus countries, so adding or dropping a provider does not mean another bespoke integration project.[1][2]
Volume, rule-based, and surge routing: traffic splits by configured volumes, routes by programmable rules such as amount or currency, and shifts automatically during processor outages.[1]
Vault with network tokens and external-vault support: card data is tokenized with scheme network tokens and auth-native flows, card-on-file stays usable across processors, and teams can also plug in an external vault.[1][2]
3DS decisioning with the Authletics toolkit: step-up authentication is applied selectively through a 3DS decision manager instead of challenging every transaction.[1]
Fraud guard experiments and intelligent retries: a Featurespace-powered fraud screen runs alongside payment experiments, while failed payments are retried intelligently to recover revenue.[1]
Cost observability and reconciliation: processing costs are broken down across the processor mix, and settlement reports are standardized into unified reconciliation, including payouts reconciliation.[1]
Full payout operations including split payments: payouts can be triggered, synced, scheduled, and routed, with split payments for marketplaces dividing one intake across sellers.[1]
Platform controls with SDKs in thirteen languages: multi-entity management, merchant onboarding SDKs, multi-currency support, a white-label theme, payment links and invoices, and a no-code orchestration builder on SDKs spanning Rust, Java, Python, NodeJS, Go, Ruby, C#, PHP, Elixir, iOS, Android, React, and Flutter.[1][2]
Who will love it
High-volume merchants spread across processors and countries: one integration plus routing, retries, and cost observability serves teams losing revenue to single-processor failures or opaque cross-border fees.[1]
Teams that must keep card data in their own infrastructure: the Apache-2.0 Standard edition self-hosts on a team's own cloud, with a PCI DSS 4.0 audited scope for card data and ISO 27001 stated.[1][2][3]
Platforms and marketplaces splitting money across sellers: split payments, multi-entity management, onboarding SDKs, and white-labelling match operators running payments for many sub-merchants.[1]
Who should avoid it
Teams without developers to spare: production integration runs through the unified API, SDKs, webhooks, and self-hosted deployment; the no-code builder covers orchestration workflows, not the whole implementation.[1][2]
Buyers needing a published monthly managed price today: the self-hosted edition is free open source, but managed tiers are quote-based with volume routing caps rather than a published per-month figure.[1]
Teams wanting a built-in payment processor: Hyperswitch orchestrates third-party processors and does not settle money itself, so at least one processor contract is still required.[1]
Alternatives and compatibility
No payment-orchestrator incumbent is published in this catalogue; Stripe, Adyen, and Primer have no records to verify against, so no supported relationship edge is proposed and catalogue publication stays blocked on that gate.[1]
Portability facts: the open-source core is Apache-2.0 with 25.4k stars and 207 contributors, a Docker-based setup documents the self-host path, and the same platform also runs as Juspay-hosted SaaS.[1]
If you run payments across several processors or countries and can staff the integration, choose Hyperswitch for its open-source switch, routing depth, and self-hosted data control; if onboarding must stay developer-light or pricing must be a published monthly figure, choose a hosted proprietary orchestrator instead.[1][2]
Questions worth asking
What is the best Hyperswitch alternative for non-technical users?
There is no evidenced simpler alternative inside this catalogue yet: Stripe, Adyen, and Primer have no catalogue records to verify against. A non-technical team should evaluate a hosted proprietary orchestrator outside the catalogue, or the Juspay-hosted Hyperswitch tier where onboarding support replaces self-hosting effort.[1][2]
Is Hyperswitch really no-code?
How much does Hyperswitch cost per month?
The open-source codebase is free to self-host under Apache-2.0 with no licence fee. Managed tiers are quote-based rather than published monthly figures, with volume routing caps at 1M, 5M, and custom levels across the three tiers. Processor fees apply separately at whatever providers are connected. Prices checked October 11, 2026.[1][2]
Sources and editorial review
Source research. Reviewed on October 11, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Hyperswitch official site
official · Observed October 11, 2026
Official homepage: open-source payments switch scope, 270+ processors, routing, vault, 3DS, fraud guard, retries, cost observability, reconciliation, payouts, no-code builder, SDKs, self-host vs SaaS, PCI DSS 4.0 and ISO 27001.
- Hyperswitch repository (official)
official · Observed October 11, 2026
Official repository: open-source payments switch in Rust (78.8%), Apache-2.0, 25.4k stars, 207 contributors, 1.2k forks, router and control center, unified API, connector directory, late-September 2026 release, PCI DSS v4.0.1 audited scope.
- Hyperswitch documentation hub
official · Observed October 11, 2026
Official documentation hub: unified API and thirteen-language SDKs, routing, vault/tokenization, 3DS, fraud guard, reconciliation, payouts, platform multi-entity/onboarding/split features, observability, quickstart, connector reference.
- Hyperswitch pricing
official · Observed October 11, 2026
Official pricing: three tiers across self-hosted Standard and Juspay-hosted options, 1M/5M/custom volume routing caps, community-to-KAM support ladder, quote-based managed pricing, PCI DSS 4.0 and ISO 27001 stated.
Compared with these products
No explicit proprietary baseline is recorded.