An open source payments switch to make payments fast, reliable and affordable
See the code
Supported Features • What's Included • Deploying Hyperswitch • Suite Compatibility • Join us in building HyperSwitch • Community • Versioning • Copyright and License
Hyperswitch Suite is the master repository for the Hyperswitch payments stack. It defines the open-source product bundle — the app server, web client, control center, card vault and WooCommerce plugin — along with the compatible versions of each component. It also hosts the Terraform and Terragrunt modules used to deploy the stack on AWS and GCP.
juspay/hyperswitch.terraform/ tree and the Deploying Hyperswitch section below.Using Hyperswitch, you can:
Hyperswitch integrates with 100+ payment processors out of the box — including Stripe, Adyen, Braintree, Worldpay, Checkout.com, Cybersource and many others — exposing smart routing and retry logic across multiple global payment methods. We continuously add new processors based on their reach and community requests.
You can browse the full list of supported processors, payment methods and capabilities here.
In addition to all the features of the open-source product, our hosted version provides features and support to manage your payment infrastructure, compliance, analytics, and operations end-to-end:
System Performance & Reliability
Value Added Services
Enterprise Support
You can try the hosted version in our sandbox.
Hyperswitch is architected as a comprehensive suite comprising multiple components, each housed in separate repositories and open-sourced.
This repository contains the Infrastructure-as-Code (Terraform / Terragrunt) used to deploy Hyperswitch on AWS and GCP.
| Cloud | Live layer | Catalog/Units | Modules |
|---|---|---|---|
| AWS | terraform/aws/live/ (Terragrunt Stacks) | terraform/aws/catalog/units/ + stacks/dev | Base, composition, application-resources, CloudFront resources |
| GCP | terraform/gcp/live/sandbox/asia-south1/ | terraform/gcp/catalog/units/ + stacks/dev | Composition, application-resources, packer |
Key deployment docs:
terraform/aws/ARCHITECTURE.md — AWS module architecture and dependency graphterraform/aws/README.md — AWS step-by-step deployment guideterraform/gcp/catalog/README.md — GCP catalog unit skeleton, tag naming and CIterraform/aws/live/README.md — how the AWS live layer is organisedThe CHANGELOG.md lists each Hyperswitch Suite release and the upstream component releases it is validated against: the Hyperswitch app server, control center, web client, card vault, encryption service and WooCommerce plugin. The suite release tag (e.g. v1.21) is the compatibility anchor; the individual application images and Helm values are managed in the GitOps layer (ArgoCD/Helm) outside this repository.
Payments should be open, fast, reliable and affordable to serve the billions of people at scale.
Globally payment diversity has been growing at a rapid pace. There are hundreds of payment processors and new payment methods like BNPL, RTP etc. Businesses need to embrace this diversity to increase conversion, reduce cost and improve control. But integrating and maintaining multiple processors needs a lot of dev effort. Why should devs across companies repeat the same work? Why can't it be unified and reused? Hence, Hyperswitch was born to create that reusable core and let companies build and customize it as per their specific requirements.
This project is being created and maintained by Juspay, South Asia's largest payments orchestrator/switch, processing more than 50 Million transactions per day. The solution has 1Mn+ lines of Haskell code built over ten years. Hyperswitch leverages our experience in building large-scale, enterprise-grade & frictionless payment solutions. It is built afresh for the global markets as an open-source product in Rust. We are long-term committed to building and making it useful for the community.
The product roadmap is open for the community's feedback. We shall evolve a prioritization process that is open and community-driven. We welcome contributions from the community. Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development. We appreciate all types of contributions: code, documentation, demo creation, or some new way you want to contribute to us.
Get updates on Hyperswitch development and chat with the community:
Check the CHANGELOG.md file for suite releases and the compatible upstream component versions.
This product is licensed under the Apache 2.0 License.
HCL
91.5%
Shell
3.8%
Python
2.2%
Go Template
1.4%
An open source payments switch to make payments fast, reliable and affordable
See the code
Supported Features • What's Included • Deploying Hyperswitch • Suite Compatibility • Join us in building HyperSwitch • Community • Versioning • Copyright and License
Hyperswitch Suite is the master repository for the Hyperswitch payments stack. It defines the open-source product bundle — the app server, web client, control center, card vault and WooCommerce plugin — along with the compatible versions of each component. It also hosts the Terraform and Terragrunt modules used to deploy the stack on AWS and GCP.
juspay/hyperswitch.terraform/ tree and the Deploying Hyperswitch section below.Using Hyperswitch, you can:
Hyperswitch integrates with 100+ payment processors out of the box — including Stripe, Adyen, Braintree, Worldpay, Checkout.com, Cybersource and many others — exposing smart routing and retry logic across multiple global payment methods. We continuously add new processors based on their reach and community requests.
You can browse the full list of supported processors, payment methods and capabilities here.
In addition to all the features of the open-source product, our hosted version provides features and support to manage your payment infrastructure, compliance, analytics, and operations end-to-end:
System Performance & Reliability
Value Added Services
Enterprise Support
You can try the hosted version in our sandbox.
Hyperswitch is architected as a comprehensive suite comprising multiple components, each housed in separate repositories and open-sourced.
This repository contains the Infrastructure-as-Code (Terraform / Terragrunt) used to deploy Hyperswitch on AWS and GCP.
| Cloud | Live layer | Catalog/Units | Modules |
|---|---|---|---|
| AWS | terraform/aws/live/ (Terragrunt Stacks) | terraform/aws/catalog/units/ + stacks/dev | Base, composition, application-resources, CloudFront resources |
| GCP | terraform/gcp/live/sandbox/asia-south1/ | terraform/gcp/catalog/units/ + stacks/dev | Composition, application-resources, packer |
Key deployment docs:
terraform/aws/ARCHITECTURE.md — AWS module architecture and dependency graphterraform/aws/README.md — AWS step-by-step deployment guideterraform/gcp/catalog/README.md — GCP catalog unit skeleton, tag naming and CIterraform/aws/live/README.md — how the AWS live layer is organisedThe CHANGELOG.md lists each Hyperswitch Suite release and the upstream component releases it is validated against: the Hyperswitch app server, control center, web client, card vault, encryption service and WooCommerce plugin. The suite release tag (e.g. v1.21) is the compatibility anchor; the individual application images and Helm values are managed in the GitOps layer (ArgoCD/Helm) outside this repository.
Payments should be open, fast, reliable and affordable to serve the billions of people at scale.
Globally payment diversity has been growing at a rapid pace. There are hundreds of payment processors and new payment methods like BNPL, RTP etc. Businesses need to embrace this diversity to increase conversion, reduce cost and improve control. But integrating and maintaining multiple processors needs a lot of dev effort. Why should devs across companies repeat the same work? Why can't it be unified and reused? Hence, Hyperswitch was born to create that reusable core and let companies build and customize it as per their specific requirements.
This project is being created and maintained by Juspay, South Asia's largest payments orchestrator/switch, processing more than 50 Million transactions per day. The solution has 1Mn+ lines of Haskell code built over ten years. Hyperswitch leverages our experience in building large-scale, enterprise-grade & frictionless payment solutions. It is built afresh for the global markets as an open-source product in Rust. We are long-term committed to building and making it useful for the community.
The product roadmap is open for the community's feedback. We shall evolve a prioritization process that is open and community-driven. We welcome contributions from the community. Please read through our contributing guidelines. Included are directions for opening issues, coding standards, and notes on development. We appreciate all types of contributions: code, documentation, demo creation, or some new way you want to contribute to us.
Get updates on Hyperswitch development and chat with the community:
Check the CHANGELOG.md file for suite releases and the compatible upstream component versions.
This product is licensed under the Apache 2.0 License.
HCL
91.5%
Shell
3.8%
Python
2.2%
Go Template
1.4%