Yes, open source payment gateways exist, and a few are serious projects with large communities. But "open source" settles only one question, who can read and change the code. It doesn't settle who runs the servers, who passes the PCI DSS assessment or who signs with the acquirers, and those are the expensive parts of running a gateway.
This page lists the main open source payment gateway projects as of November 16, 2026, sorts them by what they actually are, explains what their licenses allow and sets out the work that stays with you after you download the code.
What open source payment gateways can be
Projects that turn up when you search for payment gateway open source code fall into four groups. Mixing them up is an easy mistake, because a library and a gateway solve different problems.
| Group | What it does | Who it's for |
|---|---|---|
| Payment platform | A full service that routes payments to many providers, with an API, dashboard and vault | PSPs, platforms and large merchants that want to self-host |
| Billing platform | Subscriptions, invoicing and payment retries on top of existing gateways | SaaS and subscription businesses |
| Gateway library | Code inside an application that talks to many gateways through one interface | Developers of shops and apps |
| Card processing framework | Building blocks for card messaging, such as ISO 8583 | Teams building switches and processors |
Only the first group is a gateway in the sense a PSP means it. The others are useful parts of a payment stack, not a stack on their own.
Open source payment gateway projects compared
These are well-known projects in each group, with figures read from each repository on GitHub on November 16, 2026. Star counts show community size, not quality.
| Project | Group | License | Language | GitHub stars | Last push |
|---|---|---|---|---|---|
| Hyperswitch (Juspay) | Payment platform | Apache 2.0 | Rust | 45,788 | November 16, 2026 |
| Kill Bill | Billing platform | Apache 2.0 | Java | 5,860 | November 13, 2026 |
| Omnipay | Gateway library (PHP) | MIT | PHP | 6,068 | July 10, 2026 |
| Active Merchant | Gateway library (Ruby, from Shopify) | MIT | Ruby | 4,602 | October 22, 2026 |
| jPOS | Card processing framework (ISO 8583) | AGPL 3.0 | Java | 739 | November 12, 2026 |
Hyperswitch is the closest to a full payment gateway software open source option. Juspay open-sourced it in 2022, and it describes itself as a composable payments platform with SaaS and self-host options. Its own pages give different integration counts, from 90+ for the self-hosted editions to 300+ on its homepage, so check the list for your providers before you plan around it.
What the licenses allow
The license decides what you may do with the code once you change it. The projects above use three of them.
Apache 2.0 and MIT are permissive. You can modify the code and run it in a commercial service without publishing your changes, as long as you keep the license notices.
AGPL 3.0 is different: if you modify AGPL code and let users interact with it over a network, you have to offer them the modified source. Juspay publishes its routing component, decision-engine, under AGPL 3.0 while the Hyperswitch core is Apache 2.0, so a self-hosted stack can mix both.
Read the license of every component you deploy, not only the main repository. A permissive core with a copyleft module carries the copyleft terms for that module.
What open source doesn't change: PCI DSS
The code being open has no effect on PCI DSS. If your servers store, process or transmit card data, your environment is in scope, and you validate it like any other gateway operator.
Hyperswitch's own documentation spells this out for its self-hosted edition. Above 1 million card transactions a year it requires a Report on Compliance from a Qualified Security Assessor, below that a self-assessment questionnaire, and quarterly network scans by an Approved Scanning Vendor in both cases. The PCI DSS assessment itself then runs the same way as for any commercial gateway.
What self-hosting costs beyond the license
There's no license fee, but there's still a bill. Infrastructure, engineering time and compliance all land on you.
| Cost line | What to expect |
|---|---|
| Hosting | Hyperswitch's own blog gives USD 100 to 1,000 a month in one table and USD 100 to 1,500 in its FAQ for infrastructure |
| Engineering | Developers to deploy, patch, upgrade and extend the code, plus on-call cover |
| Compliance | Your own PCI DSS validation every year, and network scans every quarter |
| Connectors | Building or maintaining any provider the project doesn't support |
| Merchant back office | Onboarding, pricing, settlements and reconciliation, if the project doesn't include them |
The engineering line is the one that grows. Payment providers change their APIs and card schemes change their rules, and someone on your team has to keep up with both.
Is it possible to build a secure gateway from open source alone?
Technically, yes. Open source operating systems, databases, encryption libraries and payment projects can form a secure stack, and many commercial gateways run on open source components underneath.
Security comes from the design and the operations, not from whether the code is open. Segmenting the cardholder data environment, managing encryption keys properly, patching quickly and monitoring every access matter far more than the license. An open project with an active community gets security fixes in public, which helps, but you still have to apply them.
When open source fits, and when licensed software does
Open source fits teams that have strong payments engineering in-house and want full control of the code. It also suits companies whose product is the payment platform itself, where owning every layer is the point.
For a PSP or bank whose business is signing and serving merchants, the trade often runs the other way.
Our licensed white label gateway comes with 700+ ready connectors, a merchant back office, monthly updates and PCI DSS Level 1 certification that covers the platform on SaaS, and it can also run in your own cloud account or on your own servers. Weigh both against your team, using the build versus buy questions.
Questions
Are there any actual open source payment gateways?
Yes. Hyperswitch is an open source payments platform under Apache 2.0 that routes payments to many providers and can be self-hosted. Kill Bill covers billing and payments, while Omnipay and Active Merchant are libraries for connecting applications to gateways.
Is an open source payment gateway free?
The code is free under its license. Hosting, engineering, PCI DSS validation, network scans and support aren't, and they make up most of the cost of running a gateway.
Do I need PCI DSS compliance if I use open source payment gateway software?
Yes, if your environment stores, processes or transmits card data. Hyperswitch's documentation, for example, requires a Report on Compliance above 1 million card transactions a year for its self-hosted edition.
Which license is best for a commercial payment product?
Permissive licenses such as Apache 2.0 and MIT let you keep your changes private. AGPL 3.0 requires you to offer modified source to users who interact with it over a network.