A payment gateway business model is how a gateway operator makes money: a markup and service fees on every online payment, charged on top of pass-through interchange and card scheme fees. This guide is for payment service providers (PSPs), acquiring banks and fintechs that need to price a gateway, cost it and choose an operating model.
Who Gets Paid in an Online Card Payment?
Four parties share the fee your merchant pays on a card payment. The issuer receives interchange, the card scheme receives scheme fees, the acquirer keeps its markup and you keep the gateway fee. Only the gateway fee is your revenue. The other three parts are costs that pass through to the parties that earn them.
Fee component
Who receives it
Who sets it
What you can do about it
Interchange
The card issuer
The card scheme, within legal caps where they exist
Route each card to the acquirer where its interchange category costs least
Scheme fees
Visa, Mastercard and other card schemes
Each scheme, by region, card type and transaction type
Ask your acquirer for the fee tables and pass the fees through at cost
Acquirer markup
The acquiring bank
You and the acquirer, in your contract
Negotiate it down as your volume grows and connect more than one acquirer
Gateway fee
You
You, in your merchant contract
Choose the pricing model and the services you charge for
Where interchange is capped
EU: the Interchange Fee Regulation, Regulation (EU) 2015/751, caps interchange at 0.2% of the transaction value for consumer debit cards and 0.3% for consumer credit cards. The caps do not apply to commercial cards or to three-party card schemes, where the scheme itself issues and acquires, and a member state may set lower caps for domestic transactions.
Cards issued outside the European Economic Area (EEA): in April 2019 the European Commission made commitments by Visa and Mastercard binding. For online payments in the EEA with these consumer cards, interchange was capped at 1.15% for debit and 1.50% for credit. The commitments were set to apply for five years and six months, so ask your acquirer for the rates in force today.
US debit: under Regulation II, the cap for an issuer with assets of $10 billion or more is $0.21 plus 5 basis points (0.05%) of the transaction value, plus $0.01 for fraud prevention (Federal Reserve). Smaller issuers are exempt, and the regulation covers debit cards only.
US debit cards show the proportions. In 2023, interchange paid to issuers totalled $34.12 billion, and acquirers and merchants paid another $8.40 billion in network fees, the US term for scheme fees, according to the same Federal Reserve report. Neither amount is revenue for a gateway.
Two details decide what each payment costs you. Interchange depends on where the card was issued, so BIN routing, routing by the card’s bank identification number, sends each card to the acquirer where it costs least. Check your acquirer contract too: authorisations, captures, refunds and chargebacks are separate card transaction types, and each may carry its own fee.
Blended vs Interchange++: Which Pricing Model Should You Sell?
Sell Interchange++ (IC++) when you want the same margin on every payment, and a blended rate when your merchants want one predictable price. Under IC++ the merchant carries every change in interchange and scheme fees. Under a blended rate you carry it, so your margin moves with the card mix.
In the EU, the law sets the default. Under Article 9 of the Interchange Fee Regulation, an acquirer offers and charges merchant service charges, the fees a merchant pays its acquirer, specified separately for card categories and brands with different interchange levels, unless the merchant asks in writing for a blended charge. The acquirer’s agreement also shows the merchant service charge, interchange and scheme fees separately.
Model
How your merchant pays
Who carries cost variation
Fits
Watch out for
Interchange++ (IC++)
Actual interchange, plus actual scheme fees, plus your fixed markup
The merchant
Larger merchants that want to see each component
Statements are harder for small merchants to read
Blended
One rate for all cards, or one rate per card category
You
Small merchants that want a predictable fee
You absorb the gap when costly cards dominate
Subscription plus fixed fee
A monthly platform fee and a fixed fee per payment; the acquirer bills the card costs to the merchant
The merchant, in its acquirer contract
Technical PSPs whose merchants hold their own acquirer contracts
Your revenue does not grow with the payment amount
Interchange vs markup: which part is your revenue?
Interchange goes to the issuer and scheme fees go to the card scheme; both pass through you. Your revenue is only the markup you add on top, whether it is shown separately under IC++ or hidden inside a blended rate. When you plan margins, model the markup alone and treat interchange and scheme fees as cost. How and when the money reaches the merchant is covered in our guide to payment settlement.
A blended rate earns you more on cards with low interchange and less on costly ones, such as commercial cards and cards issued outside the EEA.
Two related topics have their own guides. Keeping rates and fees for each merchant is part of merchant management. Our guide to white-label credit card processing covers tiered pricing and residuals, the recurring share of margin paid to independent sales organisations (ISOs).
What Are the Revenue Streams of a Payment Gateway?
You earn from three layers: a markup on each payment, recurring fees for access to the platform, and paid services such as fraud screening, 3-D Secure, currency conversion, payouts and dispute handling. You set each price per merchant, by volume, risk profile and the services included.
Revenue stream
How you charge it
What the price depends on
Transaction markup
A percentage, a fixed fee or both, on each payment
Merchant volume, risk profile and card mix
Setup and platform fees
One-off at integration, then monthly
The integration work and the services included
Currency conversion (foreign exchange, FX)
A markup on the exchange rate
The currency pair and the share of cross-currency volume
Disputes and chargebacks
A fee per dispute
Your handling effort and the merchant’s dispute ratio
Fraud screening
Per screened transaction or monthly
Screening depth and what your fraud vendor charges you
3-D Secure (3DS) authentication
Per authentication request
Authentication volume and the cost of your 3DS server
Routing and cascading
Per transaction, or included in a higher plan
The number of acquirers you connect for the merchant
Tokenization
Per stored card or per tokenized payment
The number of cards the merchant keeps on file
Payouts
A percentage of the payout or a fixed fee
Payout speed and the payout method
You do not have to build each service to sell it. On eComCharge, the automatic currency converter lets you choose the exchange rate source and add your own markup to the base rate. The platform also includes integrated anti-fraud tools that you can offer to your merchants.
Routing and stored cards work the same way. Payment routing sends each payment to one of several acquirers by rules you define, and cascading logic retries a declined payment through the next one. Card tokenization replaces the card number with a token, so your merchants can charge returning customers without storing card data.
What Does It Cost to Run a Payment Gateway?
Your costs fall into two groups: pass-through costs that you collect from merchants and hand on, and your own operating costs. The platform, PCI DSS, staff and the losses you cannot recover from merchants make up the second group. The platform decision moves it most.
Your PCI DSS cost depends on your level. Under Visa’s service provider rules, a provider that stores, processes or transmits 300,000 or more Visa accounts or transactions a year is Level 1. It validates compliance every 12 months with an Attestation of Compliance from a Qualified Security Assessor (QSA).
Pass-through costs
Interchange, paid to issuers
Scheme fees, paid to card schemes
The buy rate: what your acquirer charges you for each payment
Fees of alternative payment methods, paid to their operators
Your own operating costs
Platform: an in-house team, a licence or a white-label subscription
Hosting, monitoring and security tooling
PCI DSS: controls, penetration tests and the yearly validation
Licensing, AML and KYC, and compliance staff
Fraud screening and 3DS vendor fees
Support, risk, sales and dispute handling staff
Fraud and chargeback losses you cannot recover from merchants
Build, rent or host: how the platform route changes your costs
Platform route
Time to a working platform
What you pay for
PCI DSS work on your side
Build in-house
12 months to 2 years (our estimate)
An engineering team, hosting, security tooling and certification
All of it: you are the service provider
Rent as software as a service (SaaS)
On eComCharge: installation from 1 week
Setup, maintenance and transaction fees to the vendor
Your own processes, staff and any systems you run; the vendor validates its platform
PCI DSS stays a shared responsibility on every route. Outsourcing PCI DSS to a vendor reduces your scope and does not remove it. Our guide on how to choose a white-label payment platform lists the questions to ask each vendor about scope, deployment and exit.
How Do the Unit Economics of a Payment Gateway Work?
Unit economics compare what you keep on each payment with what that payment costs you to handle. In the illustrative model below, a technical PSP with 50 merchants keeps €90,000 of net revenue a month and €15,000 of operating profit. Net revenue is what stays after interchange and scheme fees pass through.
Note
Illustrative model, not eComCharge data or pricing, and not market rates. Every figure below is a hypothetical assumption chosen to show how the arithmetic works. Replace each one with your own acquirer buy rate, platform cost and salaries.
Illustrative assumptions: you run a technical PSP on a white-label platform and sell IC++ pricing. The acquirer contract is in your name at a buy rate: the acquirer settles to your merchants and pays you your margin, so you never hold funds. You have 50 live e-commerce merchants, each processing €200,000 a month at a €50 average payment. 10% of volume needs currency conversion, 0.3% of transactions are disputed and you employ 8 people.
8 people × €5,000: support, risk, compliance, sales
−€40,000
PCI DSS, audit, legal, insurance
Spread evenly over the year
−€5,000
Operating profit
≈0.15% of volume, ≈17% of net revenue
€15,000
The model stops at operating profit: it leaves out tax, the cost of capital and any fraud loss you cannot recover from a merchant. Before you rely on it, replace the assumptions with your own figures. Your platform’s transaction statistics give you real volumes, average payment values and dispute counts for each merchant.
Which Payment Gateway Business Model Should You Choose?
Choose by one question: will you hold merchant funds? If not, you run a technical PSP and earn fees for processing. If you do, you run an aggregator or a payment facilitator (PayFac). You then control payouts and pricing, and you take on a licence and the liability for your merchants.
In the EU, the law draws this line. Article 3(j) of PSD2, the second Payment Services Directive, excludes technical service providers that never enter into possession of the funds. A payment institution that acquires payment transactions holds initial capital of at least €125,000 under Article 7. An electronic money institution (EMI) holds at least €350,000 under Article 4 of the second Electronic Money Directive.
Model
Who settles to the merchant
Licence or registration
What you earn
Main risk
Technical PSP
The acquirer, directly
No payment licence in the EU; PCI DSS validation
Transaction and service fees, or a markup over a buy rate when the acquirer contract is in your name
You depend on acquirers for merchant approval and pricing
Licensed aggregator
You, from safeguarded accounts (accounts that keep merchant funds apart from your own)
A payment institution or EMI authorisation
The full spread over your buy rate, plus payout and FX fees
Merchant fraud and chargebacks land on you
PayFac
You, with funds received from the acquirer that registered you
Registration with the scheme by your acquirer, plus the authorisation your jurisdiction requires for holding merchant funds
The spread over the acquirer’s buy rate
The acquirer answers to the scheme for you and passes that liability on by contract
ISO
The acquirer; you never receive settlement funds
Registration as the acquirer’s agent
A residual: a share of the acquirer’s margin
Little control over product and pricing
Payment orchestration
Each connected provider
No payment licence in the EU while it holds no funds; PCI DSS validation
Payment orchestration is a layer that routes payments across several providers without settling funds itself.
Note
You may not need a gateway business at all. If you only want to sell an acquirer’s merchant accounts, start a credit card processing company as an ISO. If payments are a feature of your software product, a SaaS payment platform setup with a partner is the simpler option.
You can start as a technical PSP and apply for a licence once your volume justifies the capital and the compliance team. Our guide to starting a payment processing company sets out the steps of that path.
Volume per employee, your markup and your acquirer buy rate move your margin most, because under IC++ interchange and scheme fees pass through. In the illustrative model above, the business breaks even at about 38 merchants. At 100 merchants it earns almost four times the baseline profit, even with four more staff.
You can reproduce each row below with the sliders of the calculator above.
Scenario (illustrative model, one change at a time)
Net revenue per month
Operating profit per month
Baseline: 50 merchants, 0.40% markup, 8 staff
€90,000
€15,000
40 merchants
€72,000
€2,600
100 merchants and 12 staff
€180,000
€57,000
Markup of 0.30%
€80,000
€5,000
Markup of 0.50%
€100,000
€25,000
10 staff
€90,000
€5,000
Break-even sits at about 38 merchants, or €7.6 million of monthly volume, in this illustrative model.
Four levers you control
In the same illustrative arithmetic, each 0.05 percentage points of markup or buy rate on €10 million of volume is worth €5,000 a month, the same as one employee.
Volume per employee: automate merchant onboarding, payment reconciliation and reporting before you hire. One PSP in our case studies tripled its transaction volume in a year without adding infrastructure.
Approvals: a declined payment earns you no percentage markup. Intelligent payment routing and cascading give each payment a second route to an approval.
Buy rate: renegotiate the acquirer’s markup when your volume grows, and connect a second acquirer so you can compare.
Service mix: sell fraud screening, 3DS, FX and payouts as separate lines, so your income does not rest on the markup alone.
What Should a Payment Gateway Business Plan Include?
A payment gateway business plan covers nine parts: target merchants, the operating model and funds flow, partners, licensing, technology, pricing, the team, a financial model, and risks with the metrics you will report. Acquirers and regulators read it before they agree to work with you.
For a licence, the plan is a legal requirement. Under Article 5 of PSD2, an application to become a payment institution includes a business plan with a forecast budget for the first three financial years. It also includes a programme of operations and evidence of initial capital.
Market and target merchants
Name the industries, merchant sizes and countries you will serve, and say why their current providers serve them badly.
Operating model and funds flow
State whether you or the acquirer settles to merchants, and who carries chargeback liability at each step.
Partners
List your acquirers, alternative payment methods, and fraud and 3DS providers, with the status of each contract.
Licensing and compliance
Name the payment service licences you need, your PCI DSS level, your AML and KYC programme and the officers responsible.
Technology
Say whether you build or rent the platform, with the cost, the timeline and the split of PCI DSS scope with your vendor.
Pricing
Choose blended or IC++, list your service fees and compare them with what your target merchants pay today.
Team
Cover compliance, risk and underwriting (the checks you run on a merchant before you accept it), payment operations, sales, support and integration.
Financial model
Build unit economics like the example above, then add the monthly ramp-up of merchants and volume, the break-even month and the cash you need until then.
Risks and metrics
Pair each risk with a mitigation, and report processed volume, net revenue as a share of volume, approval rate, chargeback ratio and the cost of acquiring a merchant.
The main risks are a thin margin under price pressure, dependence on your acquirers, liability for your merchants’ fraud and chargebacks, fixed compliance costs and rule changes that reset your costs. You can reduce each one, and you cannot hand any of them over in full to a vendor.
Risk
What happens
How you reduce it
Price pressure
IC++ makes your markup easy to compare, and large merchants negotiate it down
Earn on services as well as the markup, and track profit for each merchant
Acquirer dependency
One acquirer ends the contract or degrades, and a whole merchant portfolio stops processing
A merchant cannot cover its chargebacks. If the acquirer contract is in your name or you hold funds, the loss moves to you. If your merchants contract with the acquirer directly, the acquirer carries it and you lose the merchant’s fees
Underwrite merchants before you accept them, hold reserves (a part of each payout kept back to cover disputes) and set transaction limits
Compliance cost
PCI DSS validation, AML and licensing are largely fixed costs: they do not shrink in proportion when your volume is low
Rent a platform whose vendor already validates at Level 1, and plan the cost into your break-even
Scheme monitoring
The schemes track your merchants’ fraud and dispute ratios through your acquirer
Interchange caps and licensing rules change, and your costs change with them
Price on IC++ so that interchange changes pass through, and keep a repricing clause in merchant contracts
Fraud is the risk to size first. On US debit cards from large issuers, fraud losses to all parties were 17.6 basis points of transaction value in 2023, and merchants absorbed 49.9% of them, according to the Federal Reserve. One basis point is 0.01%. If you hold funds, a merchant’s unpaid share becomes yours.
EU licensing rules are changing too. The Council adopted its first-reading position on PSD3, the directive that will replace PSD2 and the second Electronic Money Directive, on 29 October 2026. Check your licence plan against the final text once it is adopted.
How eComCharge Supports Your Payment Gateway Business Model
eComCharge develops a white-label payment gateway for PSPs and acquiring banks. You rent it as SaaS, with installation from 1 week, or run it on your own servers, with installation from 3 months or a lifetime licence.
PCI DSS Level 1 compliance, with annual security audits since 2012.
170+ connectors with banks and payment methods, and new connectors developed on request.
Smart Routing with 50+ routing conditions for sending payments across your acquirers.
An in-house 3DS Server certified by Visa, Mastercard and UnionPay.
An automatic currency converter with your own exchange rate source and markup.
A payment gateway charges merchants a markup on each payment: a percentage, a fixed fee per transaction or both. Interchange and card scheme fees pass through to the issuer and the card scheme. On top of the markup, the gateway earns setup and monthly platform fees and sells paid services such as fraud screening, 3-D Secure, currency conversion, payouts and dispute handling.
Under Interchange++ (IC++), the merchant pays the actual interchange and the actual scheme fee for each transaction plus a fixed markup from the provider, so every cost is visible and the provider's margin stays the same. Under blended pricing, the merchant pays one rate and the provider absorbs the variation in card costs. In the EU, Article 9 of the Interchange Fee Regulation makes unblended charges the default unless the merchant asks in writing for a blended one.
The fee a merchant pays has four parts: interchange for the card issuer, scheme fees for card schemes such as Visa and Mastercard, the acquirer's markup, and the gateway or PSP fee. In the EU, Regulation (EU) 2015/751 caps interchange at 0.2% for consumer debit cards and 0.3% for consumer credit cards.
It depends on the platform route and on whether you hold merchant funds. We estimate 12 months to 2 years for an in-house build, followed by a permanent engineering team and your own PCI DSS validation. Renting a white-label gateway replaces most of that with platform fees. eComCharge pricing depends strictly on your specific needs, so contact our sales team for a quote. An EU payment institution that acquires payments also holds initial capital of at least €125,000.
Not if you only handle the technical side. In the EU, Article 3(j) of PSD2 excludes technical service providers that never enter into possession of the funds. You still need PCI DSS validation and acquirer contracts. If you collect merchant funds into your own accounts and pay merchants out, you need authorisation, for example as a payment institution. We estimate that licensing typically takes six months to one year.
There is no single figure: the margin depends on your volume, your markup, your acquirer buy rate and your team size. Interchange and scheme fees pass through, so they are not part of it. In this guide's illustrative model, a technical PSP with 50 merchants keeps 17% of its net revenue as operating profit and breaks even at about 38 merchants. Those inputs are assumptions, not market data.
A payment gateway is the technology that captures a payment and passes it to an acquirer for authorisation by the issuer. A PSP packages a gateway with acquirer connections, payment methods and merchant services. A PayFac signs merchants on behalf of an acquirer and receives and distributes their settlement. An ISO is a sales agent of an acquirer: it earns a share of the margin and never processes transactions or receives settlement funds.
A payment gateway business plan covers the target merchants and markets, the operating model and funds flow, acquirer and payment-method partners, licensing and compliance, the technology choice, pricing, the team, a financial model with a break-even volume, and the main risks with the metrics you will report. An EU payment institution application also needs a forecast budget for the first three financial years.
The main downsides are a thin margin under price pressure, dependence on acquirers and card schemes, liability for your merchants' chargebacks and fraud, and the fixed cost of PCI DSS, AML and licensing. Several acquirers, merchant underwriting, reserves and transaction limits reduce these risks. None of them can be handed over to a vendor in full.
Respectfully, the eComCharge Team
eComCharge develops and delivers the PCI DSS Level 1 certified white-label payment platform for Payment Service Providers and Payment Orchestration.
How PSPs and acquirers process high-risk card payments: which merchants count as high risk, who carries the liability, Visa VAMP thresholds, reserves and limits, the gateway features you need, multiple acquirers and the risks.
A practitioner's guide to launching a payment service provider: choosing a model, signing an acquirer, licensing, PCI DSS, platform choice, cost drivers and a 9-step launch plan.
How PSPs, acquiring banks and EMIs onboard high-risk merchants: which MCCs count as high risk, the KYB, UBO and sanctions checks EU law requires, underwriting and reserves, Visa registration and monitoring, what to automate and how to keep an evidence trail.
How a PSP protects itself from a sudden acquirer shut-off, outage or limit change: concentration risk, scheme and underwriting triggers, backup acquirers, portable tokens, volume split, an outage runbook, costs and who does not need it.
A guide to cascading payments for PSPs and acquiring banks: soft, hard and technical declines, which Visa response codes may cascade, cascade design, duplicate-charge prevention, 3DS, scheme rules, recovery KPIs and who should not cascade.
A guide for PSPs, banks and platforms on custom payment solutions: custom build vs off-the-shelf vs white-label, what can be customised, how a connector or payout flow is scoped and delivered, what drives cost and time, and the risks.