hyperswitch-prism

Prism lets your code talk to Stripe, Adyen, Braintree, PayPal, Worldpay and dozens of other payment processors through one request format, so switching processors becomes a config change instead of a rewrite. Juspay pulled it out of Hyperswitch, its open source payments platform, and it's Apache 2.0 with no paid tier.

It's a library, not a service. Install it from npm, PyPI, Maven or Cargo, or run it as a stateless gRPC server in Docker. It stores nothing: processor credentials ride along with each request and there's no database. The native SDK libraries only ship for Apple Silicon Macs and x86 Linux right now, so Windows and ARM Linux need the Docker server.

Teams already running two or more processors, or wanting the option to leave Stripe without rebuilding checkout, get the most here. It only translates requests. Routing, retries and a card vault live in the full Hyperswitch (juspay/hyperswitch), whose Enterprise and Cloud editions are contact-sales with no public prices. Solo devs on one processor should just use that processor's SDK.

The catch: it's pre-1.0 and coverage is uneven, with plenty of payment methods still marked in progress. And ignore the website line about no compliance. If raw card numbers pass through your server, you're in PCI scope no matter how stateless the library is.