At a Glance:
Hyperswitch is a modular, open-source payments infrastructure platform that enables businesses to independently adopt components for cost observability, revenue recovery, intelligent routing across 120+ processors, and PCI-compliant vaulting on top of existing payment stacks.
Overview:
Hyperswitch is a composable, open-source payments infrastructure built for businesses seeking modular control over their payment operations. It allows users to integrate independent modules—such as intelligent routing, automated reconciliation, and revenue recovery—directly into an existing payment stack without requiring a full platform migration. The system is built in Rust, connects with over 120 payment processors including Stripe, Adyen, and Braintree, and can be deployed locally via Docker or on cloud platforms using Helm charts. It is designed for developers and payments teams who need to optimize authorization rates, audit processing costs, and manage sensitive payment credentials through a unified vault while maintaining existing processor relationships.
Key Decision Points:
Modular integration model: Developers can adopt individual payment modules like routing or vaulting independently, working alongside existing processors such as Stripe or Braintree without a full stack replacement.
Multi-processor routing: A rules-based intelligent routing engine distributes transactions across 120+ supported gateways and acquirers to optimize authorization rates and reduce latency.
Self-hosted or cloud deployment: The platform runs locally via a Docker-based setup script with multiple profiles (Standard, Full, Minimal) or can be deployed to AWS, GCP, or Azure using provided Helm charts.
Existing vault compatibility: The vault module supports a bring-your-own-vault model that connects to current providers like VGS and TokenEx without requiring card data re-tokenization or migration.
Core Features:
Intelligent routing: Routes transactions across a network of 120+ processors based on predicted authorization rates, with controls for minimizing retries and latency.
Cost observability: Provides dashboards and tools to audit payment costs, detect hidden fees, and identify downgrades or penalties.
Revenue recovery: Implements card BIN, region, and method-tuned retry strategies with configurable penalty budgets and retry logic to reduce passive churn.
PCI-compliant vault: A secure service for storing cards, tokens, wallets, and bank credentials, with optional connection to existing vault providers.
Automated reconciliation: Supports configurable 2-way and 3-way reconciliation with backdated and staggered scheduling options.
Web and mobile SDKs: Offers a React-based web checkout SDK and native SDKs for Android, iOS, React Native, and Flutter, all sharing a common client core.
Use Cases:
Developers integrating payment routing intelligence on top of an existing Stripe or Braintree integration to improve authorization rates across multiple processors.
Merchants replacing a single payment gateway with direct connections to acquirers like TSYS or JP Morgan Payments while retaining their current vault provider.
Payments teams auditing processor fees and downgrade penalties through a self-serve cost observability dashboard.
Mobile application developers embedding a unified checkout experience using native SDKs for Android or iOS that connect to the Hyperswitch backend.
Open-Source Alternative Value:
Hyperswitch provides a commercial open-source alternative for payments infrastructure where the routing, retry, vaulting, and reconciliation logic is transparent and available as independent, composable modules. Because the codebase is open, teams can audit the transaction processing and retry algorithms directly. The modular design allows adoption of individual components rather than requiring a full-stack migration, and the provided Helm charts and Docker setup enable self-managed deployment on a developer's own infrastructure. The project supports a bring-your-own-vault architecture, which lets teams maintain their existing vault provider relationships without being forced into a proprietary tokenization model.
