Payment gateway regulation turns mostly on one question, and so does whether you need a payment gateway license: will your company hold or move merchants' money, or only pass payment data along? Most regulators license the money, not the technology. A few license the technology as well.
This page sets out the general rule, shows how six regulators apply it, and explains how to get a payment gateway license where one is needed.
The general rule: funds, not software
A pure gateway carries payment data from a checkout to acquirers and processors. It never receives the merchant's funds, so in most countries it isn't a regulated payment service, though it still has to meet card scheme rules such as PCI DSS validation.
The picture changes once the company collects funds and pays them to merchants. That's a payment service almost everywhere, and it needs a license or registration, or a licensed partner to do it on the company's behalf.
How six regulators treat payment gateways
The rule holds in most markets, with one clear exception. The table shows where each regulator draws the line.
| Market | Gateway that only passes data | Company that handles merchants' funds |
|---|---|---|
| European Union | Generally outside PSD2's licensing | Payment institution or e-money license under PSD2 and the E-Money Directive |
| United Kingdom | Generally outside the FCA's payment licensing | FCA authorization or registration as a payment institution or EMI |
| United States | Generally outside money transmission licensing | FinCEN MSB registration plus state money transmitter licenses |
| India | Defined by the RBI as technology without involvement in funds | RBI authorization as a payment aggregator, unless a bank |
| Pakistan | Licensed: the State Bank licenses PSOs and PSPs that run gateways, which don't hold customer funds | EMI license for businesses holding customer balances |
| Indonesia | Anyone acting as a payment service provider (PJP) needs Bank Indonesia's license first | A PJP license in the category that fits |
Pakistan and Indonesia are the cases to watch. In both, running payment infrastructure can need a license even without holding balances, so check the local definitions before assuming a gateway is unregulated.
How to get a payment gateway license where you need one
The steps follow the same order in most markets, once you know which license applies.
- Map the funds flow: who receives the money, who pays the merchant, and whether you hold balances.
- Identify the license type in each market from that map.
- Set up the local entity, capital and the people the regulator expects.
- Prepare the application, with business plan, safeguarding, AML and IT security.
- Apply, answer the regulator's questions, and launch once authorized.
Step 1 decides everything else. A gateway business that keeps funds with partners can often launch in more markets, faster, than one that settles merchants itself.
When a licensed partner is the faster route
Many gateway businesses never hold a license at all. They run the technology and the merchant relationship while a licensed PSP or bank handles the funds, under a contract that sets out who does what. It costs margin and some control, but it saves the capital and months of applications, and the payment licenses overview shows which markets that model fits.
Questions
Do I need a license to run a payment gateway?
Usually not, if your company only passes payment data and never receives merchants' funds. If you collect and settle funds, you'll need a license or a licensed partner, and some countries, such as Pakistan, license gateway operators either way.
How do I get a payment gateway license?
Work out whether you'll handle funds, identify the license that applies in each market, set up the entity and capital, prepare the application with safeguarding and AML policies, and apply to the regulator.
Does a payment gateway need PCI DSS?
Yes. Any company that stores, processes or transmits card data has to validate PCI DSS compliance, whether or not it needs a payment license.