PAYING.CO GUIDES
Open source payment gateways: what exists and what you still need
What the projects do, what they leave out, and how to pick one.
6 min read · By Kevin Medina · Updated November 22, 2026
The short version
Open source can give you payment orchestration, billing and protocol code for free. It cannot give you processor access, PCI compliance or card certification. Treat it as the software layer and plan for the rest.
What people mean by an open source payment gateway
A gateway takes a payment request from your software, sends it to a processor or acquirer, and returns the result. Almost nothing labelled open source does the second half for you. The code is free, but the connection to a card network is not. Someone still has to hold a merchant account, an acquiring relationship and the credentials that let a transaction reach an issuer.
It helps to separate four things that all get called open source payments:
- Open source software that orchestrates or switches payments between processors you already have.
- Open source billing that decides what to charge and when.
- Open source protocol libraries, such as ISO 8583, that let you build your own host or terminal code.
- Open source client SDKs for a commercial service. The SDK is open, the service is not.
Projects worth knowing
This is a starting list, not a ranking. We have not tested every project in production, and licenses, maintenance and features change, so check each repository for the current license, last release and open issues before you commit.
| Project | What it is | Main language | Notes |
| Hyperswitch | Payment switch / orchestration | Rust | Routes one integration to many processors, with retries and a vault. You still need your own processor accounts. |
| Kill Bill | Subscription billing and payments | Java | Billing, invoicing and payment plugins for several gateways. Strong fit for recurring revenue. |
| Lago | Usage-based billing | Ruby, Go | Metering and invoicing. It decides what to charge, not how money moves. |
| BTCPay Server | Crypto payment processor | C# | Self-hosted Bitcoin and crypto checkout with no third-party custodian. |
| jPOS | ISO 8583 framework | Java | The long-standing open framework for building ISO 8583 hosts, switches and terminals. Dual licensed, so check the terms. |
| Mojaloop | Instant payments switch | Node.js, TypeScript | Hub software for national and regional instant payment schemes. Aimed at scheme operators, not merchants. |
| Rafiki (Open Payments) | Open Payments reference implementation | TypeScript | Reference software for the Interledger Open Payments API. Early-stage compared with card rails. |
What open source does not solve
- Processor and acquirer access. You need a merchant account or a processing agreement either way.
- PCI DSS scope. Self-hosting card data handling puts that scope on you, which is why many teams keep card data in a hosted field or vault and only self-host the logic around it.
- Card-present certification. A terminal that takes chip and contactless cards needs EMV Level 3 certification with your processor, whatever software sits underneath.
- Fraud, disputes and reconciliation. These are operational work, not a library.
- Support and uptime. If the payment path breaks at 2 am, you own it.
A practical way to choose
- Start from the job. Online checkout, subscriptions, a terminal, a switch and a marketplace payout flow need different tools.
- Decide who holds card data. If it is not you, you probably want a hosted payment page or tokenization from a processor, plus open source around it.
- Read the license. AGPL and similar terms can affect how you ship a product built on the code.
- Check the maintenance. Recent releases, active issues and a clear security policy matter more than star counts.
- Budget for integration and certification. The code is the cheaper part of a payments project.
Our own open source libraries
Paying.co publishes public SDKs on GitHub for our hosted products Ask, Landed.net and Puny.io, in JavaScript and TypeScript, Python, Go, PHP and C#. These are client libraries for our services, not a self-hosted gateway. Browse them on the repositories page, or see how the Ask payment links API works.
Working with ISO 8583
If your project involves a card host or switch, the message format matters. Our reference covers MTI codes, response codes, processing codes and data elements, and the ISO 8583 decoder shows what is inside a message.
Frequently asked questions
Is there a free open source payment gateway?
There are free open source projects that orchestrate or switch payments, such as Hyperswitch, but none of them removes the need for a processor or acquirer. The software is free. Moving money through a card network still needs a merchant relationship.
Can I process cards with open source software only?
Not on its own. You need a processor or acquirer, and if you handle card data yourself you take on PCI DSS responsibilities. Many teams use open source for orchestration and billing while leaving card data with a hosted processor.
What is the best open source payment gateway?
It depends on the job. Hyperswitch is aimed at routing across processors, Kill Bill at subscription billing, BTCPay Server at crypto checkout and jPOS at ISO 8583 host and terminal work. Check license, maintenance and fit for your use case.
Do open source SDKs mean the payment service is open source?
No. Many commercial processors publish open source client SDKs for their APIs. The SDK is open, but the service behind it is not.
Building a payments product?
Tell us what you are building. A payments engineer will help you decide what to build, what to buy and what needs certification.
Talk to us Book a meeting with a founder