hyperswitch

Hyperswitch sits between your app and payment processors like Stripe, Adyen, and PayPal, routing each transaction to whichever is cheapest or most likely to succeed. Juspay, whose team runs payment infrastructure for more than 400 enterprises, open sourced the core in Rust under Apache 2.0. One API, many processors, no rewrite when you add or drop one.

Trying it locally is a one-line setup script. Production is different: Helm charts on AWS, GCP, or Azure, plus the PCI scope questions that arrive the moment card data flows through systems you operate. This is a payments team tool, not a weekend deploy. A newer option is adopting pieces, since the routing decision engine and the connector library now ship as standalone repos.

Single-processor startups don't need it. Stripe alone is simpler than Stripe behind a switch. It earns its keep when you juggle multiple processors for fees, geographic coverage, or failover. Solo and small teams: skip. Companies at real volume: smart routing and retries can recover a measurable slice of revenue. Enterprise Edition and Cloud exist when you would rather pay Juspay to run it, and neither has public pricing.

The catch: it orchestrates payments, it doesn't process them. You still need contracts with the underlying processors. Revenue recovery, cost observability, and reconciliation are paid add-ons on both self-hosted editions, and only come included with Cloud.