These technical guides for PSPs, banks and platforms cover what it takes to build a payment gateway, from the first architecture sketch to the yearly security audit. Each one answers a single question in depth, with public figures and named sources where they exist.
We build and license gateway software, so each payment gateway technical guide here is written from both sides. Where building makes sense, the guides say so, and where licensing is faster, they say that too.
Technical guides for PSPs: start with the steps
If you're new to the subject, begin with the build itself. It runs in eight steps, from settling the license question and lining up acquirers to testing, certification and launch, and the order matters more than the speed of any one step. The step-by-step guide walks through each.
See how the parts fit
A gateway is a dozen services, and only a few of them should ever see a card number. Our architecture overview lists every component with a diagram of how a payment moves through them.
Know what it costs
People take most of the budget. A seven-person team at US median wages costs about $1.30 million a year with benefits, and the cost of building adds compliance, infrastructure and the months before revenue.
Price the team role by role
Developers, QA, security and operations each have their own wage line in public data. The development cost guide turns them into budgets for a build and for running the gateway after launch.
Plan the team and the process
A gateway project runs in phases that can't be reordered much, and it needs roles most product teams don't have. Read about the development process before you hire.
Get PCI DSS right from day one
Security comes first. PCI DSS v4.0.1 applies to every system that touches card data, and a gateway validates every 12 months, as the PCI DSS guide explains.
Understand the specialist components
Some parts of a gateway are specialist products in their own right. 3-D Secure has its own specifications and approvals, and the 3DS Server guide covers whether to build, license or outsource it.
Decide where it runs
Hosted SaaS is fastest, but some regulators want payment data kept in the country. The on-premises guide covers who needs self-hosting and how the work splits.
Look at open source and source code
Open source projects can carry part of the load, and some vendors sell their code outright. The open source overview compares the main projects and their licenses.
Build for a specific business
A bank, a SaaS platform, a marketplace and a crypto business each need something different from a gateway. Banks, for example, often need in-country hosting and a back office for large merchant portfolios, covered in the guide for banks.
Make the build or buy decision
Decide this early. Before committing a team for 18 months, run the decision properly with numbers from your own market, your own volumes and the people you can actually hire. The build versus buy framework sets out ten questions and a break-even check.