Composable Open-Source Payments Infrastructure

Hyperswitch offers a modular, open-source payments infrastructure designed for flexibility and control. Apart from our Payment Suite offering, this solution allows businesses to pick and integrate only the modules they need on top of their existing payment stack — without unnecessary complexity or vendor lock-in.

Each module is independent and purpose-built to optimize different aspects of payment processing.

Learn More About The Payment Modules

Quickstart

Local Setup via Docker

# One-click local setup

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

cd hyperswitch

scripts/setup.sh

Hosted Sandbox (No Setup Required)

Hyperswitch offers a fully hosted sandbox environment that requires no setup. You can explore the Control Center, configure payment connectors, and test payments directly from the UI.

Cloud Deployment

You can deploy to AWS, GCP, or Azure using Helm Charts.

Cloud Deployment Instructions.

Architectural Overview

Why Hyperswitch?

Hyperswitch is a commercial open-source payments stack purpose-built for scale, flexibility, and developer experience. Designed with a modular architecture, Hyperswitch lets you pick only the components you need—whether it’s routing, retries, vaulting, or observability—without vendor lock-in or bloated integrations.

Built in Rust for performance and reliability, Hyperswitch connects to Stripe, Adyen, Braintree, Worldpay, Checkout.com, Cybersource, and 120+ processors — exposing smart routing and retry logic, and provides a visual workflow builder in the Control Center. Whether you're integrating a full payment suite or augmenting an existing stack with a single module, Hyperswitch meets you where you are.

Common starting points: teams moving from a single Stripe/ Stripe connect or Braintree integration to multi-PSP routing, merchants replacing a payment gateway with direct acquirer connections to TSYS, JP Morgan Payments, or other acquirers, and merchants rearchitecting their payments platform through Hyperswitch while keeping their existing VGS, TokenEx or other existing vault intact.

“Linux for Payments” — Hyperswitch is a well-architected reference for teams who want to own their payments stack.

We believe in:

• Embracing Payment Diversity: Innovation comes from enabling choice—across payment methods, processors, and flows.

• Open Source by Default: Transparency drives trust and builds better, reusable software.

• Community-Driven Development: Our roadmap is shaped by real-world use cases and contributors.

• Systems-Level Engineering: We hold ourselves to a high bar for reliability, security, and performance.

• Maximizing Value Creation: For developers, customers, and partners alike.

• Community-Driven, Enterprise-Tested: Hyperswitch is built in the open with real-world feedback from developers and contributors, and maintained by Juspay, the team powering payment infrastructure for 400+ leading enterprises worldwide.

Supported Connectors

Hyperswitch integrates with 100+ payment processors out of the box. Each connector has a dedicated guide covering credentials setup, webhook configuration, supported payment methods, and common failure modes.

👉 Browse all available connectors →

Hyperswitch Ecosystem Mapping

Hyperswitch is built as a set of modular services and SDKs that work together. The Rust app server in this repo is the core, and the repositories below extend it with dashboards, client SDKs, and deployment tooling.

1. Core backend services

The Rust services that process payments. The app server is the center of gravity; the vault and encryption service handle sensitive-data operations alongside it. <code class="ra0-md-code">hyperswitch-prism</code> is a separate, lighter entry point: a unified connector library that can be used directly against payment processors without running the full switch. <code class="ra0-md-code">decision-engine</code> is another standalone service: a routing control plane that selects the best gateway per transaction and can run independently of any orchestrator.

2. Dashboard

Merchant-facing UIs for configuring connectors, routing, and viewing transactions. Both require the hyperswitch backend to be running.

3. Web checkout SDKs

How a browser talks to Hyperswitch. <code class="ra0-md-code">hyperswitch-client-core</code> is the shared core, pulled in as a git submodule by every client SDK (web and mobile). <code class="ra0-md-code">hyperswitch-sdk-utils</code> holds shared assets that merchants doing Headless Implementations consume directly.

4. Mobile SDKs

Native SDKs for embedding Hyperswitch checkout into mobile apps. All are built on top of <code class="ra0-md-code">hyperswitch-client-core</code>, pulled in as a git submodule.

> [!IMPORTANT]
> An older repo, hyperswitch-sdk-react-native, is being deprecated and has already been removed from npm. Use <code class="ra0-md-code">react-native-hyperswitch</code> instead.

5. Deployment & infrastructure

Tooling for running Hyperswitch, from local development through production.

Contributing

We welcome contributors from around the world to help build Hyperswitch. Whether you're fixing bugs, improving documentation, or adding new features, your help is appreciated.

Please read our contributing guidelines to get started.

Join the conversation on Slack or explore open issues on GitHub.

Feature requests & Bugs

For new product features, enhancements, roadmap discussions, or to share queries and ideas, visit our GitHub Discussions

For reporting a bug, please read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.

Versioning

Check the CHANGELOG.md file for details.

Copyright and License

This product is licensed under the Apache 2.0 License.