Skip to content

Launch a PSP

Launch a PSP: Business Guides for New Payment Companies

These guides are for founders who want to launch a PSP, a payment facilitator or a payment processing company, and for teams inside banks and platforms planning the same move. Each one takes a single question, from licenses and acquirers to budgets and dates, and answers it with public figures where they exist.

We sell the software side, so these business guides for new payment companies treat software as one track among several. In most launches it isn't the slowest one.

Pick the business before the plan

"Payment processing company" can mean an ISO, a payment facilitator, a PSP with its own gateway or a processor connected to the card networks. To start a payment company of any of these kinds, begin with the payment business guide, which compares the four and sets the order of work.

Launch a PSP in the regulated sense

A PSP that handles merchants' money usually needs a license, and the frameworks differ by market, from EU payment institutions to India's aggregator authorization. The guide to becoming a PSP covers the license types and what an application contains.

Skip the build

Licensed gateway software takes the engineering off your critical path. Software is the fast part. The license and the compliance team stay yours, and the guide to launching without building a gateway compares three routes to market.

Run sub-merchants as a payment facilitator

Visa treats a company as a payment facilitator if it signs sellers for an acquirer or receives their settlement funds, even if it does only one of the two. Read about sponsors and Visa's US$1,000,000 threshold in the payment facilitator guide.

Go further down the stack

Processing at card network level is a different business. It needs scheme membership or a sponsor, plus a yearly Report on Compliance, and few companies ever need to become a processor in that sense, because a PSP working through acquirers that already hold network connections reaches merchants years sooner and with far less capital.

Plan the first 90 days

The license and acquirer tracks start on day one because they run on other people's calendars. Start both early. Our 90-day plan splits the first three months into parallel columns of work.

Know what each market asks for

Kuwait's central bank sets out seven license types for electronic payments, and Pakistan's approves gateways in three stages. The requirements guide lists what every market asks for, with those two in detail.

Write the business plan

In the EU, a payment institution's plan forecasts three financial years with target and stress scenarios. Our business plan template includes a worked forecast and the merchant count needed to break even.

Budget the first year

People cost more than code. On licensed software, the operations team is often the largest first-year cost, and the startup cost breakdown prices a lean team at US median wages and sets it beside published software plans, so you can see how far apart the two lines sit before you raise money.

Set realistic dates

A complete UK application gets an FCA decision within three months under the Payment Services Regulations 2017. Most delays are sequencing. The launch timeline shows where the weeks go and which ones you can win back.

Settle the software track early

Once the software is chosen, one of the three launch tracks is done.