43.6k stars · Apache-2.0 · v1.126.0 (2026-08-24)
Open, composable payments orchestration across many processors, with routing and revenue recovery.
▶Repo detailsthe review · specs · pros & cons · install
What it is
Hyperswitch is a payment orchestration layer written in Rust. It gives you one API in front of many payment providers, with routing rules, retries, card storage and a merchant control panel.What it is good for. A business that already takes money and is feeling the cost of one provider — fees, a country that is not supported, or payments that fail for one card type. The routing is the point: send European cards one way and American cards another, and retry a failure with a second provider instead of losing the sale. Be clear about the stage this fits. If you have not taken a first payment yet, Polar from Edition 11 is the right size, because it handles EU VAT for you and takes a percentage. Hyperswitch is what you move to later, and it is worth knowing it exists before you write payment code you will have to unpick.
- Apache-2.0, and it comes from a company that runs payments at scale rather than a side project.
- Routing rules, automatic retries across providers, and card storage in one place.
- There is a hosted sandbox, so you can see the whole thing working before installing anything.
- It needs PostgreSQL and Redis, and the full profile also brings a monitoring stack. Use the minimal profile on a small machine.
- Self-hosting anything that touches card numbers puts the card-industry compliance work on you. That is the real cost, not the licence.
- Releases come very fast — version 1.126.0 already. Pin your version and read the notes before upgrading.
git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch cd hyperswitch scripts/setup.sh
