What it is

Hyperswitch is an open-source, composable payments infrastructure built in Rust for managing global payment transactions. It operates as a modular platform that abstracts and unifies interactions with multiple payment, payout, fraud, vault, and tokenization providers—including Stripe, Adyen, Braintree, Worldpay, and Checkout.com—while supporting over 120 payment service providers. It lives in the fintech ecosystem and is licensed under Apache-2.0.

Hyperswitch solves the fragmentation and vendor lock-in inherent in traditional payment stacks by decoupling core functions—such as routing, vaulting, reconciliation, and observability—into independent, replaceable modules. This allows businesses to adopt only the capabilities they need, integrate with existing systems, and avoid costly migrations. It also replaces proprietary SaaS tools for cost analytics, revenue recovery, and reconciliation with open-source equivalents.

Key capabilities

• Intelligent routing to select the optimal payment service provider per transaction based on predicted authorization rates, region, card BIN, and method
• PCI-compliant vault service for storing cards, tokens, wallets, and bank credentials, with support for bring-your-own-vault integrations (e.g., VGS, TokenEx)
• Cost observability dashboards to audit, monitor, and optimize payment fees, detect hidden charges, and analyze downgrades
• Revenue recovery system using configurable retry strategies tuned to BIN, region, payment method, and penalty budgets
• Reconciliation engine supporting 2-way and 3-way matching with backdated processing and customizable output formats
• Drop-in widgets for alternate payment methods including PayPal, Apple Pay, Google Pay, Samsung Pay, Pay by Bank, and BNPL providers like Klarna
• Control Center UI for configuring connectors, managing environments, and testing payments without code changes

Who uses it and how

• Payment processors and acquirers embed Hyperswitch to offer unified APIs to merchants while retaining control over routing logic and connector selection
• Fintechs and SaaS platforms integrate Hyperswitch modules (e.g., vault, routing) into their existing stacks to reduce reliance on multiple point solutions
• Enterprises with complex multi-connector setups use reconciliation and observability modules to automate operations and reduce manual effort in audit and cost tracking

Getting started

Deploy locally using Docker via git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch && cd hyperswitch && scripts/setup.sh, which supports Standard, Full, and Minimal deployment profiles. A fully hosted sandbox environment is available at no setup cost for testing and exploration.

When to use it — and when not to

Hyperswitch replaces paid SaaS tools for routing, vaulting, and reconciliation but requires self-hosting infrastructure (PostgreSQL, Redis, S3-compatible storage, and optionally SMTP) for full functionality. It trades simplicity for flexibility—ideal when fine-grained control over payment logic is needed—but adds operational overhead compared to fully managed gateways. Avoid if you require out-of-the-box fraud detection or need to avoid infrastructure management entirely.

# One-click local setup

git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch

cd hyperswitch

scripts/setup.sh