Writing the code that sends a card payment to an acquirer is the easy part of a payment gateway. The hard parts sit around it: the contracts that let you process at all, the security standard your whole environment has to pass, and the back office that turns transactions into settlements your merchants trust.
This guide walks through how to build a payment gateway in eight steps, in the order the work actually has to happen. It names the standards and bodies involved, gives the figures that are public, and says where licensing existing software is the faster route. We build and license gateway software ourselves, so we'll be plain about both options.
How to build a payment gateway: first decide what it is
People search for how to create a payment gateway or how to make a payment gateway when they mean three different businesses. The word you use decides which licenses, contracts and certifications you need, so settle it first.
| You want to | What you're building | What you'll need beyond software |
|---|---|---|
| Pass card data from merchants to acquirers | A payment gateway | Acquirer integrations, PCI DSS validation |
| Sign merchants and pay them out | A payment service provider (PSP) | Usually a payment license, acquirer contracts, a back office |
| Authorize and clear with the card schemes | A payment processor | Scheme membership or a sponsor, scheme certification, much larger investment |
If you're asking how to build a payment processor, check first whether a gateway or a PSP would do the job. Direct scheme processing is a different scale of project, and it usually belongs to banks and established processors.
Step 1: pick the business model and check the license
Start with the money flow, because it decides your regulatory status. A company that only transmits payment data has a lighter path in most countries than one that receives merchant funds and pays them out.
If you'll hold or move funds, expect to need a payment institution, e-money institution or money transmitter license, depending on the country. That process runs on the regulator's timetable, so begin it before writing code, because PSP licenses differ by country in scope, capital and review time.
Step 2: line up acquirers and payment methods
Acquirers come next. A gateway with no acquirer behind it can't process a single payment. Acquirers review a new gateway or PSP before they sign, including your ownership, compliance setup and business model.
Pick two acquirers from the start if you can. One acquirer is a single point of failure, and routing between two gives you a fallback when one declines more than usual or goes down. Add local payment methods for each market you plan to serve, since a card-only checkout loses shoppers who pay by bank transfer or wallet.
Step 3: design the architecture
A gateway is a set of services, not one program. The core pieces are an API layer for merchants, a tokenization vault for card data, a routing engine, connectors to each acquirer and a 3-D Secure component. Around them sit fraud screening, a merchant back office, settlement and reconciliation, and reporting.
Design the cardholder data environment as small as possible. Everything that stores, processes or transmits card data falls inside PCI DSS scope, so isolating the vault and the few services that touch card numbers keeps the rest of the system simpler to secure and audit. That one decision shapes the whole gateway architecture, from where tokens live to which services can call the vault.
Step 4: plan PCI DSS from day one
PCI DSS is the security standard every company that stores, processes or transmits card data has to meet. Its current version is v4.0.1, the only one still active since v4.0 was retired at the end of 2024.
Of the 64 requirements that v4 added, 51 became effective on March 31, 2025. Acquirers have to check their service providers' PCI DSS status at least once a year under Visa's rules, so yours will ask for your validation every year.
A gateway usually validates as a service provider through an assessment by a Qualified Security Assessor, and the audit covers people and processes as much as code, which is why PCI DSS for PSPs needs an owner on your team from the first sprint.
Step 5: build connectors, 3-D Secure and tokens
Each acquirer has its own API, message formats, error codes and test environment. Budget time for every connector, including refunds, partial captures, voids and the error cases, not just a successful authorization.
3-D Secure needs its own planning. EMVCo maintains the EMV 3-D Secure specifications and runs the approval process for 3DS products, so licensing a 3DS Server and MPI, or connecting to an approved one, is often quicker than building and getting your own approved. Network tokenization adds another integration, this time with the card schemes' token services, and it keeps stored cards working when issuers reissue them.
Step 6: build the merchant back office
Merchants judge a payment provider by its back office as much as by its approval rates. Your team needs onboarding with KYB and KYC checks, underwriting and risk scoring, pricing per merchant, settlements with reserves and holdbacks, reconciliation and chargeback handling.
Your merchants need a dashboard with their transactions, statements and payouts, plus integration options such as a hosted payment page, SDKs and plugins. Teams can easily underestimate this part, since none of it moves a payment but all of it decides whether merchants stay.
Step 7: test, certify and pass acquirer onboarding
Test every flow against each acquirer's sandbox before going live: approvals, soft and hard declines, 3-D Secure challenges, refunds and chargebacks. Then expect acquirer-specific certification, where the acquirer checks your messages against its own test scripts.
Validate first. Run your PCI DSS assessment before live traffic, not after. Acquirers won't route production payments through an environment that hasn't validated.
Step 8: launch and operate
Go live with a small group of merchants, watch the first settlements closely, then open sales. Then the real work starts. From then on, a gateway is an operations business. You'll answer incidents at any hour, keep up with card scheme rule changes, renew PCI DSS validation every year and add connectors as merchants ask for new markets.
Plan the operating team before launch, since the development team that built the gateway rarely has the on-call and compliance roles that run it.
How long and how much it takes
Building a gateway is mostly a staffing cost spread over a long time. The figures below are the public ones; vendor estimates are vendors' own and labeled as such.
| Figure | Source |
|---|---|
| $135,980 median annual wage for US software developers, May 2025 | US Bureau of Labor Statistics |
| $500,000 to $1 million and 12 to 18 months to build a gateway in-house | PayAdmit's own estimate |
| From $500,000 to build your own PSP | Tranzzo's own estimate |
| From $150,000 for an on-premise gateway license with source code | UniPay Gateway's published price |
The wage figure shows why estimates run high. Eight developers at the US median cost $135,980 x 8 = $1,087,840 a year in wages alone, before benefits, compliance, hosting and the team that runs the gateway after launch. Those extra lines are what push the cost to build well past the wage bill.
The faster route: license the software
Sometimes building is right. It makes sense when payment software itself is the product you'll sell, or when you need control no vendor offers. For many PSPs and banks, the gateway is a means to sign and serve merchants, and licensing it moves the first live payment from more than a year away to days.
Our white label gateway runs as SaaS, in your own cloud account or on your own servers. On SaaS with ready connectors, processing starts in about 5 business days on average, with 700+ connectors, a merchant back office and PCI DSS Level 1 certification that covers the platform. Weigh build versus buy on your own volumes and markets before you hire a team.
Questions
How do I create a payment gateway from scratch?
Decide whether you're building a gateway, a PSP or a processor, settle licensing and acquirers, then keep the card-handling part of the system small and plan PCI DSS from the start. After that come connectors, 3-D Secure, the merchant back office, testing, acquirer certification and launch.
Can I build a payment gateway without a license?
A gateway that only transmits card data often needs no payment license, but it still needs PCI DSS validation and acquirer contracts. If you receive or pay out merchant funds, you'll usually need a license in each country you serve.
What's the hardest part of building a payment gateway?
For most teams, PCI DSS and the merchant back office. The security standard covers your whole environment and people, and the back office takes as much work as the payment flow itself.
How do I make a payment gateway accept local payment methods?
Each method needs its own connector, either directly or through a PSP that aggregates them. Plan which methods each market needs before choosing acquirers, since some acquirers bundle local methods and others don't.