Payment gateway development has a shape that surprises teams coming from ordinary software. Feature work is a minority of the effort. Compliance, certification with acquirers and the operations around live money take as much time as the code, and they set the order in which the code can be written.
This page covers how a gateway project runs phase by phase, who you need on the team, which technology choices matter and which don't, and how to judge a payment gateway development company if you'd rather hire one.
Phases of payment gateway development
A gateway project runs in phases that overlap but can't be reordered much. The compliance work in particular has to start before the first line of production code.
| Phase | What happens | What it produces |
|---|---|---|
| Discovery | Business model, markets, acquirers, license question | A scope and a list of connectors |
| Compliance design | Cardholder data environment, PCI DSS approach, data residency | A segmented architecture and an assessor plan |
| Core build | Merchant API, vault, routing, first connector, hosted page | A gateway that authorizes test payments |
| Back office | Onboarding, pricing, settlements, reconciliation, chargebacks | Tools for operations and finance teams |
| Certification | Acquirer test scripts, 3-D Secure approval path, PCI DSS assessment | Permission to process live payments |
| Launch and operations | First merchants, monitoring, on-call, scheme rule updates | A running payment business |
It's tempting to plan the first three rows and treat the rest as a short tail. In practice, the back office and certification can take as long as the core build.
The team you need
Payment gateway software development needs a mix of roles most product teams don't have. The table shows the core ones, and the size of a gateway development team grows with every acquirer and market you add.
| Role | Why a gateway needs it |
|---|---|
| Payments architect | Designs the money flow, the cardholder data environment and the connector model |
| Backend engineers | Build the API, vault, routing, connectors and back office |
| Security engineer | Owns encryption, key management, access control and PCI DSS evidence |
| QA engineer with payments experience | Tests declines, refunds, 3-D Secure and acquirer edge cases |
| DevOps or SRE | Runs infrastructure, monitoring, backups and on-call |
| Compliance or risk lead | Works with the assessor, acquirers and the regulator |
| Product owner for operations | Speaks for the teams who'll onboard and settle merchants |
The last role is the easiest to skip. Without it, the back office gets built for developers instead of for the people who use it all day.
Choosing a technology stack
Language matters less than people expect. Gateways run in production on Java, Kotlin, Go, C#, TypeScript on Node.js and Python, and the choice usually follows the team's experience.
What matters more is the set of properties the stack has to support. Every payment request needs an idempotency key so a retry never charges twice. Money amounts need exact decimal types, never floating point. Components should talk through queues so one slow acquirer doesn't block the rest, and the database must replicate across locations with tested backups.
GitHub's Octoverse 2025 report found that TypeScript overtook Python and JavaScript in August 2025 to become the most used language on GitHub, which makes it easy to hire for. That's a good reason to use it for merchant-facing SDKs and dashboards even if the core runs on something else.
How long payment gateway development takes
Timelines depend on scope, team and how many acquirers you start with. Vendors that sell gateways publish their own estimates for building in-house, which show the range.
PayAdmit, for example, estimates 12 to 18 months and $500,000 to $1 million to build a gateway in-house, by its own figures. Treat that as one vendor's view, not a benchmark, and add the time your license and acquirer onboarding take, since neither depends on your developers.
Mistakes that cost the most later
Some errors are cheap to avoid in the first month and expensive to fix after launch. These four are worth checking for in any gateway codebase.
Storing money as floating-point numbers is the classic one. A value like 0.1 can't be represented exactly in binary floating point, so rounding errors creep into fees and settlements; use integer minor units or exact decimal types from the start.
Logging is the second. A debug log that captures a full request can end up holding card numbers or CVV codes, and PCI DSS forbids keeping sensitive authentication data such as the CVV after authorization, even encrypted. Mask card data before anything reaches a log.
The third is building for one acquirer. Hard-coding one provider's message format into the core makes the second connector a rewrite, so put every acquirer behind the same internal interface from the first release.
The fourth is leaving reconciliation for later. When the first settlement file from an acquirer doesn't match your own records, you need tooling that finds the gap per transaction. Building it under pressure, with merchants waiting for payouts, is the worst time to start.
Hiring a payment gateway development company
If you don't have the team in-house, you can hire one. Payment gateway development companies range from general software agencies with a payments page to specialists who have certified gateways with acquirers before.
Ask each candidate four questions before you sign. Which acquirers have they certified a connector with? Have they built a system that passed a PCI DSS Level 1 assessment? Who owns the source code at the end? Who runs and updates the gateway after launch, since a gateway without updates falls behind card scheme rule changes?
The answers sort agencies from specialists quickly. They also show the hidden cost of a custom build, which is the team you need to keep after the agency leaves.
Custom development or licensed software
Custom development gives you full control and full responsibility. Licensed white label software gives you a working gateway, a back office and certifications on day one, with the vendor maintaining it.
| Custom build | Licensed white label gateway | |
|---|---|---|
| Time to first live payment | 12 to 18 months by one vendor's estimate | About 5 business days on SaaS with ready connectors, on ours |
| Connectors | Built one by one | 700+ ready on ours; a missing one in about 14 days |
| PCI DSS | Your full assessment | Covered by our Level 1 certification on SaaS |
| Maintenance | Your team, for as long as the gateway runs | Monthly updates from the vendor |
| Control | Total | Configuration, plus custom work where the vendor offers it |
We also offer payment gateway software development as a service alongside the platform. The build versus buy decision usually comes down to whether payment software is your product or a tool for selling something else.
Questions
What is payment gateway development?
It's the work of designing, building, certifying and running the software that carries card and alternative payments from merchants to acquirers. It covers the payment flow, a tokenization vault, routing, connectors, 3-D Secure, a merchant back office and PCI DSS compliance.
Which programming language is best for payment gateway development?
There isn't one best language. Java, Kotlin, Go, C#, TypeScript and Python all run production gateways, and the team's experience matters more than the language itself.
How do I choose a payment gateway software development company?
Ask which acquirers it has certified connectors with, whether its systems have passed a PCI DSS Level 1 assessment, who owns the code and who will run the gateway after launch.
Can I start with licensed software and add custom development later?
Yes, if the vendor allows it. A licensed gateway can carry your brand from day one, and custom features can be added on top where the vendor offers development work.