The short answer: from about half a million dollars for a lean build by one vendor's estimate, to around $3 million over three years for a US-based team that builds and then runs it. The long answer depends on six cost lines, and many estimates count only the first one.
This page goes through all six, shows the figures that are public, and adds them up over three years. The team line rests on a development cost breakdown by role, using US median wages.
The six cost lines
To answer how much does it cost to build a payment gateway, you need all six lines: people, compliance, infrastructure, connectors, licensing and the months before revenue. Here's what each covers.
| Cost line | What it covers | Public figure |
|---|---|---|
| Team | Engineers, QA, security and operations for the build and after | About $1.30 million a year for a seven-person team at US median wages with benefits |
| Compliance | PCI DSS gap work, the yearly assessment, quarterly external scans | Assessor fees are quoted, not published |
| Infrastructure | Hosting, replication across locations, monitoring, backups | Hyperswitch's own blog puts self-hosting its platform at USD 100 to 1,500 a month in infrastructure |
| Connectors and services | Acquirer integrations, 3-D Secure, fraud scoring, KYC checks | Varies by provider; KYC is usually a fee per check |
| Licensing and legal | Payment license where your model needs one, contracts with acquirers | Set by each regulator and law firm |
| Time to revenue | Months of cost before the first merchant pays you | 12 to 18 months of build by one vendor's estimate |
The team line dominates. The others are smaller in money but can be larger in time, especially licensing and acquirer onboarding.
Cost of developing a payment gateway: the team
A minimum team of five developers, one QA engineer and one security engineer earns $913,380 a year at US median wages for May 2025, according to the Bureau of Labor Statistics. Benefits make up 30% of private employers' compensation costs in the BLS employer cost survey, so the loaded figure is about $1.30 million a year.
At that rate a 12-month build costs about $1.30 million and an 18-month one about $1.96 million, before anything else on the list. A team hired outside the US costs less per head, but the schedule barely changes, because certification and acquirer reviews don't run faster.
Compliance costs
PCI DSS is a cost every year, not once. A gateway is a service provider, and Visa requires issuers and acquirers to make sure their service providers demonstrate compliance at least every 12 months.
The first assessment is the expensive one: a gap review, remediation, evidence collection and the assessor's testing. After that come quarterly external vulnerability scans and a yearly reassessment. The assessor's fee is only part of the PCI DSS cost, since the gap work before it often takes longer than the audit.
Infrastructure costs
Infrastructure is the smallest line in most budgets, at least early on. Hyperswitch, which publishes an open source payments platform, estimates USD 100 to 1,000 a month for self-hosting infrastructure in one table and USD 100 to 1,500 in its FAQ, plus engineering time.
That range covers a small deployment. Replication across locations, disaster recovery, separate environments for testing and a segmented cardholder data environment all add to it as volume grows.
How much does it cost to build a payment gateway over three years?
Adding the lines up shows why a build is a multi-year commitment. These scenarios use only the public figures above and leave out compliance fees, licensing and connector costs, which vary too much to publish.
| Scenario | Build | Running costs after launch | Three-year people cost |
|---|---|---|---|
| Lean build (vendor estimate) | $500,000 to $1 million over 12 to 18 months, PayAdmit's own figure | Not included in the estimate | From $500,000, plus running costs |
| US-based team | About $1.96 million for 18 months | About $714,671 a year for a four-person operating team | About $1.96M + $1.07M = $3.03 million |
The second row is the honest ceiling for a US team. The first is what a lean, lower-cost build can reach, before the team that keeps it running.
What the numbers mean against licensing
Published license prices look small next to a build. Coriunder lists a $5,000 setup and $1,000 or $2,000 monthly minimums, and UniPay Gateway lists an on-premise license with source code from $150,000. Even a hosted instance at UniPay's published $15,000 a month adds up to $540,000 over three years before transaction fees, which is below the people cost of a US build.
The comparison isn't only about money. A license gets you processing in days or weeks instead of a year and a half, and the vendor keeps the software current. Building pays off when payment software is the product you'll sell, or when no vendor offers the control you need. The build versus buy framework helps you check which side you're on.
Questions
How much does it cost to set up your own payment gateway?
By one vendor's estimate, $500,000 to $1 million and 12 to 18 months for a lean in-house build. A US-based seven-person team costs about $1.30 million a year with benefits, so an 18-month build and the first year and a half of running it come to about $3 million in people alone.
What compliance do I need when building a payment gateway?
PCI DSS for the whole cardholder data environment, validated every 12 months, plus quarterly external scans. If you hold or move merchant funds, you'll usually need a payment license as well.
What's the cost to build a custom payment gateway compared with buying one?
Building costs mostly people, from about half a million dollars for a lean team to about $3 million over three years for a US team. Published license prices run from a $5,000 setup with monthly minimums to $150,000 for a license with source code.
Are there hidden costs in building a payment gateway?
The usual ones are the operating team after launch, yearly PCI DSS work, connectors that break when acquirers change their APIs and the revenue you don't earn while the build runs.