A payment processing company makes money by moving other businesses' payments and keeping a slice of each one. It sounds like a software business, and part of it is. The rest is regulation, bank relationships and risk management, and those parts decide how fast you can open and whether you survive your first fraud wave.
This guide covers how to start a payment processing company from the first decision to the first live merchant. It explains the business models to choose from, what each needs in licenses and partners, how the money works and the order in which the work has to happen.
Choose your payment gateway business model first
"Payment processing company" covers four quite different businesses. Pick one before anything else, because it decides your license, your partners and how much capital you need.
| Model | What you do | What you need first |
|---|---|---|
| ISO or agent | Sell another company's processing and earn residuals | A sponsoring acquirer or processor that registers you |
| Payment facilitator | Sign merchants under your master account | A sponsoring acquirer, scheme registration, underwriting |
| PSP with its own gateway | Sign merchants, run your gateway, settle with acquirers | A payment license where required, acquirer contracts, software |
| Processor or acquirer | Connect to card schemes, acquire payments directly | Scheme membership or sponsorship, a banking or payment license, heavy capital |
Many founders start in the middle two rows. The first is a sales business with lower margins, and becoming a payment processor, the last row, is usually a path for banks and well-funded companies.
How hard is it to start an independent payment processor?
Harder than most software startups, mainly because of three gates that don't depend on your product. A regulator has to authorize you if you'll hold or move merchant funds. Acquirers have to accept you, and they review your ownership, compliance and business model before signing. And your environment has to pass a PCI DSS assessment before live card data touches it.
None of these gates moves faster because the code is ready. Starting them early is the single most useful thing a founder can do.
How to start a payment processing company, step by step
The order below keeps the slow, external work running while the internal work gets done, whether you're starting a credit card processing company or a broader PSP. It applies to the PSP and payment facilitator models most founders pick.
- Choose the model, the first market and a merchant niche you can actually reach.
- Check the license that model needs in that market, and apply or line up a licensed partner.
- Approach acquirers early, with a clear compliance plan and target merchant profile.
- Decide whether to build or license the gateway and merchant back office.
- Set up compliance: AML program, KYB procedures, risk policies, PCI DSS plan.
- Hire the core team: risk and onboarding, compliance, finance operations, sales, support.
- Test with acquirers, pass certification and your PCI DSS assessment.
- Sign the first merchants, keep the group small and watch their first settlements.
Steps 2 and 3 set your launch date. Steps 4 and 6 set your costs.
How a payment processing company makes money
Revenue comes from the gap between what merchants pay and what processing costs you. A merchant pays a rate per transaction, plus fees such as setup, monthly or chargeback fees. You pay interchange to the card issuer, scheme fees to the card networks and the acquirer's margin.
Take a hypothetical PSP with 300 merchants, each processing $40,000 a month, so $12 million a month in total. At a net margin of 0.4 percentage points after interchange, scheme and acquirer costs, it earns $12,000,000 x 0.4% = $48,000 a month, or $576,000 a year, before its own costs.
That's why volume and merchant retention matter more than headline rates, and why it pays to know where each slice of processor revenue comes from.
What it costs to start
Costs fall into licenses and legal work, capital requirements, compliance, people and software. Software is the line you control most, since building a gateway yourself is a year or more of engineering while licensing it takes days to weeks.
People are the largest ongoing cost whichever way you go, since onboarding and risk staff, compliance, finance operations and support all grow with the merchant base. Licenses and capital add to the startup cost before the first merchant pays you.
Where software fits
A payment processing company needs a gateway that connects to acquirers and payment methods, a checkout for merchants, a vault for card data, routing between acquirers and a merchant back office for onboarding, pricing, settlements and reconciliation.
Our white label gateway covers that whole software layer under your brand, with 700+ ready connectors and a merchant management system. On SaaS, processing can start in about 5 business days on average once the connectors you need exist, which takes software off your critical path. The license, the acquirer contracts and the merchants stay yours, since we don't take part in the flow of funds.
Questions
How do I start a payment processing company?
Choose a model and a first market, sort out the license and acquirers early, decide whether to build or license the software, set up compliance and the core team, pass certification and PCI DSS, then launch with a small group of merchants.
Is a payment gateway business profitable?
It can be, at scale. Margins per transaction are small, so profit depends on volume, merchant retention and keeping fraud and chargeback losses under control.
Do I need a license to start a credit card processing company?
Usually, if you hold or move merchant funds. ISOs and agents work under a sponsoring acquirer's registration, while PSPs and payment facilitators need their own license or a licensed partner, depending on the country.
How would you start an international online payment processing company?
Start in one market and build the license, acquirers and local payment methods there first. Add countries one at a time, since each brings its own license question, acquirers and methods.