Market Size, Demand & Growth

The global payment processing solutions market was worth $38.3 billion in 2025 and is forecast to reach $88.4 billion by 2032, a 12.7% compound annual growth rate (Global Industry Analysts via GlobeNewswire, 2026). The United States alone accounted for roughly $11.8 billion of that 2025 figure, the single largest national share.

Those are platform-and-service revenue numbers, not total transaction volume. They matter to a founder because they describe the fee pool that ISOs, payment service providers and gateway vendors compete over, not the trillions in money that flows through the rails. A business plan that confuses gross payment volume with addressable revenue will be marked down by any sophisticated lender or investor, so this distinction sits at the front of every plan we write.

Three demand drivers run through every recent analyst note: real-time and account-to-account payments, embedded checkout inside software platforms, and cross-border commerce that needs multi-currency settlement. The credit-card segment alone is projected to reach $39.9 billion by 2032 at an 11.3% CAGR, while debit grows faster at 12.2%. For a new entrant, the practical read is that horizontal "we process everything" positioning is crowded; the open lanes are vertical specialisation and software-embedded payments where a generalist incumbent has thin coverage.

In the UK and EU, the same demand exists under a different regulatory wrapper. Open banking adoption and PSD2-driven account-to-account rails have created room for payment institutions that never touch a card network. A plan aimed at a UK lender should size the opportunity in that context rather than transplanting US card economics directly.

It is also worth being honest in the plan about who already owns the market. Stripe, Adyen and Checkout.com dominate developer-led online payments; Square and Block own much of the small-merchant in-person segment; Worldpay and the bank-owned acquirers hold the enterprise and high-street base. A new entrant does not displace these players head-on. It finds the merchants those platforms serve generically and serves them specifically. Stating that competitive reality, and then explaining the wedge, signals to a lender that the founder understands the board they are playing on. A plan that claims to compete with Stripe on price is one that experienced reviewers stop reading.

The macro tailwind is real but it is not a strategy. Real-time rails, embedded finance and cross-border commerce all expand the fee pool, yet that same growth attracts capital and compresses rate. The durable advantage in this market has never been being cheapest; it has been being indispensable to a defined set of merchants. Every figure in this section exists to support that single strategic point, and the template is built to make you prove it rather than assert it.

Quick Answers Buyers Search For

These are the questions that show up most often in search around this niche. Short answers here, with the full working further down the page.

How do payment processors actually make money?

On the markup over interchange. The card networks set interchange; the processor and its partners add a margin on top. Under interchange-plus pricing that margin is quoted in basis points, and a slice of it flows back to whoever brought the merchant in. It is a recurring, volume-linked fee, not a one-time sale.

Can you start without becoming a bank?

Yes. The most common entry route is the ISO model, where you resell an acquiring bank's processing under a registered partnership and never hold customer funds. You only step into heavy licensing when you decide to hold or move money yourself.

Where is the margin pressure worst?

Flat-rate retail processing, where Stripe, Square and PayPal have set price expectations. The defensible margin sits in verticals with underwriting complexity, recurring billing, or integration needs that a flat-rate aggregator handles poorly.

How fast can a vertical ISO reach breakeven?

Most reach operating breakeven once the residual book clears roughly 80 to 120 active merchants, which a focused two-person sales effort typically hits inside 12 to 18 months. The worked example later on the page shows the arithmetic.

What It Costs to Launch

A payment processing venture costs roughly $58K to $236K (£45K to £186K) to stand up, and the spread is mostly explained by one decision: do you resell someone else's infrastructure, or build and license your own. A white-label ISO can launch near the floor; a PSP or gateway operator that owns its stack and pursues money transmitter licensing lands toward the ceiling.

Cost breakdown that holds up to scrutiny

The single biggest reason first-time payment plans get rejected is a thin compliance line. PCI DSS is not a one-off purchase. A Level 1 assessment by a Qualified Security Assessor runs $15K to $50K and more for the initial audit, then recurs annually, and the remediation work it surfaces is rarely free. Treat it as a program, with a line in years one through three, not a single setup cost.

• Technology layer: a white-label gateway license avoids most build cost; a proprietary gateway adds engineering payroll and a longer runway before revenue.
• Compliance and security: PCI DSS, penetration testing, and an annual QSA engagement. Budget for the recurrence, not just the first audit.
• Licensing and bonds: if you hold funds, surety bonds and minimum net-worth requirements apply per state in the US, which is the line that scales worst.
• Risk and underwriting: AML/KYC tooling, sanctions screening, and a reserve policy for chargeback exposure.
• Go-to-market: merchant acquisition is the recurring cost that determines how fast the residual book compounds.

SBA & Funding Routes

Payment businesses sit in a financial-services NAICS family that lenders read as services rather than asset-heavy operations. That shapes how you fund them. There is little equipment to pledge as collateral, so lenders weigh the founder's track record, the strength of the acquiring-bank or processor partnership, and the credibility of the residual forecast.

The SBA 7(a) program is the most common government-backed route for a US launch in this space. It supports working capital, technology and licensing spend, and software businesses use it routinely. Because there is no large equipment base to secure the loan, expect lenders to lean on personal guarantees, a documented sales pipeline, and a partnership letter from your processor or sponsor bank. A clean five-year projection that separates one-time launch cost from compounding residual revenue is what moves these applications from "maybe" to "approved."

Beyond SBA debt, the realistic funding stack for this niche looks like this:

• Founder equity and revenue-based finance: common for lean ISOs, where the residual book itself becomes the asset lenders later underwrite against.
• SBA 7(a) working-capital loan: best fit for technology and compliance spend with a documented pipeline.
• Angel or seed equity: appropriate for PSP and gateway models with a real software moat and a larger build.
• UK Start Up Loans: the government-backed Start Up Loans scheme offers up to £25,000 per founder at a fixed 6% rate, useful seed capital for a UK ISO before FCA-regulated activity begins.

Whichever route you choose, the plan needs to show the lender that month-one cash burn is survivable until the residual book crosses breakeven. That is the number underwriters circle.

One nuance specific to payments: the residual book itself is a financeable asset once it exists. Established ISOs routinely borrow against, or sell, their residual streams because the cash flow is predictable and recurring. That means a founder who reaches a few hundred merchants has financing options that did not exist at launch, and the plan can legitimately describe a two-stage funding story: modest seed capital to build the book, then asset-backed finance or a partial residual sale to fund expansion without diluting equity. Spelling out that path shows a lender you understand how value accrues in this specific business, which is exactly the sophistication that separates a funded plan from a rejected one.

How the Money Works

Revenue in this business is the markup over interchange, and the cleanest way to model it is in basis points. Under interchange-plus pricing, a merchant pays the network's interchange rate plus a defined margin. An ISO that places that merchant earns a split of the margin, typically 5 to 25 basis points of processing volume, paid as recurring residual income. A basis point is one hundredth of a percent, so 12 bps on a transaction is 0.12% of its value.

The reason experienced operators love this model is that residuals recur and compound. Unlike a one-time merchant cash-advance commission, every merchant you keep keeps paying. Add a new merchant and you stack revenue on top of the existing book rather than replacing it.

Worked example: a vertical ISO residual book

Suppose you sign 120 merchants averaging $25,000 in monthly card volume. That is $3.0 million processed per month. At a 12 bps residual split, the math is straightforward:

• Monthly residual: $3,000,000 × 0.0012 = $3,600 per month
• Annual residual: roughly $43,200 per year, before any ancillary revenue
• Add gateway SaaS fees: a $20 monthly gateway fee across 120 merchants adds $2,400 per month, or $28,800 a year
• Combined run-rate: about $72,000 a year from a 120-merchant book, growing with every new signing

Net margins of 11% to 32% are realistic once that book matures, because the marginal cost of servicing an existing merchant is low. The first year is usually thin: acquisition cost and compliance spend land before the residuals compound. This is exactly why investors want to see the breakeven merchant count, not just the end-state margin.

Operators add further revenue through hardware sales or leasing, chargeback and dispute management fees, PCI compliance service fees, and premium support tiers. A plan that models only the residual understates the business; a plan that stacks these streams realistically is what earns a higher valuation.

ISO vs PSP vs Gateway

Most confused payment plans we review fail because they pick a label without picking a model. These three are not interchangeable. Your licensing burden, your startup cost, and your revenue share all follow from which one you are. Decide this on page one of your plan.

In practice many modern entrants blend the three: a gateway-plus-ISO hybrid that owns the checkout experience while a sponsor bank holds the funds. That blend keeps licensing light while capturing software margin. Whatever the mix, the plan should state it plainly, because lenders price risk off this choice.

Licensing Across Three Jurisdictions

Licensing is the line that founders most often underestimate and lenders most often probe. The rule of thumb: if you only sell and never hold customer money, the burden is light; the moment you hold or move funds, it becomes the defining cost and timeline of the whole venture.

United States

At the federal level, a money services business registers with FinCEN by filing Form 107 within 180 days of establishment, then renews every two years. Registration is free but it is only a reporting step, not authorisation to operate. The hard part is state-level: a Money Transmitter License (MTL) is required in every state where you transmit money, and once surety bonds and net-worth requirements are counted, each state runs $50,000 to $500,000 and more and takes 6 to 18 months. National coverage means repeating that across most of the country, which is why so many entrants start as ISOs and let a sponsor bank carry the licensing. Layered on top, PCI DSS compliance is mandated by the card networks and your acquirer.

United Kingdom

The Financial Conduct Authority authorises two relevant permissions. An Authorised Payment Institution (API) needs initial capital of roughly €20,000 to €125,000 depending on the services offered, with authorisation taking 6 to 12 months and an annual fee around £1,500. An Authorised E-Money Institution (AEMI), which issues e-money or wallets, needs £350,000 of initial capital, must hold own funds of at least 2% of average outstanding e-money, and takes 6 to 18 months because the FCA scrutinises safeguarding and float projections closely. A Small EMI route exists below €5 million average outstanding e-money and €3 million monthly transactions.

Singapore

Under the Payment Services Act 2019, the Monetary Authority of Singapore (MAS) licenses payment firms as either a Standard Payment Institution or a Major Payment Institution, with base capital from S$100,000 to S$250,000 plus AML/CFT controls and a security audit. Singapore is a common Asian beachhead because the single national regime avoids the state-by-state fragmentation of the US.

The practical takeaway for your plan: pick the lightest model that lets you serve your target merchants, and only step up to fund-holding licenses when the residual book justifies the compliance overhead. We have seen more payment startups stall on premature licensing than on lack of demand.

Mistakes That Sink First-Time Operators

Patterns repeat across the payment plans we are asked to fix. These five account for most of the failures.

• Going national before authorisation. Founders model nationwide revenue while holding one state's MTL. The plan promises volume the licensing cannot legally support yet. Sequence the licensing into the forecast.
• Building a gateway you did not need. A proprietary stack burns runway when a white-label partnership would launch in weeks. Build only if the technology is the differentiator.
• Treating PCI DSS as a checkbox. It is an annual program with remediation cost. A one-line setup figure signals inexperience to any reviewer who knows the space.
• Pricing on the headline rate. Quoting a flat rate while ignoring chargeback exposure, reserves and interchange-plus economics is how operators sign unprofitable merchants. Model net margin per merchant, not gross rate.
• Modelling one-time signings instead of a compounding book. The value of this business is the recurring residual asset. A forecast that treats each signing as a one-off undervalues the venture and misleads the founder about cash flow.

Who You Actually Sell To

The fastest way to lose margin in payments is to sell to everyone. Flat-rate aggregators have already won the long tail of cafes and corner shops by making onboarding instant and pricing predictable. A new entrant that competes there is fighting on the one axis where incumbents are strongest. The plans that fund well pick a defensible buyer and build the whole offer around them.

Three segments tend to produce the best economics for a focused operator, and a strong plan quantifies the size, spending behaviour and switching trigger of each rather than describing them in the abstract.

Notice that none of these segments buy on rate alone. That is the point. When the buyer values underwriting expertise, billing tooling or integration depth, the conversation moves off price and your interchange-plus margin survives. A plan that names its priority vertical, sizes the merchant population, and states the average monthly volume per merchant gives a lender something concrete to underwrite. A plan that says it will serve "small and medium businesses" gives them nothing.

The same discipline applies to geography. A US operator that starts in one or two states where it already holds licensing, then expands as the residual book funds the next state's MTL, tells a far more credible growth story than one promising national coverage from day one. In the UK, a single FCA permission covers the whole country, which is part of why UK launches can scope their addressable market more simply than US ones.

Operations, Risk & the Numbers Underwriters Circle

Payments is a risk business wearing a technology costume. The processor sits between the merchant and the card networks, and when a merchant fails, disappears or commits fraud, the liability flows upstream. A plan that ignores this reads as naive; one that addresses it directly earns trust.

Chargeback and reserve exposure

Every merchant you place carries chargeback risk. If a merchant goes under owing refunds, the processor and its partners can be left holding the bill. That is why sponsor banks impose reserve requirements and why your plan needs a reserve policy: a percentage of volume held back, or a rolling reserve released after a defined period. Model this as a real line, because it directly affects working capital. A merchant doing $25,000 a month with a 10% rolling reserve ties up $2,500 of float per cycle.

Fraud and AML controls

Anti-money-laundering and know-your-customer obligations are not optional once you touch funds. Transaction monitoring, sanctions screening and suspicious-activity reporting are ongoing operating costs, not setup items. The Bank Secrecy Act framework in the US and the FCA's expectations in the UK both assume a living compliance program with a named responsible person. Budget for the tooling and the headcount.

Sponsor-bank dependency

For an ISO, the sponsor bank relationship is the single biggest concentration risk. If the bank exits a vertical or tightens underwriting, your pipeline can stall overnight. A credible plan names a primary sponsor relationship and a contingency, and treats the partnership terms (revenue split, exclusivity, exit clauses) as core economics rather than boilerplate.

Uptime and PCI scope

Merchants leave processors that drop transactions. Service-level commitments, redundancy and a documented PCI DSS scope are operational table stakes. The narrower you can keep your PCI scope, often by tokenising and never storing raw card data, the cheaper and faster your annual assessment becomes. This is a design decision worth making early, and worth stating in the plan because it materially lowers the recurring compliance line.

Underwriters reading the plan will circle three numbers: monthly burn before breakeven, the breakeven merchant count, and the reserve-adjusted working-capital need. Put those three figures in plain sight and the financing conversation gets dramatically easier.

There is also a quieter operational risk that rarely appears in first drafts: concentration. If a handful of large merchants make up most of the processed volume, the loss of one of them can swing the business from profit to loss in a single month. A mature plan reports the share of volume from the top five merchants and sets a target ceiling, the same way a lender would assess customer concentration in any other business. Diversifying the book is not just good practice; it is what makes the residual stream financeable later.

Building the Residual Book

Acquisition is the engine of this business. Because revenue compounds, the cost and pace of signing merchants determines everything downstream. The plan should treat merchant acquisition as a measured channel with a cost per acquisition and a payback period, not as a vague "we will do marketing" line.

• Vertical referral partnerships: in healthcare, legal or SaaS, a relationship with an industry association, practice-management vendor or accountant network produces warm, high-retention merchants. This is the channel that defends margin.
• Embedded and ISV partnerships: integrating into a software platform turns its customer base into your pipeline and produces stickier merchants than cold outbound ever will.
• Direct field sales: still effective in verticals where trust and underwriting expertise matter, though the cost per signing is higher and the ramp is slower.
• Content and search: ranking for the specific problems your vertical merchants face brings inbound leads at a low marginal cost once it compounds, mirroring the residual model itself.

Retention deserves as much attention as acquisition. A residual book leaks value through attrition, so the plan should set a target monthly churn and the tactics to hold it down: responsive support, proactive PCI help, and billing tooling that reduces involuntary churn. Reducing merchant attrition by even one percentage point a month meaningfully changes the five-year value of the book, and sophisticated investors know to ask for that number.

Sample Plan Preview

This is an extract from a sample payment processing solutions plan, redacted and shortened, to show the tone and the level of financial detail a funder expects.

What's in the Template

The free download is a structured Word document built specifically for payment processing ventures, not a generic shell. Sections are sequenced the way lenders and the SBA read them.

• Executive summary framed around your chosen model (ISO, PSP or gateway) and funding ask
• Market analysis with the $38.3B sizing and the vertical-specialisation thesis built in
• Business model section that forces a clear ISO/PSP/gateway decision
• Revenue model with a basis-point residual calculator structure and ancillary streams
• Compliance and licensing plan covering FinCEN, state MTLs, PCI DSS, and FCA/MAS routes
• Five-year financial projections separating one-time launch cost from compounding residuals
• Risk register covering chargebacks, reserves, fraud and sponsor-bank dependency
• Funding request structured for SBA 7(a), Start Up Loans, or equity reviewers

If you would rather not write it yourself, our research and content service fills the narrative and data for you, or a bespoke plan delivers the whole document with a five-year model. You can also browse the full free business plan templates library or compare with the related digital payment business plan template.

The Terms Your Plan Needs to Use Correctly

Reviewers in this space spot imprecise language fast. Using these terms correctly in the plan signals that you understand the mechanics rather than the marketing.

• Interchange: the fee set by the card networks (Visa, Mastercard) and paid to the card-issuing bank on every transaction. You do not control it; you price on top of it.
• Interchange-plus pricing: a transparent model where the merchant pays interchange at cost plus a defined markup. It is the model sophisticated merchants prefer and the one your residual is calculated from.
• Basis point (bps): one hundredth of one percent. Residual splits and markups are quoted in bps; 25 bps is 0.25% of processed volume.
• Residual: the recurring share of the markup paid to the party that placed and services the merchant. The compounding residual book is the core asset of an ISO.
• Acquiring bank (acquirer): the bank that holds the merchant account and settles funds. ISOs operate under an acquirer's sponsorship.
• Sponsor bank: the regulated institution that lets an ISO or PSP operate under its licensing and bears ultimate liability, in exchange for a share of economics.
• Chargeback: a forced reversal of a transaction initiated by the cardholder's bank. Excessive chargebacks trigger fines and reserve increases.
• PCI DSS: the Payment Card Industry Data Security Standard. Mandatory, audited annually at higher volumes, and a recurring cost rather than a one-off.

Frequently Asked Questions

Useful Links & Resources

These links were preserved from the live page so important references and partner links are not lost during the page refresh.

• Facebook
• Instagram
• LinkedIn
• YouTube