Hyperswitch Review

Hyperswitch is described as a commercial open-source payments stack with a modular architecture, so you can adopt only the pieces you need. The README lists six modules: Cost Observability (audit and optimize payment costs, spot hidden fees and downgrades), Revenue Recovery (retry strategies tuned by card BIN, region, and method to fight passive churn), Vault (a PCI-compliant store for cards, tokens, wallets, and bank credentials, with bring-your-own-vault support for providers such as VGS and TokenEx), Intelligent Routing (route each transaction across Stripe, Adyen, Braintree, Worldpay, Checkout.com, and 120+ others to the processor with the highest predicted authorization rate), Reconciliation (2-way and 3-way with backdated support), and Alternate Payment Methods (drop-in widgets for PayPal, Apple Pay, Google Pay, Samsung Pay, Pay by Bank, and BNPL such as Klarna). A visual workflow builder lives in the Control Center. The core is built in Rust and licensed Apache-2.0.

The README offers a one-click local setup: clone the repository at the latest branch with --depth 1 and run scripts/setup.sh, which detects Docker or Podman and offers Standard (app server and Control Center), Full (adds monitoring and schedulers), and Minimal (app server only) profiles, then prints access links. After that you configure a payment connector in the Control Center and test a payment. For production, Helm charts support AWS, GCP, or Azure, and a hosted sandbox exists for exploring the Control Center without setup. Moving real card traffic through a self-hosted stack involves PCI scope and operational responsibility the README does not minimize, so treat it as infrastructure work.

Day-to-day use happens in the Control Center, where you add connectors, view logs, define routing rules and retry strategies, and try payments from the UI. Developers integrate through APIs and SDK-style drop-in widgets. This is based on the README and docs links; we did not run test payments.

• Intelligent routing across 120+ processors
• Revenue recovery with configurable retry logic
• PCI-compliant vault with bring-your-own-vault option
• Cost observability and reconciliation
• Drop-in widgets for wallets, bank payments, and BNPL
• Visual workflow builder and Control Center

• Avoids lock-in to a single processor by design
• Modules are independent, so you can add routing or retries without replacing your stack
• Performance-oriented Rust core with a permissive license
• Very active repository, about 45,300 stars

• It is not a processor, so you still need merchant accounts with each connector
• PCI compliance and security are your problem when self-hosting
• The README is written by the vendor and describes capabilities rather than limits or pricing
• Complexity is high for small businesses with a single gateway

Self-hosting is free under Apache-2.0. The README mentions a hosted sandbox and Juspay's managed offering but does not publish prices, so we cannot state a cost for the managed product.

Stripe is a processor and full payments platform with a polished developer experience, fraud tools, and billing, all hosted. Hyperswitch does not replace the processor; it orchestrates multiple processors, including Stripe, and keeps the routing logic and vault under your control. It makes sense at the scale where cost, redundancy, and authorization rates matter.

• Businesses that already use several payment processors
• Teams that want to reduce processor lock-in and optimize authorization rates
• Engineering organizations able to carry PCI responsibilities

• Early-stage startups with a single Stripe integration
• Teams without payments or compliance expertise
• Anyone expecting a turnkey replacement for Stripe's billing and tax products