Blog Main Image

For payment providers , merchant onboarding is a critical revenue driver, yet it's often hampered by universal pain points. The root cause of slow or failed onboarding is rarely a single technical issue. Instead, it’s typically caused by organizational silos and a fragmented technology infrastructure.

When teams operate in isolation, they rely on disconnected systems, painfully stitched together with the digital equivalent of sticky tape and string: email threads and shared spreadsheets. The result is a poor merchant experience. Applicants are bounced between departments, asked to re-enter the same details, and left waiting for weeks. This frustration directly fuels merchant abandonment.

The cost is staggering. Operationally, it means higher overhead and bloated staffing. As Daniel Sheahan, CEO of MVSI  notes, “The biggest challenge is cost investment. In people, processes, and technologies. This investment is a delicate balance; under-resourcing leads to failure at scale and brand damage, while over-investment wastes precious capital.”

Strategically, it creates dangerous compliance gaps. But most critically, it drives a hemorrhaging stream of merchant abandonment. Fragmented systems are universally recognized as one of the biggest barriers to agility and scalability. 

You can patch this with point solutions, but that won't fix the architecture. If you want to scale sustainably, you need to start by investing in a unified platform; modern merchant onboarding, designed for an automated onboarding process.

For a full definition and stage-by-stage breakdown, read our complete guide to end-to-end merchant onboarding.

‍

What is scalable merchant onboarding?

Fast onboarding is about reducing time to activation. Scalable merchant onboarding is different. It means handling more applications, products, markets and partners without operational effort, headcount or risk increasing at the same rate.

The goal is not simply to make one merchant journey faster. It is to increase onboarding capacity without recreating the same bottlenecks at higher volume.

‍

How end-to-end merchant onboarding supports scale

Scalable onboarding depends on end-to-end process design. If application data, verification results, underwriting decisions and ongoing due diligence sit in separate systems, higher volume simply creates larger queues and more handoffs.

An end-to-end merchant onboarding workflow gives payment providers the foundation to scale with control. Routine applications can move through configured rules, while incomplete, contradictory or higher-risk cases are routed to the right team with the relevant context.

‍

Key Takeaways

Sustainable scaling requires more than faster forms or extra reviewers. It depends on four operating principles:

  • Scale capacity, not manual workload: Higher application volumes should not require manual review and headcount to grow at the same rate.
  • Automate the predictable and manage by exception: Routine, lower-risk applications can move through configured workflows while complex, incomplete or higher-risk applications are routed for human review.
  • Keep the merchant journey connected: Application data, verification, underwriting, approvals and ongoing due diligence should build on the same merchant record so bottlenecks do not simply move downstream.
  • Configure for change: New merchant types, products, markets and partner channels should be supported through configurable rules and workflows not repeated custom rebuilds.

‍

The true cost of scaling merchant onboarding

Scaling merchant onboarding is not only a technical challenge. It is a financial and operational one. Payment providers need to decide where to invest in people, processes and technology so growth does not create larger queues, higher costs or weaker risk control.

‍

The high cost of under-investment in merchant onboarding:

  • The Strategy: Many organizations intentionally under-invest in their digital onboarding solutions, viewing it as the safer financial path.
  • The Risk: This becomes a critical vulnerability during periods of rapid growth or major product launches, creating gaps in your merchant onboarding processes. 

This leads directly to failure at scale and brand damage, as Sheahan warns, citing a client example: “Their old merchant onboarding process fell flat on its face and they had a lot of disgruntled customers. They eventually got through them, but I’m sure they lost a tonne of them along the way.” The cost of under-investment is ultimately measured in abandoned merchants, lost revenue, and long-term reputational harm.

‍

The burden of over-investment

  • The Problem: Investing too much in the wrong areas means a significant waste of money and resources in your merchant onboarding process.
  • The Cause: Pouring capital into fragmented solutions, whether through extra headcount to manage manual processes or point solutions that create new problems such as data silos.

This leads to bloated operational overhead, without achieving scalability. A miscalculation of capital strains the bottom line and inhibits the agility needed to compete, locking payment providers  into inefficient cost structures that are difficult to unwind. The path to scalable merchant onboarding requires navigating this investment paradox. Sustainable growth isn’t found in either extreme but through strategic investment in a unified foundation that optimizes both cost and performance from day one.

‍

What Breaks as Merchant Onboarding Volume Grows?

Merchant onboarding usually breaks at the handoff points. As volume grows, disconnected systems, repeated data entry, unclear ownership and manual review queues become harder to absorb.

Scaling pressure Common response Scalable response
More merchant applications Add reviewers and larger queues Automate routine cases and manage by exception
More data and checks Add point solutions and manual transfers Connect data, verification and decisions in one workflow
More exceptions Expand manual review teams Route exceptions to the right specialist with full context
More products and markets Build separate journeys or custom code Configure rules, requirements and approval paths
More partners and channels Duplicate processes and lose visibility Support tailored journeys within centralized governance

‍

Manual scale vs scalable merchant onboarding

Area Manual scale Scalable onboarding
Data collection Merchants repeat information across forms and teams Data is captured once and reused across the workflow
Verification Checks happen in separate tools KYB, KYC and AML results feed the same merchant record
Risk review More volume creates larger review queues Lower-risk cases move automatically and exceptions are routed
Governance Policy depends on manual interpretation Rules, thresholds and approval paths are configured
Reporting Teams rely on spreadsheets and status updates Leaders see application, risk and decision data in one view

‍

How to Build a Frictionless and Automated Merchant Onboarding Process

The core failure lies in siloed process design. Data collected by one team becomes another’s manual input, creating significant merchant friction. Critical intelligence slips through the cracks, causing blind compliance spots even the best Anti- Money Laundering (AML) compliance tools can’t fix. What outwardly looks like a process of managed handoffs and approvals is actually an assembly line of friction points that systematically slow time-to-revenue, inflate error rates, and degrade the merchant experience, ultimately leading to higher merchant attrition.

This siloed approach is a direct result of each business unit requiring its own tools, processes and people, inevitably designing for disconnection rather than a unified customer journey. These inefficiencies hit the bottom line, whether through the cost of additional resources or lost revenues from abandoned merchant applications.

The secret to robust compliance and risk management is “automation, automation, and automation.” But scalable automation does not mean removing human judgment. Routine checks and lower-risk applications can move through configured workflows, while incomplete, contradictory or higher-risk cases are routed to the right team for review.

That allows payment providers to increase onboarding capacity without making every new application another manual task. Compliance stops being something that simply requires more people as volumes grow and becomes part of a repeatable, risk-based operating model.

‍For a deeper look at how straight-through processing, management by exception and human review can work together at high volume, see Instant Onboarding at Scale: A Guide for Payment Providers.

‍

How organizational silos increase merchant attrition and compliance risk 

This isn’t a talent problem; it’s an architectural one within the merchant onboarding process. Institutions are pouring ever more resources into their defense, investing heavily in AML compliance tools. UK financial institutions spent £38.3 billion on financial crime compliance in 2023, up 12% from the previous year, according to LexisNexis Risk Solutions. Yet when onboarding remains siloed, higher spend does not necessarily translate into a more efficient or scalable process.

This misdirected investment means that legitimate, low-risk merchants who clearly meet policy are subjected to excessive paperwork and frustrating delays in their merchant applications, while the sophisticated, high-risk actors slip through unchecked. 

These gaps create a toxic cycle. Compliance teams are blamed as barriers to growth, morale drops, and sales teams feel blocked. The result is a culture of conflict instead of collaboration. The problem is so prevalent that regulators have taken note, warning that entrenched silos create significant pain points for scalability and agility.

‍

Implementing a customer-centric merchant onboarding journey

The antidote is a radical shift to a journey-centric, end-to-end design. The entire merchant onboarding process needs to be mapped to the merchant’s experience, not to your internal org chart. As McKinsey advises, organizations should minimize functional silos: “keeping functional silos as dominant decision-making units may lead to optimizing individual processes and touchpoints, but not the end-to-end customer journey”. 

In regulated payments, that journey-centric model means connecting application data, verification, underwriting, approval and ongoing due diligence within an end-to-end merchant onboarding workflow.

In practice, this requires two fundamental and simultaneous shifts:

  • A Metrics and Incentives Revolution: You need to stop measuring success by internal metrics. The real measure of health is the merchant’s experience. Time-to-first-transaction, drop-off rates at each stage, conversion velocity—these are the KPIs that reveal whether your process is an engine for growth or a primary cause of merchant attrition. 
  • Cross-Functional Ownership: This isn't just about better meetings; it's about restructuring accountability for the entire business onboarding journey. Dedicated cross-functional teams should be empowered to shepherd a merchant from initial application straight through to full activation. 

‍

Choosing the right scalable merchant onboarding software for your business

This customer-centric approach requires modern, unified merchant onboarding software. The essential technical foundation for scalable merchant onboarding includes a single source of truth, real-time data access and a central workflow engine. Together, these capabilities reduce duplicate entry, automate routine checks and make no-touch onboarding possible for merchants that meet defined rules and risk criteria, while keeping decisions, exceptions and reviewer actions visible in one place.

This shift fundamentally changes how you buy tech. Don’t just buy features; buy orchestration capabilities. Demand that platforms demonstrate how they let you compose and modify complex journeys, automate routine decisions and move eligible merchants from application to activation with no manual touch.

But don’t stop at the happy path. Ask what happens when an application falls outside the rules. Does the platform automatically identify the exception, retain the relevant context and route it to the right person for review?

During vendor evaluations, insist on seeing both: a genuinely no-touch journey for a straightforward merchant and an exception journey that shows how human review is handled when it is needed.

For a detailed breakdown of how to choose the best merchant onboarding software, see our guide: What to Look for in an Onboarding Platform: The Essential Checklist for Acquirers and PSPs.

‍

Real-world proof: More capacity without more manual work

A leading payment provider used OnBoard to replace a highly manual, fragmented onboarding process with connected automation. Since implementation, it has processed more than 15,000 applications with no human touch, shortened merchant time-to-live by 12 days, and reduced operational headcount by six FTEs.

That is scalability in operational terms: more onboarding capacity and faster activation without manual workload increasing at the same rate.

Read the full case study: How Smarter Onboarding Unlocked Rapid Growth for a Leading Payments Provider.

‍

Building a Future-Ready Merchant Onboarding Infrastructure: Products and Fraud 

Streamlining your existing process for today's merchants is just the foundation. The next, greater test of your infrastructure is scaling to accommodate not just more volume, but entirely new forms of business that didn't exist yesterday. This requires a product-centric mindset. “The world is moving so rapidly,” says Sheahan. “The concept of paying and being paid is changing at a rate of knots every single day, from multi-currency to crypto and even carbon credits.”

The notion of a homogenous intake is a relic of the past. The data confirms this shift is already reshaping the market:

  • McKinsey’s 2024 payments analysis finds the entire value chain is fragmenting under a proliferation of new rails and players.
  • Platforms and marketplaces are no longer niche; they now process a staggering 30% of all global consumer purchases.
  • McKinsey survey data shows that vertical-specific software solutions captured more than 50% of SME spending in the US in 2023.

This means payment providers’ daily intake is wildly diverse. A coffee shop using a basic POS, a subscription SaaS business billing overseas customers, and a complex DeFi app could all arrive in your queue on the same morning. Each merchant requires its own contracts, a unique automated risk assessment, verification rules, pricing, and ongoing monitoring requirement. 

Meanwhile, the idea of value continues to evolve. Stablecoins and tokenized money are becoming increasingly important within the payments ecosystem, although widespread adoption is still developing.

For onboarding teams, the point is not to predict which payment model wins. It is to build workflows that can adapt when new products, merchant types and risk requirements arrive.

Beyond new products and payment types, acquirers also face increasingly sophisticated fraud threats. Criminal networks are using AI-driven tactics and cross-border teams to probe onboarding systems for weaknesses. As Daniel Sheahan notes, every new product release is quickly tested by fraudsters looking to exploit gaps. Without the right infrastructure, acquirers are forced to slow processes and add manual checks, raising costs and frustrating merchants. With a unified, automated platform like OnBoard by MVSI, fraud and risk controls can be built into the onboarding workflow at scale, helping acquirers respond to evolving threats without forcing every merchant through additional manual review.

‍

How a product-centric architecture enables automated onboarding

The answer lies in adopting a product-centric, modular architecture. This approach allows a merchant onboarding platform to adapt more quickly to new jurisdictions, product lines, brands, or risk profiles through configuration instead of costly development projects. The core benefit is flexibility: Instead of relying on lengthy and expensive coding projects, teams can integrate new requirements seamlessly with fully configurable rules and workflows.

For example, supporting a new merchant category or payment product may require different documentation, risk rules and approval paths. In a configurable platform, those requirements can be introduced through workflow and rules configuration rather than rebuilding the core onboarding process from scratch.

‍

Why API-First Architecture Matters for Scalable Merchant Onboarding

An API-first architecture allows onboarding components and external data sources to connect without forcing teams to move information manually between systems. Identity verification, watchlist screening, document collection, credit and risk data, and internal systems can contribute to the same onboarding workflow while remaining independently maintainable.

Real-time data access can help teams validate information while the merchant is still engaged, request additional evidence sooner and make decisions with a more complete view of the application. It also supports a stronger audit record by keeping data inputs and workflow actions connected.

The scalability benefit is adaptability. When a data provider, risk rule or requirement changes, modular integrations and configurable workflows make it easier to update the affected part of the journey without rebuilding the entire onboarding process. FATF has highlighted how divergent AML/CFT requirements and inconsistent implementation can increase cost and reduce payment speed, reinforcing the need for infrastructure that can adapt as requirements evolve.

‍

How to Scale Across Compliance and Privacy Requirements

Even after breaking down silos and moving to a product-focused setup, payment providers face another difficult scaling challenge: applying financial crime controls and privacy requirements consistently across markets.

AML/CFT frameworks can require firms to collect, verify, retain and, in some circumstances, share specific information. Privacy regimes such as GDPR and CCPA place controls around how personal data is collected, used, retained and accessed.

The challenge is not that these regimes are inherently contradictory. It is that payment providers need to satisfy both within the same onboarding infrastructure, often across multiple jurisdictions and at high volume.

For teams trying to deliver instant onboarding, that creates a genuine operational squeeze. They need enough information to make defensible risk decisions, while also controlling what data is collected, why it is used, who can access it and how long it is retained.

‍

Balancing API compliance tools with data privacy regulations

This isn’t a theoretical problem; it’s a daily operational nightmare for compliance officers and product teams.

Globally, standard-setters have also acknowledged the need to balance these objectives. FATF revised Recommendation 2 to ensure compatibility between AML/CFT requirements and data-protection and privacy rules, while promoting information sharing among competent authorities.

For payment providers, the practical challenge is governance: knowing what information must be collected and retained, who can access it, why it is being used, when it can be shared, and when it should be deleted or restricted.

‍

Solving the compliance bind with automated risk assessment

You can’t manage that complexity reliably with a patchwork of point solutions and manual oversight. Compliance needs to be engineered into the onboarding architecture, not bolted on as an afterthought. Policy must become code.

In practical terms, that means translating policy into configurable rules, permissions, retention controls and review paths that can be applied consistently across the onboarding journey.

  • Access and workflow actions can be recorded with the relevant user, time, data and decision context, giving teams a clearer record of what happened and why.
  • Permissions, masking, retention and deletion rules can be configured around the provider’s policies and applicable requirements, helping teams govern how information is used throughout the merchant relationship.
  • Verification and screening components can be updated independently, reducing the need to redesign the entire onboarding journey when requirements or data sources change.

A unified, API-first architecture makes those controls easier to manage centrally while allowing individual components to evolve. That turns regulatory change into a controlled configuration and governance task rather than another reason to rebuild the onboarding process.

Conclusion: Laying the Foundation for Scalable Merchant Onboarding Success

‍Onboarding isn’t just a utility to be patched; it’s a core strategic function that fundamentally dictates your ability to grow, innovate, and compete. The payment providers who will capture the next decade of growth are not those who simply go faster, but those who stop managing isolated silos and start building integrated, intelligent, and inherently adaptable systems.

The secret to scaling is simple in concept but unforgiving in execution: it all hinges on the foundation. Investing from day one in a unified, automated, and API-first stack is how you scale with structure, not sprawl. It’s how you launch new services in weeks, not months. It’s how you convert more customers, not lose them to merchant friction. 

OnBoard by MVSI supports this model by bringing configurable workflows, API-based integrations and automated compliance controls into one connected platform. Eligible merchants can progress through no-touch onboarding when they meet defined rules and risk criteria, while exceptions and higher-risk cases are routed for review. This helps payment providers grow onboarding capacity without manual workload increasing at the same rate.

That gives payment providers a more adaptable foundation for new markets, products and merchant types, without rebuilding the onboarding journey every time the business changes.

Book a demo of OnBoard’s merchant onboarding platform.

‍

Disclaimer: This article is for general informational purposes only and does not constitute legal, regulatory, compliance or risk advice. Requirements vary by jurisdiction, business model, payment program and risk profile.

‍

Frequently Asked Questions

What is the difference between scalable merchant onboarding and end-to-end merchant onboarding?

End-to-end merchant onboarding describes the connected workflow from application intake through verification, risk assessment, approval, activation and ongoing due diligence. Scalable merchant onboarding describes the ability to run that workflow at higher volume without manual effort, headcount, cost or risk increasing at the same rate. In practice, end-to-end process design is the foundation that makes scalable onboarding possible.

Does scalable merchant onboarding eliminate human review?

No. Strong scalable onboarding models automate routine work and use management by exception, while complex, uncertain or higher-risk applications remain subject to appropriate human review.

Why does fragmented merchant onboarding become harder to manage at scale?

Fragmented systems create repeated data entry, manual handoffs, separate review queues and inconsistent visibility. As application volumes rise, those inefficiencies multiply and can increase onboarding delays, operational effort and merchant friction.

How can payment providers increase onboarding volume without increasing headcount at the same rate?

Payment providers can automate repeatable data collection, verification, screening, routing and lower-risk decisions, while sending exceptions and higher-risk cases to human reviewers with the relevant context.

What is the difference between fast and scalable merchant onboarding?

Fast onboarding reduces the time it takes an individual merchant to reach activation. Scalable onboarding maintains speed, control and consistency as application volumes, products, markets or partner channels grow.

What is scalable merchant onboarding?

Scalable merchant onboarding is the ability to handle growing application volumes without manual effort, headcount, cost or risk increasing at the same rate. It relies on connected data, configurable workflows, automation and management by exception.