Skip to content

Launch a PSP

Payment Gateway Business Plan: Template and Example

A payment gateway business plan has two readers. Investors want to know whether the business can make money. Regulators and acquirers want to know whether it can survive a bad year without losing merchants' funds. A plan written only for the first reader usually fails the second, so it pays to write for the regulator from the start.

In the EU, the regulator's expectations are written down. The European Banking Authority's guidelines on authorizing payment and e-money institutions (EBA/GL/2017/09) list what a business plan should contain, and national authorities apply them. This page turns that list into a template and works through a three-year example.

What a payment gateway business plan has to show

Guideline 4 of the EBA guidelines asks for a marketing plan and a forecast, and it's specific about both. The marketing plan covers your competitive position in the payment segment you're entering, who your payment service users are, and how you'll reach them.

The forecast is where most of the work sits. It covers the first three financial years and has to show you can run "appropriate and proportionate systems, resources and procedures". That means an income statement and a balance sheet forecast with target and stress scenarios, the assumptions behind them, an explanation of the main income and cost lines, and a cash flow breakdown for the same three years.

Capital comes on top. The plan states your own funds and the initial capital you'll hold, and projects your minimum own funds for each of the three years. Under Article 7 of PSD2, a payment institution offering services such as acquiring payment transactions must hold initial capital of at least EUR 125,000.

A PSP business plan template

The template below follows the EBA list and adds the sections acquirers ask about in due diligence. Fill in each row with your own numbers and sources.

Section What to write Where the numbers come from
Summary The model, the market, the merchants you'll serve and what you need The rest of the plan
Market and competition Your segment, the PSPs already in it and why merchants would switch Market data, competitor pricing pages
Merchants and channels Who you'll sign, by industry and size, and how you'll find them Your pipeline, partner agreements
Services and pricing Payment methods, markets, fees per merchant group Your price list, acquirer costs
Operations Onboarding, underwriting, monitoring, settlement and support Your policies and staffing plan
Technology Gateway software, hosting, security, outsourcing arrangements Vendor contracts, PCI DSS plan
Compliance AML program, safeguarding, named responsible officers Your policies
Three-year forecast Income statement, balance sheet, cash flows, target and stress cases Your assumptions, stated line by line
Capital Initial capital, own funds and how they're projected The license rules in your country

The forecast row decides whether the rest is believed. Every number in it should trace back to an assumption written down beside it, such as merchant count or margin.

Example: a three-year forecast

Here's a hypothetical PSP to show how the assumptions turn into revenue. It signs small and mid-sized merchants processing $30,000 a month on average, earns a net margin of 0.30% after interchange and acquirer costs, and charges a $25 monthly fee.

Assumption or line Year 1 Year 2 Year 3
Active merchants, average 40 120 250
Processing volume (merchants x $30,000 x 12) $14.4 million $43.2 million $90 million
Margin revenue at 0.30% $43,200 $129,600 $270,000
Monthly fees ($25 x 12 x merchants) $12,000 $36,000 $75,000
Total revenue $55,200 $165,600 $345,000

Each merchant brings in $1,380 a year. That's $1,080 of margin plus $300 of fees. The stress case changes two assumptions: merchant count 30% lower and margin down to 0.22%. In year three that gives 175 merchants, $63 million of volume, $138,600 of margin revenue and $52,500 of fees, so $191,100 in total.

Checking the forecast against costs

A plan reads as credible when its revenue is set against realistic costs. Our startup cost breakdown puts a lean four-person operations team at about $358,571 a year with benefits, at US median wages, and the lowest published software plan at about $17,000 for the first year.

Against those two lines, $375,571 a year in all, this PSP breaks even at about 273 merchants, because $375,571 / $1,380 = 272.2. The target case reaches 250 merchants in year three and still falls just short.

That isn't a flaw in the example. It's the point a regulator looks for, and the plan should say how the gap closes, whether through larger merchants, more revenue lines or the capital to carry the company until it does.

Payment gateway business plan PDF

Most people looking for a payment gateway business plan PDF want a finished file to copy. A downloaded template won't match your regulator's list or your own numbers, though. Build the plan from the sections above, keep the forecast in a spreadsheet so the assumptions stay editable, and export the written plan to PDF when you file it.

Where the software appears in the plan

Technology shows up twice. It's a cost line in the forecast, and it's a section the regulator reads for security and outsourcing.

On licensed software, that section describes the vendor rather than your own engineering. Our white label gateway runs on SaaS under our PCI DSS Level 1 certification, with a 99.95% uptime SLA, or self-hosted in your own cloud account or on your own servers if your regulator prefers.

Ask your vendor early for the security and outsourcing documents the application needs, because a regulator reviewing an outsourced gateway will read them as closely as your own policies, and on self-hosted setups we support your PCI DSS audit.

Questions

What should a payment service provider business plan include?

A marketing plan with your competitive position and channels, a three-year forecast with income statement, balance sheet, cash flows and stress scenarios, and your capital and own funds. In the EU, the EBA's authorization guidelines set out this list.

How many years should the forecast cover?

Three financial years, under the EBA guidelines for EU payment and e-money institution applications, with a cash flow breakdown for each year.

What's a stress scenario in a PSP business plan?

A version of the forecast where key assumptions go wrong, such as fewer merchants or lower margins. It shows whether your capital and costs still let you operate and protect merchants' funds.

How much capital does a payment gateway business plan need to show?

It depends on the license. Under PSD2, a payment institution that acquires payment transactions needs at least EUR 125,000 of initial capital, on top of the cash it needs to reach break-even.

Add the software line to your plan

Tell us your market, your hosting preference and the merchant volume in your forecast.