Hyperswitch is Juspay's open-source, Rust-based payments orchestration platform (Apache 2.0) connecting 100+ processors. We deployed it on the client's own cloud and configured intelligent, success-based routing across multiple acquirers.
A US e-commerce retailer processing eight-figure GMV was bleeding margin to a single processor and feared Stripe lock-in. They had no way to split traffic across acquirers or retry failed charges intelligently without a long, risky in-house build.
- Deploying a PCI-aware payments switch into the client's own AWS account without a months-long platform project.
- Integrating three processors (Stripe, Adyen, Checkout.com) behind one unified payments API and a single drop-in checkout.
- Configuring success-based routing and smart-retry recovery so declined transactions were re-attempted on the acquirer most likely to approve them.
We deployed Hyperswitch via its official AWS CloudFormation template, replaced the client's Stripe Elements with the Hyperswitch Web SDK, added merchant connector accounts through the Control Center, and configured a success_based_routing algorithm with revenue-recovery retries.
- One-click AWS CloudFormation provisioning of the Rust hyperswitch-router and Control Center inside the client's account in well under an hour.
- A unified checkout built on the Hyperswitch Web SDK and Vault, routing payments across Stripe, Adyen, and Checkout.com with no processor-specific code in the storefront.
- A success-based routing policy plus elimination routing and smart retries, with webhooks wired into the client's order service for settlement state.
A customized view of the system we shipped for this engagement — the components and how requests and data flow between them.
Before — manual bottleneck flow
Every payment goes to one acquirer with no fallback, so a decline is simply lost.
Failed-payment reports are pulled by hand with no automated retry path.
Adding any new acquirer means a bespoke integration and a fresh PCI scope review.
After — automated optimized flow
One drop-in widget tokenizes the card via Vault, processor-agnostic.
The switch picks the acquirer most likely to approve and retries the rest automatically.
Final payment state is pushed to the client's order system in real time.
“We were nervous about touching payments at all. They moved us onto Hyperswitch one processor at a time so nothing broke in production, and the routing has quietly recovered a chunk of the declines we used to just write off.”
