The team required for a payment gateway changes shape at launch. Before go-live you need builders who can design a secure system and certify it with acquirers. After go-live you need operators who keep it running at three in the morning, answer merchants and pass the next security audit. It's easy to plan for the first team and forget the second.
This page sets out both teams role by role, sizes them for a small and a full scope, lists the software and hardware a gateway company runs on, and compares hiring, outsourcing and licensing.
The team required for a payment gateway build
A payment gateway development team turns a design into a certified gateway. These roles cover the work for a minimum release; larger scopes add engineers to the same roles rather than new ones.
| Role | Main job during the build | Minimum |
|---|---|---|
| Payments architect or tech lead | Money flow, cardholder data environment, connector model | 1 |
| Backend engineers | API, vault, routing, connectors, back office | 3 to 5 |
| Frontend engineer | Hosted payment page, merchant dashboard, admin panel | 1 |
| QA engineer | Declines, refunds, 3-D Secure, acquirer test scripts | 1 |
| Security engineer | Encryption, key management, access control, PCI DSS evidence | 1 |
| DevOps engineer | Environments, deployment, monitoring, backups | 1 |
| Compliance lead | Assessor, acquirers, regulator, policies | 1, often part-time at first |
That's eight to eleven people for a minimum build. Payments experience matters more than headcount here, since a smaller team that has certified a connector before moves faster than a larger one learning the domain.
The run team
After launch, the work shifts from building to operating. The run team is smaller in engineering and larger in operations.
| Role | Main job after launch |
|---|---|
| Engineers on call | Incidents, connector changes, scheme rule updates |
| Site reliability or DevOps | Uptime, capacity, patching, disaster recovery tests |
| Security | Yearly PCI DSS assessment, quarterly scans, access reviews |
| Merchant onboarding and risk | KYB reviews, underwriting, monitoring, chargebacks |
| Finance operations | Settlements, reconciliation, merchant statements |
| Merchant support | Integration help, payment questions, disputes |
The first three rows are engineering. The last three grow with the number of merchants, and they're the team a PSP needs whether it builds the gateway or licenses it.
Headcount by scope
Scope drives the size of the team more than anything else. Every acquirer, country and payment method adds work for engineers, and every merchant adds work for operations.
| Scope | Build team | Run team (engineering) |
|---|---|---|
| One market, two acquirers, hosted page only | 8 to 9 people | 3 to 4 people |
| Several markets, five acquirers, SDKs and plugins | 12 to 15 people | 5 to 7 people |
| Multi-region, own 3-D Secure, self-hosted in several countries | 20 people or more | 8 people or more |
These are planning ranges, not benchmarks. Use them to sanity-check a plan, then size the team from your own scope and the experience of the people you can hire. Multiply each range by the development cost per role to turn it into a budget.
Software and hardware required for a payment gateway company
A gateway company runs on a fairly standard stack, with a few payment-specific pieces. You'll need most of these whatever you build in.
- cloud accounts or data center space, with separate environments for production, testing and the cardholder data environment
- a relational database with replication across locations, plus backups inside and between them
- message queues between services, so a slow acquirer doesn't block the rest
- encryption key management, often in hardware security modules or a cloud key service
- monitoring, logging and alerting across every service and connector
- source control, a build pipeline and security scanning for code and dependencies
- access to each acquirer's sandbox, and a 3-D Secure Server or a service that provides one
Hardware matters less than it used to, since most gateways run in the cloud. Hardware security modules are the main exception, though a cloud key service can stand in for a dedicated HSM in some setups.
Which programming languages a gateway team uses
Gateways run in production on Java, Kotlin, Go, C#, TypeScript, Python and Rust, and the choice usually follows the team. Pick the language your senior engineers know best for the core, and make sure it has mature libraries for decimal money, cryptography and the protocols your acquirers use.
Hiring is easier for popular languages. GitHub's Octoverse 2025 report found TypeScript became the most used language on GitHub in August 2025, which makes it a practical choice for SDKs and dashboards even when the core runs on something else.
Hire, outsource or license
Each route trades control against time and cost. Many companies end up with a mix.
| Route | What you get | What you keep doing |
|---|---|---|
| Hire in-house | Full control and knowledge inside the company | Everything, for as long as the gateway runs |
| Outsource the build | A team with payments experience, faster start | Running the gateway after the agency leaves |
| License the software | A working, certified platform and a vendor team behind it | Sales, merchant operations and your own business rules |
With our white label gateway, the build team shrinks to the people who configure it and connect your systems, and a dedicated payment team on our side handles implementation and ongoing support. Your hiring goes into the run team's operations rows: onboarding, risk, finance and merchant support.
Questions
What team is required to build a payment gateway?
At minimum a payments architect, three to five backend engineers, a frontend engineer, QA, security, DevOps and a compliance lead, which is eight to eleven people for a narrow first release.
How many people does it take to run a payment gateway?
For one market and a few acquirers, plan on three to four engineers for operations and on-call, plus onboarding, risk, finance and support staff who grow with the number of merchants.
What software and hardware are required for setting up a payment gateway company?
Cloud or data center infrastructure with separate environments, a replicated database, message queues, key management, monitoring, a build pipeline and acquirer sandboxes. Hardware security modules are the main specialist hardware.
Can I run a payment company without a development team?
Yes, with licensed white label software. You'll still need operations staff for onboarding, risk, finance and support.