Merchant Onboarding · Platform Capability

Merchant Onboarding Software for Banks, PSPs & Acquirers

Digitize and automate merchant onboarding from application and document collection through KYC/KYB, sanctions screening, risk assessment, underwriting, approval and activation. Connect onboarding directly with merchant management and payment acceptance infrastructure.

Discuss Your Onboarding Architecture Request a Platform Demo

Merchant application — MER-30291

Submitted 3 minutes ago

✓

Application

✓

KYC

Underwriting

Approval

Activation

Identity verification passed

Done

Sanctions screening cleared

Done

Risk assessment in review

Pending

Merchant activation

Queued

Digital Merchant Applications

Replace paper, email and fragmented application processes with configurable digital onboarding workflows.

Automated Verification & Decisioning

Coordinate KYC, KYB, document validation, sanctions screening, risk assessment and underwriting through connected workflows.

Faster Merchant Activation

Move approved merchants into merchant management, commercial configuration and payment acceptance without disconnected manual provisioning.

What Is Merchant Onboarding Software?

Merchant onboarding software is a digital platform that manages the process of acquiring and activating a new merchant, from application and document collection through identity and business verification, risk assessment, underwriting, approval and activation.

It replaces a process that has traditionally depended on paper forms, emailed documents, and manual verification queues with a structured digital workflow that a bank, PSP, PayFac, payment processor, or acquirer can configure and operate consistently across its merchant portfolio.

Merchant onboarding is the entry point into the merchant lifecycle. Once approved, the merchant record moves into ongoing merchant management, payment configuration, settlement, and operational processes — onboarding hands off a fully verified, activated merchant rather than operating as an isolated intake form.

Why Digital Merchant Onboarding Matters

Onboarding is the first experience a merchant has with an acquirer, and it sets the tone for everything that follows. A slow, document-heavy application process signals a slow, document-heavy relationship — and every day a merchant waits for approval is a day of transaction volume that isn't being processed.

Onboarding speed is not only a convenience metric. It affects merchant acquisition, because merchants comparing acquirers notice how long an application takes before they can process their first transaction.

It also affects operating cost: manual review scales with headcount and reviewer availability rather than with transaction volume, which becomes a constraint as a merchant portfolio grows.

A merchant onboarding platform built as a connected workflow — rather than a form submission followed by a manual queue — turns onboarding from an operational bottleneck into a repeatable, governable process that scales with the business.

Challenges with Traditional Merchant Onboarding

Many acquirers still onboard merchants through manual, paper-driven processes that introduce delays, errors, and inconsistent outcomes.

Paper-Based Processes

Applications and documents routed by email or in person slow every step that follows.

Manual KYC

Identity and business verification performed by hand is slower and less consistent than automated verification.

Long Approval Cycles

Underwriting decisions that depend on manual review queues can stretch onboarding from hours into days or weeks.

Fragmented Systems

Application, verification, and activation often live in separate tools, requiring manual handoffs between teams.

Compliance Challenges

Inconsistent manual verification increases the risk of onboarding errors and compliance gaps.

Poor Merchant Experience

A slow, opaque application process is often a new merchant's first — and most lasting — impression of the acquirer.

Inconsistent Underwriting Decisions

Manual review processes can produce inconsistent approval decisions, processing times, and outcomes depending on which reviewer handles a given application.

Digital Merchant Onboarding Lifecycle

Merchant onboarding can follow a common lifecycle while requirements, verification steps and decision rules vary by merchant type, geography, risk profile and onboarding policy.

Application

The merchant submits a digital application, replacing paper-based intake.

Business Information

Legal entity, ownership, and contact details are captured for reuse throughout onboarding.

Document Collection

Required documents are uploaded digitally rather than couriered or emailed.

Identity Verification

Business owners and principals are verified against submitted documentation.

KYB Verification

The business is verified for legal existence and registration status.

AML / Sanctions Screening

The applicant is screened against sanctions and configured watchlist sources.

Risk Assessment

A risk profile is generated from verification outcomes and business characteristics.

Underwriting

The risk profile and configured policy drive an approval, decline, or manual review decision.

Approval / Decline

Applications are resolved to an outcome, with unresolved cases routed for reviewer attention.

Contract Acceptance

The merchant reviews and accepts commercial terms digitally.

Pricing Assignment

Fee schedules and pricing configuration are assigned to the merchant record.

Merchant Activation

The merchant account is created and eligible payment acceptance channels are provisioned.

Application

Document upload

Business verify

Risk assessment

Merchant approval

Pricing assign

Business info

Identity check

Sanctions screen

Underwriting

Contract accept

Merchant activation

Application to activation: the twelve-stage onboarding workflow

Configurable Merchant Onboarding Workflows

Onboarding requirements can vary based on merchant type, business structure, country, geography, MCC, risk category, merchant segment, and regulatory requirements.

Configuration Dimensions

Onboarding workflows can be configured around merchant type, business structure, country and geography, MCC, risk category, and applicable regulatory requirements, so a single platform can support onboarding policies that differ across markets and merchant types.

Merchant Segments

Onboarding workflows can be tailored to different merchant segments, including individual merchants, SMEs, enterprise merchants, marketplaces, PayFac sub-merchants, and higher-risk businesses, each with a workflow suited to that segment's requirements.

Merchant Application & Document Collection

The application stage is where digital onboarding replaces paper intake, and where required fields and documents can vary by merchant type, country, business structure, MCC, risk category and onboarding policy.

Digital Application Forms

A structured digital form replaces paper or emailed application intake.

Business Information

Legal entity, registration, and business detail captured as part of the application.

Owner Information

Details on business owners and principals captured for downstream KYC verification.

Document Upload

Required documents are uploaded digitally as part of the application process.

Document Status

Applicants and reviewers can see the current status of submitted documents.

Missing-Document Handling

Incomplete submissions can be flagged so outstanding documents are requested rather than silently blocking the application.

Save / Resume

Where supported by configuration, applicants can save an in-progress application and resume it later rather than restarting.

Application Status

Applicants and internal teams can track where a given application sits in the onboarding process.

Merchant Verification & Document Validation

Verification is where onboarding delays and compliance risk most often originate. Coordinating verification steps through one workflow, rather than a manual queue, is central to what the platform manages.

KYC

Identity verification for the individual owners and principals associated with a merchant.

KYB

Business verification confirming legal existence and registration status of the applying entity.

OCR

Where supported, optical character recognition extracts data from uploaded documents to speed up review.

Document Validation

Uploaded documents can be checked for completeness and validity as part of the workflow, where supported.

Biometric Verification

Where genuinely required by risk policy and supported by configuration, biometric checks can confirm applicant identity.

Sanctions Screening

Applicants can be screened against configured sanctions and watchlist sources as part of the onboarding workflow.

Adverse Media

Where supported, adverse media checks can be included as an additional screening input.

Third-Party Providers

The platform is designed to integrate with external identity, business, and screening providers through its API-first architecture.

Merchant Risk Assessment & Underwriting

Underwriting brings verification outcomes and business attributes together into a decision, applied consistently rather than left entirely to individual reviewer judgment.

Verification ResultsBusiness AttributesMCCRisk SignalsGeographyTransaction Expectations

↓

Risk / Decision Engine

↓

ApproveDeclineManual Review

Risk Scoring

Risk inputs from verification and business attributes are combined into a risk profile used to inform the underwriting decision.

Decision Rules

Underwriting decisions are driven by configurable rules and risk thresholds rather than a single fixed policy.

Approve / Decline / Manual Review

Applications resolve to one of three outcomes: approval, decline, or routing to manual review.

Exception Handling

Where policy and risk signals don't support an automatic decision, applications move into a manual review path rather than stalling.

A note on decisioning: Underwriting decisions are driven by configured rules and risk thresholds. This page does not claim AI/ML-based decisioning; confirm the specific decisioning approach used in your deployment with solution engineering.

Exception Handling & Manual Underwriting

Enterprise onboarding is not fully straight-through. Where an application requires manual attention, the platform supports:

Manual review queue for applications that don't clear automated decisioning

Reviewer assignment for cases requiring attention

Requests for additional documentation from the applicant

Reason codes attached to decisions and escalations

Escalation paths for higher-risk or ambiguous cases

Approval, decline, or re-review outcomes recorded against the application

An audit trail of manual actions taken during review

Merchant Contract & Pricing Setup

Once an application is approved, commercial setup happens as part of onboarding, before the merchant record moves into ongoing merchant management.

Contract Acceptance

The merchant reviews and accepts commercial terms digitally as part of the onboarding flow.

Pricing Assignment

A fee schedule is assigned to the merchant record based on configured pricing policy.

MDR & Fee Configuration

Merchant discount rate and fee configuration are set during onboarding to reflect the agreed commercial terms.

Commission & Revenue Sharing

Where applicable to the merchant's onboarding model, commission or revenue-sharing terms can be configured.

Settlement Terms

Settlement terms relevant to the merchant are established as part of onboarding, ahead of activation.

Ongoing pricing management, contract renewals, and ongoing commercial administration are handled in Merchant Management Software; this section covers what happens specifically during onboarding.

From Merchant Approval to Activation

Approval is not the finish line — activation is. Once approved, the merchant record moves through commercial and payment configuration before it's ready to accept transactions.

Onboarding Approved

Merchant Management Record Created

Commercial Configuration

Payment Acceptance Configuration

Settlement Profile

Merchant Activated

Payment Channel Provisioning

POS

POS terminal assignment configured as part of activation for eligible merchants.

Explore →

SoftPOS

SoftPOS acceptance configured for eligible merchants as part of activation.

Explore →

QR

QR-based acceptance configured for eligible merchants as part of activation.

Explore →

Payment Gateway

Online payment acceptance configured alongside in-store channels for eligible merchants.

Explore →

Merchant Management Record

An approved application creates the merchant record that Merchant Management Software operates going forward.

Settlement Profile

Settlement cycle and payout configuration are established as part of activation. Explore Settlement Engine →

A note on channel provisioning: Eligible payment acceptance channels can be provisioned based on the merchant's approved profile, configuration and onboarding policy. Not every merchant is provisioned with every channel automatically; provisioning follows the merchant's approved profile and configuration

Merchant Onboarding Funnel & Analytics

Visibility into where applications succeed, stall, or drop off is central to operating onboarding as a managed process rather than a black box.

Applications Started

Applications Completed

Verification Passed

Underwriting

Approved

Contract Accepted

Activated

First Transaction

Onboarding metrics commonly tracked at each stage include application completion rate, verification pass rate, approval rate, manual review rate, activation rate, time to activation, and time to first transaction.

Exact metrics and reporting available in your deployment should be confirmed with solution engineering.

Notifications & Application Status

Keeping applicants and internal teams informed of status reduces both applicant frustration and unnecessary status-check inquiries.

Application Events

Notifications can be configured around key onboarding events, including application received, document missing, verification failed, additional information required, approved, declined, contract pending, and activation completed.

Notification Channels

Where supported by configuration, status updates can be delivered through channels such as email, portal notifications, and webhook events to connected systems. Confirm the specific channels enabled for your deployment with solution engineering.

Role-Based Operations & Audit Trail

Onboarding touches multiple internal functions — operations, compliance, risk, and finance — each of which needs appropriate access to the parts of the process relevant to their role.

Role-Based Onboarding Operations

Roles commonly involved in onboarding include merchant operations, compliance, KYC reviewers, risk analysts, underwriters, relationship managers, finance, and platform administrators. Access can be scoped so each role reaches the onboarding tasks and decisions relevant to it.

Audit Trail & Decision Governance

Onboarding activity is tracked to support audit and compliance review, including application changes, document changes, verification results, risk results, underwriting decisions, the reviewer involved, decision reasons, manual overrides, approvals, and activation.

Integrate With Existing KYC/KYB & Compliance Providers

Many acquirers already work with specific identity, business, or sanctions screening providers. Onboarding is designed to connect to those providers rather than replace them outright.

API-Based Integration

Verification providers are connected through the platform's API-first architecture.

Webhook Support

Provider responses and status changes can be received through supported integration patterns.

Response Normalization

Verification results from different providers are handled within a consistent onboarding workflow.

Verification Status

The current status of a verification check is reflected in the application's onboarding stage.

Failure Handling

Failed or inconclusive verification results can route an application to manual review rather than a dead end.

Retry Handling

Where supported, verification checks can be retried as part of the workflow rather than requiring a new application.

A note on integration architecture: This section describes integration with third-party KYC/KYB and compliance providers at a conceptual level. It does not claim a specific provider abstraction layer beyond what is actually implemented — confirm supported providers and integration patterns with solution engineering.

Merchant Onboarding vs Merchant Management

	Merchant Onboarding	Merchant Management
Scope	Application → Verification → Risk → Underwriting → Approval → Activation	Merchant Master Data → Hierarchy → Pricing → Contracts → Payment Configuration → Ongoing Lifecycle
Primary question	Should this merchant be approved and activated?	How is this merchant's relationship operated over time?
Duration	A defined process with a start and an end	Continuous, for the life of the merchant relationship

Merchant onboarding creates and activates the merchant relationship. Merchant management maintains and operates that relationship throughout its lifecycle. Explore Merchant Management Software for how an activated merchant is managed going forward.

Merchant Onboarding Software vs eKYC

eKYC is a verification capability — it confirms an individual's or business's identity against submitted documentation and data sources.

Merchant onboarding is the broader lifecycle that eKYC feeds into: Application → Documents → KYC/KYB → Screening → Risk → Underwriting → Approval → Contract → Activation. Explore the DigiPay.Guru eKYC Platform for verification-specific capability.

Merchant Acquisition vs Merchant Onboarding

Merchant acquisition is the broader commercial process of attracting and winning merchants — sales, partnerships, and business development that bring a prospective merchant to the point of applying.

Merchant onboarding is the operational process of collecting, verifying, assessing, approving and activating those merchants once they apply. Onboarding is what turns a won prospect into a live, transacting merchant.

PayFac & Sub-Merchant Onboarding

Payment facilitators onboarding sub-merchants can follow the same underlying onboarding lifecycle, configured for sub-merchant hierarchy and PayFac-specific requirements.

PayFac

→

Sub-Merchant Application

→

KYC / KYB

→

Risk Assessment

→

Underwriting

→

Approval

→

Sub-Merchant Activation

Hierarchy, underwriting policy, pricing, risk treatment, and activation for sub-merchants are configured to reflect the PayFac's own program requirements. Confirm the specific PayFac and sub-merchant capabilities enabled for your deployment with solution engineering.

Merchant Onboarding Software for Banks, PSPs & Acquirers

Banks & Acquirers

Large merchant portfolios, regulatory workflows and structured underwriting.

PSPs

Digital onboarding connected to external verification and payment infrastructure.

PayFacs

Sub-merchant onboarding and underwriting under a payment facilitator model.

Payment Processors

Onboarding infrastructure connected to merchant configuration and processing.

Fintechs

Digital merchant acquisition without building the entire onboarding stack internally.

Implementing Merchant Onboarding Software

Moving from an existing onboarding process — manual or partially digital — to DigiPay.Guru's onboarding platform follows a structured implementation path.

Existing Process Assessment

Review current onboarding steps, systems, and pain points.

Merchant Data & Workflow Mapping

Map existing merchant data and onboarding workflow to the target platform configuration.

KYC/KYB Provider Integration

Connect required identity, business, and screening providers.

Workflow & Decision Rule Configuration

Configure onboarding stages, required documents, and underwriting rules.

UAT

Validate the configured workflow against representative test applications.

Pilot Launch

Run onboarding for a limited scope of merchants before wider rollout.

Migration / Production Rollout

Move to full production onboarding once the pilot has validated the configuration.

What Should You Look for in Merchant Onboarding Software?

Configurable workflows that reflect differences across merchant type, geography, MCC, and risk category

Coordinated KYC/KYB and sanctions screening rather than disconnected manual checks

Clear approve, decline, and manual review decisioning with reason codes and an audit trail

Integration flexibility with existing verification and compliance providers

A direct handoff into merchant management, commercial configuration, and payment acceptance — not a separate downstream setup project

Role-based access appropriate to compliance, risk, operations, and finance functions

Visibility into funnel performance and where applications stall

Why DigiPay.Guru

Onboarding on DigiPay.Guru is not a standalone module bolted onto an acquiring platform — it's the entry point into the same merchant record that powers management, payment acceptance, and settlement. An approved merchant doesn't wait for a second system to catch up; activation happens on the same platform that just finished verifying them.

Discuss Your Onboarding Architecture Request a Platform Demo

Frequently asked questions

A merchant onboarding platform is the system of record and workflow engine that coordinates every step of onboarding — application, verification, risk assessment, underwriting, and activation — as one connected process rather than separate manual tasks.

Merchant onboarding creates and activates the merchant relationship: application, verification, risk, underwriting, approval and activation. Merchant management maintains and operates that relationship afterward: merchant master data, hierarchy, pricing, contracts, payment configuration and ongoing lifecycle.

eKYC is a verification capability focused on confirming identity. Merchant onboarding is the broader lifecycle that includes application, documents, KYC/KYB, screening, risk assessment, underwriting, approval, contracting and activation.

KYC (Know Your Customer) verifies the individuals associated with a merchant, such as owners and principals. KYB (Know Your Business) verifies the business entity itself. Merchant onboarding may require both, depending on merchant type, jurisdiction and policy.

Merchant underwriting is the decisioning step where verification results, business attributes, risk signals and configured policy are evaluated to approve, decline, or route an application to manual review.

Underwriting combines verification outcomes with business attributes and configured risk rules to generate a decision. Where policy allows automated decisioning, an application can move to approve, decline, or manual review without a reviewer touching every case.

Applications that don't clear automated verification can be routed to a manual review queue, where a reviewer can request additional documentation, escalate, or make a final approve or decline decision.

Yes. Onboarding requirements, documents, and verification steps can be configured to reflect differences across merchant type, geography, MCC, risk category and regulatory requirements.

Yes. Sub-merchant onboarding under a PayFac model can follow the same application, verification, risk, underwriting and activation stages, configured for sub-merchant hierarchy and payment facilitator requirements.

Yes. The platform is designed to integrate with third-party identity, business and sanctions screening providers through its API-first architecture.

Where supported by configuration, merchants can save an in-progress application and resume it later rather than restarting from the beginning.

Once an application is approved, the merchant record moves into merchant management, commercial and payment configuration are applied, and eligible payment acceptance channels are provisioned according to the merchant's approved profile.

Common onboarding metrics include application completion rate, verification pass rate, approval rate, manual review rate, activation rate, time to activation and time to first transaction.

Migration typically starts with an assessment of the existing process, mapping merchant data and workflows, integrating KYC/KYB providers, configuring workflow and decision rules, running UAT, and rolling out through a pilot before full production migration.

Ready to Modernize Merchant Onboarding?

Discuss your current application, KYC/KYB, underwriting and activation workflow with the DigiPay.Guru team.

Discuss Your Onboarding Architecture Request a Platform Demo

Look through your eyes of insight to our insightful thoughts

DigiPay.Guru is born to simplify financial transactions. We love discussing the latest finTech solutions. We write regular blogs where we cover insightful topics with our insightful thoughts to cater you with imperative informations.