Payment Gateway Business Model: Revenue Streams & How to Start a Gateway Company

A payment gateway business model allows PSPs to provide businesses with the infrastructure needed to accept and manage online payments. It securely transfers payment data between the parties involved and supports transaction authorization. Revenue can come from transaction fees, setup charges, subscriptions, value-added services, and, where the company’s role permits, a share of the Merchant Discount Rate.

The guide below describes a full roadmap for launching and scaling a payment gateway company, covering revenue streams, pricing, unit economics, business models, compliance, partnerships, technology, go-to-market strategy, and operations.

What Does a Payment Gateway Company Do?

A payment gateway company is a technology provider that enables businesses to accept and manage online payments securely. A gateway is a central component of the payment processing workflow. It’s a secure digital bridge that captures, encrypts, and moves payment data between customers, merchants, acquiring banks, and processors. For a closer look at the technical side, read our step-by-step walkthrough of building a gateway.

Beyond transaction handling, payment gateway companies also offer tools that help their merchant clients operate more efficiently. These often include provider connections, settlement reporting dashboards with real-time analytics, payment routing logic that can improve approval rates and reduce fees, billing and reconciliation tools, and built-in compliance and risk controls for dispute management and settlement visibility.

In this context, another related term may come up: payment aggregator. A payment gateway and a payment aggregator are similar but distinct terms.

A payment aggregator is a type of PSP that acts as a financial intermediary between merchants and the banking network. It transfers data between the major players involved in transaction processing: the customer, the merchant, the acquiring bank, the issuing bank, and the card network.

Instead of requiring each business to open its own merchant account with an acquiring bank, the aggregator onboards multiple sub-merchants under a shared master merchant account, which can shorten the time needed to start accepting payments. See our payment aggregator explainer for a clearer breakdown of this model.

A payment gateway company is also distinct from a payment processing company, which handles the actual movement of funds rather than just the payment data. We break down that adjacent model in a separate roadmap for the processing-company route.

For these companies, revenue can come from several sources, including transaction fees, subscriptions, setup charges, and value-added services. We explain these income streams in more detail in the section below.

How Payment Gateways Make Money

A significant portion of a payment gateway service provider’s revenue comes from the markups applied to transactions processed through its platform. In simple terms, a payment gateway earns income from each transaction by charging a percentage fee, a fixed fee, or both as part of the Merchant Discount Rate (MDR). After the underlying transaction costs are covered, the remaining markup becomes your margin.

To understand what an MDR includes, you need to start with the card network business model, since card networks are major players in online payments.

When we talk about card networks, we usually mean Visa or Mastercard. Banks and other payment participants pay these networks fees for access to their infrastructure and for transactions processed through it. Acquirers, processors, and other parties involved in the payment flow may also charge their own fees.

Payment service providers similarly charge merchants. To accept payments online, a merchant may rely on an acquiring bank, card network, payment processor, and online payment gateway. Each participant may charge a percentage fee, a fixed amount per transaction, or both. The total amount charged to the merchant is the MDR. Meanwhile, the difference between your merchant pricing and the underlying costs determines your margin.

Payment gateways also generate income through setup charges, subscriptions, and other service fees that their customers pay regularly. Read the full financial model of a payment processor for a broader breakdown of payment costs, pricing, and margins.

Inside the Merchant Discount Rate

MDR is the blended rate a merchant pays to accept a card payment, typically a percentage of transaction value plus a fixed per-transaction amount. It is not a single fee but a stack, and each layer belongs to a different party.

For a payment provider, the distinction matters commercially: interchange and scheme fees are pass-through costs you cannot compress, while the processing and gateway layers are where your margin actually lives.

Interchange fee. Paid by the acquirer to the issuer for authorizing and settling the transaction. Rates vary by card type (consumer vs. commercial), presence (card-present vs. e-commerce), merchant category, and, most significantly, geography. Under the EU Interchange Fee Regulation, consumer debit is capped at 0.20% and consumer credit at 0.30% for EEA domestic and intra-EEA transactions. Commercial cards and inter-regional transactions carry no such cap and routinely run several times higher.

Scheme fees. Charged by the card network for use of its rails and billed to both the acquiring and issuing sides. Unlike interchange, these are made up of dozens of individual line items, like authorization, settlement, cross-border, currency conversion, fraud, and data services, which is why scheme fee reconciliation is one of the harder problems in acquiring.

Acquiring markup. The acquirer’s own margin for holding the merchant relationship, carrying settlement risk, and managing chargeback exposure. If your company holds an acquiring license, this converts from cost to revenue.

Processing and gateway fees. The technology layer: authorization routing, tokenization, 3DS, retries and cascading, reporting. This is the component a white-label provider serves, and the only one where infrastructure quality translates directly into unit economics.

What MDR does not include. Chargeback and representment fees, refund fees, FX markup, monthly minimums, PCI compliance charges, and settlement or payout fees are all billed separately. Merchants comparing providers on headline MDR alone frequently misjudge total cost by 20–40%.

Pricing Models Providers Use

A payment gateway pricing model determines how the provider combines underlying processing costs with its markup. Payment gateway providers charge merchants using one of two models: blended pricing or interchange++. Each offers a different balance between price stability and margin visibility.

Blended Fee

Payment service providers using a blended fee structure charge merchants a flat rate. It combines the average transaction processing cost with a fixed markup. This means the merchant pays a fixed fee per transaction, regardless of factors such as card type or the customer’s location. For example, a blended fee might be set at 2.5% per transaction, with no breakdown of how costs vary by different variables.

This pricing strategy gives merchants a stable and predictable rate, but the underlying costs remain less visible. For the provider, the margin may vary between transactions because interchange and card network fees can change while the merchant rate stays fixed.

Interchange++ Fee

Interchange++ is typically used by PSPs in the USA or large acquirers in Europe. This model provides a detailed breakdown of the three main costs associated with card payments: the acquirer’s markup, the card network’s fee, and the interchange fee. This way, the rate for each transaction will vary depending on the specific payment method used.

Unlike blended pricing, interchange++ makes the provider’s markup and underlying payment costs more transparent. But the final rate is less predictable because interchange and card network fees vary between transactions.

On average, the merchant is charged 1–3% under interchange++ pricing for each transaction. For example, if the total interchange++ rate is 2.0%, the fees may be divided as follows:

• 1% – interchange fee
• 0.5% – acquirer markup
• 0.5% – card scheme

In addition, the merchant will also pay a fixed PSP fee. Let’s assume the PSP fee is 0.5% of the transaction amount, a common markup charged by many PSPs.

For example, a customer makes a $1,000 purchase at the online store with a card issued outside the EEA. From this amount, the merchant will pay a $10 Interchange fee to the issuing bank, $5 to the acquiring bank, $5 to the card scheme, and $5 to the PSP. Accordingly, a merchant would receive $975 out of the $1,000 paid by the customer.

Revenue Streams of a Gateway Business

A payment gateway revenue model usually combines transaction-based income with recurring platform fees and paid services. Revenue grows through higher processing volume, a larger merchant base, and additional services sold alongside the core gateway infrastructure.

Unit Economics of a Gateway Business

Unit economics show what a gateway company can earn from each active merchant after covering the costs of serving that merchant.

When calculating startup costs for a fintech payment gateway company, count both the one-time expenses required to launch and the ongoing monthly costs of running the business. Akurateco and Dwayne Gefferie’s ebook explains in detail what exactly requires significant investment when building a payment infrastructure. Licensing an existing platform can reduce the initial investment, although it adds recurring license and service fees.

The figures below are illustrative. Actual results depend on transaction volume, merchant pricing, infrastructure costs, staffing, and commercial agreements.

Assumptions for the Worked Example

Suppose a gateway company serves 100 active merchants, each processing an average of $100,000 per month. This gives the company a total monthly payment volume of $10 million.

The gateway retains 0.30% of this volume as transaction revenue. It also charges each merchant a $250 monthly platform fee and earns an average of $50 per merchant from additional services.

The retained take rate is the part of the transaction fee that remains with the gateway after pass-through payment costs have been deducted.

Revenue Build-Up

A 0.30% retained take rate on $10 million in monthly volume generates:

$10,000,000 × 0.30% = $30,000

Monthly platform fees generate:

100 merchants × $250 = $25,000

Additional services generate:

100 merchants × $50 = $5,000

Total monthly revenue is:

$30,000 + $25,000 + $5,000 = $60,000

The gateway therefore earns an average of $600 in monthly revenue per merchant.

Monthly Cost Lines

Suppose the company’s monthly operating costs include:

• $15,000 for the platform and infrastructure
• $3,000 for fraud checks and transaction monitoring
• $4,000 for merchant support and dispute handling
• $18,000 for technical and payment teams
• $5,000 for compliance and legal work
• $6,000 for sales, administration, and other expenses

In that case, these cost lines total $51,000 per month.

They cover the technology, staff, security, compliance, integrations, and merchant support required to operate the gateway.

Net Profit per Merchant per Month

The company’s monthly operating profit is:

$60,000 in revenue − $51,000 in costs = $9,000

Dividing this result by 100 active merchants gives:

$9,000 ÷ 100 = $90

In this example, each merchant generates an average of $600 in revenue, costs $510 to serve, and contributes $90 in operating profit per month.

One-time launch costs also affect the result. For example, if the company spends $120,000 before launch and spreads that amount over 24 months, it adds $5,000 to monthly expenses. Monthly profit then falls to $4,000, or $40 per merchant.

A gateway company can improve its unit economics by increasing retained revenue per merchant, controlling operating costs, and spreading fixed expenses across a larger merchant base.

Business Models for Gateway Companies

A payment gateway startup can adopt several business models based on its monetization strategy, operational scope, and the extent to which it participates in the payment lifecycle. Each model has its own pros and cons.

Model 1: Full PSP / Payment Gateway Company

You build a full-service offering for merchants that includes both gateway technology and the PSP layer for payment processing and settlement.

Pros:

• Full ownership of the payment stack
• Highest revenue potential across processing fees, FX margins, value-added services, and settlements
• Strong competitive positioning with full control over performance and merchant experience
• End-to-end merchant management, including onboarding, risk, authorization flows, and payouts

Cons:

• High development and maintenance costs if built internally
• Requires licensing, depending on the country of operation
• Heavier compliance burden, including PCI DSS
• Higher operational complexity, requiring multiple specialized teams
• Longer time-to-market owing to the prolonged development timelines

Building an in-house gateway is typically only chosen by companies with extremely high transaction volumes and a strong, unique need for complete control over every detail of the payment flow. This also entails accepting the high cost and risk of managing PCI compliance.

Model 2: Gateway-as-a-Service Company

You offer gateway infrastructure but don’t process funds, while merchants connect their own PSPs, acquirers, and APMs.

Pros:

• Faster time-to-market thanks to thanks to software already built by an expert team
• Usually no financial licensing required, since you never hold funds
• Immediate access to multiple integrations and connections
• White-label branding and customization options
• Lower operational overhead compared to full PSPs

Cons:

• Revenue potential may be lower, as monetization is focused on software rather than processing fees
• Payment performance depends on the merchant’s PSP partners, not the gateway
• Less control over settlement and payout experience

This model is ideal for financial entrepreneurs who want to quickly tap into the market and open a new payment revenue stream but don’t have the expertise or resources to build and maintain a complex, regulated payment infrastructure.

One caveat on licensing: the exemption depends on your jurisdiction and on how money actually moves through your setup, not on how you describe your role. Passing payment instructions between merchants and their providers generally keeps you outside licensing requirements, while holding funds even briefly or controlling a settlement account generally does not.

Model 3: Vertical-Specific Payment Gateway

Instead of operating a general PSP, this model focuses on specialized industries and their unique payment needs, including travel, betting, marketplaces, and subscriptions.

Pros:

• Clear product-market fit, with a solution addressing the exact needs of one domain
• Targeted compliance and risk management
• Stronger differentiation with industry-specific features
• Stronger readiness to invest in specialized capabilities that solve unique business challenges

Cons:

• Requires deep domain expertise to maintain a competitive edge
• Regulatory obligations vary greatly across different countries, depending on the industry
• Market size is narrower, limiting growth potential

If your focus is on a particular niche with unique payment needs, a vertical-specific payment gateway helps to target a specific customer base and solve their challenges.

Model 4: SaaS or Platform Adding Its Own Gateway Layer

In this model, a SaaS product or digital platform extends its core offering by adding a payment gateway layer. The platform becomes a payments provider, gaining additional revenue while delivering a more integrated experience to its users.

Pros:

• Improved margins as payments become a new source of revenue
• Higher customer retention, since merchants rely on the platform for both payments and software
• Full control over the user experience, from checkout to reporting
• Stronger differentiation with an all-in-one solution

Cons:

• More operational responsibilities, including risk, compliance, and support
• Additional technical complexity, requiring engineering resources
• Financial licensing may be required if the platform holds the funds
• Significant competition with global payment giants

This model allows existing SaaS and platforms to introduce new payment revenue, increase customer retention, and gain greater control over the user experience without becoming a full PSP.

How These Compare to PayFac and Aggregator Models

The gateway models above describe how a company builds, operates, or licenses payment infrastructure. There are also PayFac and payment aggregator models. They define how a provider onboards merchants and gives them access to payment processing.

Under a PayFac-as-a-Service model, merchants are onboarded through a registered payment facilitator and its acquiring relationship. A payment aggregator model also groups multiple merchants under a shared acquiring setup, although the exact structure and responsibilities vary by market.

Does Your Model Require a License?

The licensing outcome is driven by one question — how money moves through your setup:

Use this table as a starting point. Your compliance obligations depend on your jurisdiction, your exact setup, and the exact fund flow, so treat it as the first question to bring to regulatory counsel rather than as an answer in itself.

Market Research: Your Ideal Merchant Base

Merchant segments handle payments in distinct ways. Their risks, transaction flows, and day-to-day needs vary, so they rely on payment gateways for different reasons. As a payment gateway company, you need to understand these differences to decide which features and integrations to prioritize in your platform architecture.

Digital Banks / Fintech Apps

Fintech companies handle sensitive financial and identity data every day, so their payment operations need to be secure and stable. For them, payment gateways are core components that support transaction processing, identity verification, and authorization across different payment rails.

They may also need account-to-account payments, digital wallets, card issuing connections, multi-currency support, and integrations with banking or compliance systems. As fintech products expand, the gateway must support new providers and payment flows without disrupting existing operations.

Subscription Businesses

Subscription businesses focus heavily on keeping customers over time. That is why they need robust technology for recurring billing, tokenization, and reliable retry flows. Many companies use payment gateways to store payment details securely, recover failed renewals, manage subscription updates, and keep daily billing tasks under control.

SaaS companies may also need support for monthly and annual plans, free trials, upgrades, downgrades, usage-based billing, and prorated charges. Payment reporting should help them track recurring revenue, failed payments, churn, refunds, and renewals across different plans and markets.

Ecommerce

Ecommerce merchants typically look for smooth checkout experiences and a variety of ways for customers to pay. They also care about approval performance and being able to accept international shoppers. Payment gateways help them address these areas by improving conversion, reducing drop-offs, managing fraud risk, and ensuring the system can handle high-volume periods.

Travel and Airlines

Travel payments are usually large in value, often cross-border, and tend to generate more disputes. Because of this complexity, along with additional 3DS and Strong Customer Authentication requirements, merchants in this niche rely heavily on gateways that help them reduce international declines, manage fraud exposure, support multiple currencies, and diversify processing through several PSPs.

High-risk Verticals

As a rule, high-risk industries face higher fraud and chargeback rates, stricter underwriting, and fewer willing acquirers because the nature of the industry creates additional operational, financial, and compliance risks for banks and PSPs. Because of these challenges, many operators use high-risk payment gateways to connect with specialized PSPs, manage risk more effectively, handle disputes faster, and stay aligned with compliance requirements while keeping approval rates at a workable level.

Marketplaces and Platforms

Marketplaces work with many different sellers, split payments, and scheduled payouts. That is why they rely on payment gateways to onboard sellers through Know Your Business checks, handle multi-party transactions, manage payout flows, and give both buyers and sellers clear, consolidated reporting.

Compliance & Licensing Requirements

When exploring how to start a payment gateway company, you need to understand the core foundations for any gateway startup: compliance and licensing. In practice, they define the regulatory framework within which your company can operate and are necessary to launch and maintain a functional gateway in the market you target.

Let’s examine the fundamental payment gateway licensing requirements that are strategically important for launching and operating a gateway business.

PCI DSS

PCI DSS compliance applies to organizations that store, process, or transmit cardholder data, as well as systems that can affect the security of the cardholder data environment. The level of responsibility and the scope of validation depend heavily on the gateway architecture.

When it comes to compliance, there’s a nuance many new founders miss: working with a certified provider can reduce your PCI DSS scope, but it does not remove your responsibilities or the need to validate compliance at the level your setup requires. The PCI Security Standards Council provides the official PCI DSS requirements and guidance that determine what remains in scope and how compliance must be validated.

You also need to ensure cardholder data stays outside your environment if reduced scope is the goal. An integration that routes card data through your own servers, even briefly, brings those systems under PCI DSS.

The cost is not limited to validation paperwork. Depending on your setup, the cost can include security controls, evidence collection, vulnerability management, penetration testing, segmentation controls where segmentation is used, and recurring compliance work. That makes PCI DSS compliance an ongoing obligation rather than a one-off expenditure. The total cost depends on your architecture and the requirements of your acquirer or payment brands, and in some cases on transaction volume. Confirm it with a Qualified Security Assessor before budgeting for compliance.

Local Regulations

Whether you’re operating in the EU, GCC, LATAM, or Africa, each has its own local regulations that a payment business must adhere to. Depending on the target region, you’ll need to understand how government officials define payment services and what requirements apply. Getting this right early helps you choose the fastest way into the market, shape your commercial approach, pick the right tech setup, and avoid unnecessary risks or costs.

Contracts with Acquiring Banks and PSPs

You can’t operate as a payment gateway without establishing legal partnerships with your acquiring banks and PSPs. The one fact that you need to realize is that it’s a fundamental requirement for processing transactions, supporting multiple payment methods, or giving merchants access to the providers they need.

AML/KYC Expectations

When onboarding merchants, you are responsible for applying AML/KYC checks to confirm who the merchant is and whether their activity is legitimate. This is often a requirement from banking partners and helps prevent fraud, chargebacks, and regulatory issues later.

Due to numerous challenges in payment gateway development, primarily around licensing and compliance nuances, new payment gateway companies decide to take a smarter, more efficient path.

To accelerate time-to-market and reduce regulatory complexity, many startups rely on support models such as:

• White-label payment gateway platforms that allow businesses to avoid building the entire infrastructure from scratch. PCI DSS scope becomes much narrower because cardholder data is handled inside the vendor’s certified environment instead of yours, but it does not disappear, and your acquiring partners will ask for evidence of your compliance.
• Outsourced PCI or compliance certification, where a specialized firm manages your PCI DSS audit and documentation if your business model requires certification.
• Compliance-as-a-service providers that take over ongoing operational tasks, such as merchant onboarding, AML checks, transaction monitoring, and regulatory reporting.

Each approach simplifies the launch of a payment gateway for founders. As a result, founders can focus on going live and merchant acquisition.

Essential Departments & Teams

Every gateway launch also depends on the people behind it. In most early-stage setups, this means building a small but capable team that can cover the fundamental processes.

A typical starting team includes around 15-36 people across seven core functions, depending on the company’s technology model, market scope, and level of outsourced support.

Compliance & Risk (2–4 people)

This group manages your regulatory obligations and keeps merchant activity under control. They handle licensing matters, review AML and KYC documents, and monitor risk on an ongoing basis.

Technology & Product (6–12 people)

This team drives the development and evolution of your payment gateway. They coordinate product updates, support new integrations, and ensure the platform remains reliable as transaction volume increases.

Customer Support & Merchant Operations (2–5 people)

These are the people who stay close to your merchants day to day. They answer questions, solve operational issues, and help keep transaction flows running smoothly.

Sales & Partnerships (2–6 people)

This function focuses on bringing new merchants on board and building relationships with PSPs, acquirers, and alternative payment method providers. Their work shapes your commercial pipeline and partner network.

Finance & Settlement Operations (1–3 people)

The finance team oversees reconciliation, invoicing, and settlement-related checks. They help ensure that money movement and reporting remain accurate and timely.

Account Management (1–3 people)

Once merchants go live, this team looks after them. They help improve payment performance, support feature adoption, and maintain long-term relationships and retention.

Marketing (1–3 people)

This team represents your brand in the market. Through thought leadership, targeted campaigns, and search-focused content, they build awareness and attract qualified prospects looking for payment infrastructure.

Partnerships Required to Launch a Payment Gateway Company

A payment gateway depends on a network of financial, technology, and risk partners. The broader this network, the more payment methods, processing routes, and markets the gateway can support. To operate effectively, you need to secure relationships with several key players across the payments landscape:

• Acquiring banks, which provide merchant acceptance and support transaction authorization, clearing, and settlement.
• PSPs, which give your merchants access to additional processing routes and geographies.
• Local APMs and digital wallets needed to support region-specific payment habits.
• Fraud prevention providers, which strengthen security and reduce operational risk.
• KYC/KYB vendors who help you verify merchants during onboarding.
• BIN sponsors, if required by your business model, which enable card issuing or tokenization.
• Infrastructure providers such as AWS, Azure, or Oracle Cloud, which host your platform and support uptime.

It is this wider ecosystem of partners that makes a payment gateway work. No single provider can realistically build every payment method, integration, or fraud tool in-house without slowing growth or increasing costs.

A modern gateway creates value by giving merchants more options across payment routes, methods, and performance optimization. Over time, this allows you to expand coverage, support different merchant segments, control costs, and remain competitive.

Technology Options: Build, White-Label, or Hybrid

When exploring how to start a payment gateway company, you ultimately choose among three technology paths: building in-house, using white-label payment gateway solutions, or adopting a hybrid model. Each comes with different levels of control, cost, and speed to market.

One thing to state upfront: Akurateco develops and provides white-label payment gateway infrastructure, so we have a commercial interest in one of the three options below. The trade-offs listed for each path are the ones we would want a buyer to weigh before choosing any vendor, including us.

Option 1 — Build a Custom Gateway

There are several business implications associated with payment gateway development. One of the most important is the cost of gateway development, along with the time and resources required to build a payment gateway from scratch. ScienceSoft’s 2025 research estimates that building a custom gateway costs $100,000–$300,000+ and takes approximately 6–11 months.

That is why this option is typically chosen only by companies with very high transaction volumes, unique requirements, or a strong need for control and proprietary processing logic. For most early-stage PSPs and startups, the time-to-market and cost barriers are difficult to justify.

Option 2 — White-Label Payment Gateway

With a white-label payment gateway, startups can take the shortest path to launch: typically a few weeks rather than the months or years required for in-house development. The infrastructure, security layers, and hundreds of integrations are already built and maintained by the vendor. Because the vendor’s environment is PCI DSS-certified, the compliance scope you have to cover yourself becomes much narrower.

This allows founders to focus immediately on merchant acquisition, partnerships, support, pricing, and operations. A white-label gateway is often chosen over in-house development by PSP startups, SaaS platforms adding payments, regional providers, and entrepreneurs who want to launch a gateway business with lower upfront costs.

The trade-offs are real. You depend on the vendor’s roadmap for new connectors and features. That means some requests may not align with its priorities or delivery capacity. Recurring license or revenue-share fees replace the upfront development spend, so buyers should compare total long-term costs rather than launch costs alone.

You also give up some ownership of the underlying technology. Differentiation can still come from your commercial offer, service, and market focus rather than from proprietary technology, but competitors can access similar core infrastructure. Switching vendors later takes planning, which is why the selection criteria below matter more than the launch timeline.

Option 3 — Hybrid Model

Many modern PSPs adopt a hybrid strategy: they launch using a white-label solution, validate demand, build revenue, and then gradually extend the platform with proprietary modules where differentiation is needed.

This model combines rapid market entry with the option to develop a more customized or partially in-house stack over time. It also reduces risk by allowing the company to validate its business model before making major engineering investments. For a deeper comparison of these paths by cost, risk, and timeline, read our full build-vs-buy analysis for PSPs.

White-Label Gateway Economics

The white-label payment gateway business model replaces most in-house development costs with platform licensing fees. Instead of funding years of engineering, integrations, security work, and maintenance, you pay to use infrastructure that is already built and supported.

White-label providers usually structure their commercial agreements in one of two ways:

• Upfront license. A PSP pays a larger initial fee, followed by recurring charges for hosting, support, maintenance, or transaction volume. This requires more capital at launch but can leave the provider with a larger share of future revenue.
• Revenue share. The initial cost is lower, but the platform vendor receives an agreed percentage of transaction or service revenue. This reduces the barrier to entry while lowering the margin retained as volume grows.

Some vendors combine both through a setup fee, monthly platform charge, and transaction-based pricing.

The most valuable benefit is faster time to revenue. A licensed platform significantly shortens the period between the initial investment and the first merchant income. Compared with custom development, which typically takes at least a year, this option allows you to launch within weeks. You can start onboarding merchants and charging transaction fees, subscriptions, setup fees, and value-added service fees without waiting for the full gateway stack to be developed.

Your retained margin is the revenue collected from merchants after deducting license fees, revenue share, processing costs, payment method charges, fraud tools, compliance, support, and other operating expenses. Merchant pricing and commercial strategy remain under your control, subject to the platform agreement.

Akurateco’s PCI DSS-certified white-label payment gateway combines branded payment infrastructure, integrations, merchant management, billing, and reporting into a single platform.

How to Choose a White-Label Gateway Vendor

Most white-label gateways can reduce launch time and upfront costs. But long-term reliability and scalability depend on much more. Before selecting a vendor, evaluate these critical factors:

• Connector depth. A long provider list means little if key integrations are outdated or limited. Look for live coverage in your target markets, supported payment flows, and clear ownership of connector maintenance.
• Merchant management. Weak merchant controls create manual work as the portfolio grows. Assess onboarding, multi-MID support, permissions, billing, limits, and reporting from one interface.
• Configurability. Frequent vendor dependence slows routine changes. Identify which routing rules, fees, limits, workflows, and branding elements your team can manage without development support.
• Service terms. Platform issues directly affect merchants and revenue. Compare SLA commitments, incident response, support coverage, and delivery times for new integrations.
• Data access. Limited access can restrict reporting, optimization, and future migration. Review API availability, export formats, data granularity, and ownership of transaction records.
• Exit conditions. A difficult exit can create technical and commercial lock-in. Check notice periods, data portability, migration assistance, and access after the contract ends.

Choose a vendor that can support both launch and scale. Clear ownership, service terms, and exit conditions prevent costly surprises later.

Go-to-Market Strategy

Launching a payment gateway is only half the story. You also need a sustainable flow of clients. Winning merchants requires a targeted strategy, especially in the early stages when your positioning, partnerships, and sales focus are still taking shape.

Here are recommendations on how a new payment gateway company should shape an effective go-to-market strategy.

Define Your ICP (Ideal Customer Profile)

Start by identifying the type of merchant your gateway is built to serve. In payments, an ICP is defined by how a merchant processes, not by company size or industry label alone. Four variables do most of the work.

Processing volume. There is a floor below which a merchant may not justify your onboarding and support costs, and a point above which a merchant is more likely to expect customized pricing, direct acquiring relationships, and greater control over their payment setup. Your initial target usually sits between the two, but you may be able to serve a wider range of merchants as your onboarding and support processes become more efficient.

Card mix and geography. The types of cards a merchant accepts and where those cards are issued affect its payment costs. EEA consumer debit and credit cards are generally subject to capped interchange. Commercial and inter-regional cards can carry different, often higher costs. Card mix can therefore have a significant impact on the economics of an account. This understanding helps you determine what pricing and acquiring setup may be viable.

Risk classification. A merchant’s category code is an important part of determining which acquirers may support the business and under what conditions. Know which merchant categories, geographies, and risk profiles your acquiring partners accept before you build a pipeline around merchants they are unlikely to approve.

Existing setup. A merchant already using one or more payment providers may have established integrations, contracts, and internal processes. In this case, switching is more complex. Merchants dealing with fragmented payment setups, limited provider coverage, or operational inefficiencies may have a stronger reason to consider a new PSP. Understanding the merchant’s current setup helps you assess both the sales effort required and the problems your offer needs to solve.

The sharpest early ICP is often a merchant that has outgrown a simple single-PSP setup and needs broader payment capabilities but does not want to build and manage complex payment infrastructure. This type of merchant has a clear operational problem, a reason to consider a new PSP, and a stronger need for capabilities such as multiple acquiring connections, routing, broader payment-method coverage, reporting, and reconciliation.

Target High-Value Verticals First

Prioritize verticals with high processing volumes and complex payment operations.

These merchants often manage multi-PSP setups, cross-border flows, recurring billing, or elevated dispute rates. A new gateway can serve digital goods, marketplaces, subscription businesses, travel companies, and financial apps. These sectors move quickly and are often more willing to consider a new provider when it can remove clear payment friction.

Choose Local-First or Global-First Expansion

Your target geography determines which integrations, licenses, and partners you need first.

A local-first strategy works well when you specialize in one geography or regulatory zone, such as the EU, GCC, or LATAM. A global-first strategy better suits gateways focused on cross-border commerce, currency coverage, and PSP aggregation.

The decision should be based on how fast you want to go live and which partners you can secure.

Design a Commercial Routing Strategy

Your routing strategy should reflect merchant needs, processing costs, and provider performance.

Commercial routing defines why transactions are sent through specific PSPs or acquirers. It should account for processing patterns, geography, currencies, approval rates, cost, and provider availability.

When designed well, it can support higher approvals, cost savings, PSP failover, broader coverage, and new payment methods. In many cases, this can also become a core part of your commercial offer, especially for merchants that have outgrown a single-PSP setup.

Focus on the Features Merchants Expect in Year One

Your first release should cover the core capabilities merchants need to operate confidently.

These usually include:

• Fast KYC, KYB, and technical onboarding
• Clear dashboards and reporting
• Smart routing and multiple PSP options
• Reliable settlement visibility and transaction monitoring

Missing any of these capabilities can make sales cycles longer and merchant onboarding more difficult.

Differentiate Where It Matters

Strong positioning should focus on measurable operational value rather than broad claims.

The market is crowded, but existing providers can be less flexible when merchants need quicker adjustments or more tailored payment setups, such as adding a new connector, onboarding a non-standard merchant profile, or changing routing rules for a single account. A new gateway can stand out by adapting faster to customer needs instead of simply offering more features.

A new gateway can stand out through:

• Faster onboarding, integration, and deployment
• Wider PSP, APM, currency, and regional coverage
• Greater automation across risk, monitoring, and alerts
• Clear pricing that merchants can understand
• Better visibility into transactions, reconciliation, settlements, and disputes

Clear market positioning is what moves you from “another PSP” to a platform merchants rely on for daily operations.

Scaling Your Payment Gateway Company

Once your payment gateway is live and supporting its first merchants, the next step is scaling. As your clients grow, their expectations evolve. Over time, they will need stronger performance, faster transactions, broader coverage, and more sophisticated tools.

Focusing on these core areas will help your gateway meet growing payment demands, strengthen performance, and scale more efficiently.

Operational Bottlenecks That Make a Gateway Break

A payment gateway must support a growing merchant base and increasingly complex operational needs. As the merchant base grows, any manual processes become the main barrier to scale:

• Merchant onboarding. Repeating KYC/KYB reviews, pricing setup, credentials, permissions, and account configuration slow activation.
• Reconciliation. More PSPs, currencies, and settlement schedules create reporting gaps and manual matching work.
• Provider incidents. Fragmented monitoring makes outages, failed transactions, and merchant communication harder to manage.
• Configuration duplication. Copying routing rules, fees, limits, and settings across accounts increases errors and inconsistencies.

A centralized merchant management system reduces these bottlenecks by keeping merchant data, configurations, permissions, and operational workflows in one place.

Expand Geographic Coverage (PSPs / Acquirers / APMs)

Broader payment coverage allows you to support merchants in more markets.

Scaling starts with expanding your processing network. Adding new PSPs, local acquirers, and APMs helps you enter new markets, increase approval rates, and support merchants with region-specific payment habits.

Add A2A and Open Banking Rails

A2A and open banking payments can expand coverage while reducing transaction costs.

Account-to-account and open banking payments are becoming more widely used. Introducing these rails strengthens your offer with lower-cost transactions, faster settlements, and support for regulatory requirements across European, GCC, and APAC markets.

Add Tokenization and Network Tokenization

Tokenization helps merchants protect payment data and improve recurring payment performance.

As merchants grow, so does their need for advanced retention tools. Tokenization and network tokenization help reduce payment friction, improve recurring acceptance rates, and strengthen security for subscription-heavy verticals.

Introduce Risk Scoring and Automation

Automated risk controls allow the gateway to manage higher transaction volumes without increasing manual work at the same rate.

A scalable gateway must handle risk without adding unnecessary operational workload. Automated decisioning, transaction scoring, and real-time monitoring reduce fraud exposure and streamline operations, which can be an important differentiator for enterprise merchants.

Grow Your Merchant Base

A larger merchant portfolio spreads fixed operating costs and creates more recurring revenue. Once you have a healthy sales pipeline, portfolio growth can become constrained by onboarding throughput. Each new merchant you add must complete required business verification, like KYB, and underwriting for your acquiring setup, and be configured before it can start processing. In an early-stage setup, it’s natural that some of these steps may still involve a lot of manual work, but it often creates onboarding bottlenecks.

For that reason, time-to-first-transaction is an important metric to manage. A long onboarding process leaves signed merchants waiting to start processing, which may cause drop-offs. If you manage to shorten that path, that can help turn signed accounts into active, transacting merchants faster.

As the portfolio grows, track two key metrics: the share of onboardings that require manual intervention and the time from signed contract to first live transaction.

For similar types of merchants, onboarding should become faster and require less manual work over time. If it starts taking longer or needs more manual effort, identify which steps are slowing the process down.

Move to Multi-PSP Routing to Increase Approval Rates

Multi-PSP routing improves resilience by giving transactions more than one processing path.

As volume increases, merchants expect stronger payment performance. Multi-PSP routing helps optimize costs, reduce declines, and provide redundancy. This makes your gateway more resilient and commercially attractive.

Common Mistakes New Gateway Companies Make

When starting a payment gateway company, the most common mistakes involve launching before the business has the right partnerships, compliance resources, product direction, and operational controls in place. The main pitfalls that early-stage teams should avoid are:

• Starting with technology instead of partnerships. Many founders begin coding before securing acquirers, PSPs, or APMs. Without these partners, even the best gateway cannot process a single transaction.
• Underestimating compliance costs. PCI DSS, licensing, AML/KYC, and banking requirements often take more time and budget than expected, which can delay the launch and drain resources.
• Poor merchant onboarding flows. Long KYC/KYB checks, unclear instructions, or slow integrations can lead to early churn and lost deals.
• Failing to differentiate in a saturated market. New gateways often launch with a generic offer and no clear go-to-market strategy. As a result, they struggle to stand out from established PSPs.
• Hiring developers before product managers. Building without a product roadmap leads to unnecessary features, slow releases, and misalignment with merchant needs.
• No monitoring or visibility tools. Gateways that do not provide clear reporting, alerts, and real-time transaction statuses can quickly lose merchant trust.
• Scaling infrastructure too late. Traffic spikes or expansion into new verticals can expose gaps when the infrastructure was not designed for growth from the beginning.

Many of these mistakes happen because early teams try to manage too much too soon. A strong foundation can reduce this overhead and allow founders to focus on partnerships, merchant acquisition, and growth.

Conclusion

A payment gateway company can earn recurring revenue through transaction markups, setup fees, subscriptions, and value-added services. To remain sustainable, merchant pricing must cover processing, technology, compliance, support, and risk costs while leaving enough margin for growth.

However, revenue alone does not ensure a successful launch. The business also needs a defined merchant segment, strong acquiring and PSP relationships, a clear compliance plan, and infrastructure that can scale. Building everything in-house may suit companies with large budgets and highly specific requirements, while licensing an established platform can reduce development risk and shorten time to revenue.

Akurateco’s white-label payment gateway provides PCI DSS-compliant infrastructure with pre-built 700+ connectors, merchant management, reporting, analytics, and customization tools in one platform. This lets new gateway companies focus on merchant acquisition, partnerships, pricing, and payment performance instead of building the core technology from scratch.

FAQ

How do payment gateways make money?

Payment gateways earn most of their revenue from the Merchant Discount Rate (MDR) charged on each transaction, complemented by setup fees, recurring fees, value-added services, and other charges.

What are the main revenue streams in a payment gateway business model?

Beyond transaction fees, revenue comes from setup fees, recurring fees, chargeback and fraud fees, cross-border fees, value-added services, custom development, and partnership referrals.

What does the Merchant Discount Rate (MDR) include?

MDR is the total per-transaction fee a merchant pays that consists of the interchange fee, the card network fee, the acquiring bank fee, and the payment service provider’s margin.

What is the difference between blended and interchange++ pricing?

Blended pricing charges a single flat rate per transaction regardless of card type or location, while interchange++ breaks the cost into interchange fee, acquirer markup, and card scheme fee, so the rate varies by payment method.

How much does it cost to start a payment gateway company?

The cost varies widely based on the approach. According to ScienceSoft’s 2025 figures, developing a custom payment gateway can cost $100,000–$300,000+. A white-label payment gateway can reduce initial costs by at least half, allowing startups to launch quickly and with a narrower compliance scope.

How long does it take to launch a payment gateway company?

It usually takes about 6–11 months to start a payment gateway business, depending on the complexity of routing, reporting, and integrations. With a white-label solution, companies typically launch within weeks, depending on the integrations and setup they want.

Can a startup launch a payment gateway using a white-label solution?

Yes, for most startups, it is the fastest route to market. A white-label platform gives you ready infrastructure and integrations. It keeps cardholder data inside the vendor’s certified environment, so your own PCI DSS scope is much smaller but is not eliminated entirely. The trade-off is dependency since your roadmap and connector coverage partly follow the vendor’s delivery capacity and priorities.

Do payment gateway companies need their own acquiring bank?

Not necessarily. Many gateways operate via merchant-provided PSPs and acquirers, simply facilitating transactions between them. However, gateways that act as full PSPs or provide settlements must secure acquiring partnerships and, in many regions, licensing.