PayFac Master AccountSponsor Bank arrangementSub-M 1Sub-M 2Sub-M 3Sub-M 4Sub-M 5Sub-M 6Split Settlement · Funding · Reserve ManagementMaster–sub-merchant model as core architecture

What Is a Payment Facilitator?

A Payment Facilitator (PayFac) aggregates payment acceptance for many sub-merchants under a single master merchant account, rather than each sub-merchant holding its own direct acquiring relationship. The PayFac onboards sub-merchants under its own umbrella — typically operating under a sponsor bank relationship for the underlying acquiring license — and takes on responsibility for underwriting, risk monitoring, and settlement across its sub-merchant portfolio.

That model is distinct from both a traditional merchant acquirer and a standard PSP. A traditional acquirer maintains a direct acquiring relationship with each individual merchant. A PSP typically routes and processes payments on behalf of merchants without necessarily aggregating them under one master account. A PayFac sits further along that spectrum: it owns the sub-merchant relationship end to end — onboarding, underwriting, and settlement — under its own master account, which is why software platforms are usually built specifically with sub-merchant management at the center, not added as an afterthought.

Master Merchant AccountPayFacSub-M 1Sub-M 2Sub-M 3Sub-M 4Sub-M 5Split Settlement EngineOne transaction, funds split accurately across every partyMaster–sub-merchant model

Traditional Merchant Acquirer vs. PSP vs. PayFac

DimensionTraditional Merchant AcquirerPSPPayFac
Merchant relationshipDirect relationship per merchantProcesses on behalf of merchants, relationship structure variesSub-merchants onboarded under one master account
UnderwritingPerformed per merchant by the acquirerMay be performed by underlying acquiring partnersPerformed by the PayFac under its sponsor bank arrangement
Onboarding speedTypically slower, individual underwritingVaries by PSP modelDesigned for fast, high-volume sub-merchant activation
Settlement structureDirect settlement to the merchantVaries by PSP modelSplit settlement from the master account to sub-merchants
Best suited forLarger, individually underwritten merchantsMerchants wanting a simplified processing relationshipSoftware platforms embedding payments for many smaller sub-merchants

Challenges of Building a Payment Facilitator Business

01

Operational complexity.

Managing underwriting, risk, and settlement across a large sub-merchant portfolio is a fundamentally different operational challenge than running a single merchant account.

02

Sub-merchant management at scale.

Manual processes that work for dozens of sub-merchants break down at hundreds or thousands.

03

Funding workflows.

Getting split settlement and sub-merchant funding right — accurately and on schedule — is central to the PayFac model working at all.

04

Commercial flexibility.

Different sub-merchant segments often need different pricing and fee structures, which a rigid system can't easily support.

05

Sponsor bank coordination.

Aligning platform operations with sponsor bank requirements adds a layer of coordination beyond standard acquiring.

06

Risk management.

Underwriting and monitoring thousands of smaller sub-merchants requires different risk tooling than underwriting a handful of large merchants.

07

Scaling challenges.

Growing a sub-merchant base quickly without operational strain requires infrastructure built for that scale from the outset.

Build a Modern PayFac Platform with DigiPay.Guru

DigiPay.Guru provides the technology platform covering the complete PayFac lifecycle — sub-merchant onboarding, payment acceptance, processing, split settlement, funding, and reporting — built specifically around the master–sub-merchant model rather than a standard merchant acquiring platform with sub-merchant features added on. The platform is the technology layer; sponsor bank relationships, licensing, and regulatory obligations remain the PayFac's own arrangements, established directly with its sponsor bank and applicable regulators.

Sub-Merchant Onboarding · KYC/KYB · Approval WorkflowsDigiPay.Guru PayFac PlatformSplit Settlement · Funding · Reserve ManagementSponsor Bank / Acquirer Infrastructure

Sub-Merchant Lifecycle Management

ApplicationDigital formKYC / KYBIdentity checkUnderwritingPolicy-drivenActivationUnder master acctActive Sub-Merchant

Digital Sub-Merchant Onboarding

A digital application flow for sub-merchants joining under your master account.

KYC & KYB Integration

Identity and business verification integrated into the onboarding workflow.

Approval Workflows

Configurable underwriting and approval steps applied consistently across sub-merchants.

Merchant Hierarchies

Master account and sub-merchant relationships modeled accurately.

Merchant Profiles

A complete profile per sub-merchant, connected to their processing and funding history.

Merchant Self-Service Portal

Sub-merchants access their own transaction and funding data directly.

Manual Sub-Merchant Management vs. Automated Lifecycle Management

DimensionManual Sub-Merchant ManagementAutomated Lifecycle with DigiPay.Guru
Onboarding at volumeBottlenecked by manual review capacityDigital onboarding supports high-volume activation
Underwriting consistencyVaries by reviewerPolicy-driven, applied consistently
Funding accuracyManual calculation, error-prone at scaleSplit settlement and funding calculated automatically
Sub-merchant supportSupport-ticket dependentSelf-service portal reduces routine requests

Comprehensive Payment Acceptance

POS Payments

In-store card-present acceptance for sub-merchants with a physical presence.

SoftPOS

NFC-enabled Android smartphones accepting contactless payments.

QR Payments

Static and dynamic QR code acceptance for sub-merchants.

E-commerce Payments

Online, card-not-present acceptance for digitally-selling sub-merchants.

Payment Gateway

Gateway connectivity supporting embedded checkout experiences.

Digital Wallet Integration

Wallet-based payment methods accepted alongside cards.

Payment Processing & Funding

Transaction $100Split Settlement EngineSub-Merchant$92PayFac Fee$5Reserve$3Configurable per sub-merchantAutomated, accurate, every transaction

Authorization Engine

Real-time transaction validation and decisioning at the sub-merchant level.

Payment Routing

Transactions routed through the master account's acquiring relationships.

Settlement Engine

Configurable settlement cycles applied per sub-merchant.

Sub-Merchant Funding

Funds distributed to sub-merchants accurately and on schedule.

Split Settlement

Transaction funds divided across sub-merchant, platform fee, and other parties automatically.

Reserve Management

Rolling and fixed reserve models configurable per sub-merchant.

Commercial Management

Merchant Pricing

Pricing models configured per sub-merchant or segment.

Billing & Invoicing

Platform fees and recurring charges invoiced automatically.

Revenue Sharing

Revenue splits between the PayFac and its sub-merchants calculated automatically.

Commission Management

Commission arrangements for referral or partner channels calculated automatically.

Merchant Statements

Settlement and funding statements generated and available to sub-merchants.

Fee Configuration

Fee structures configured to match each sub-merchant's commercial agreement.

Separate Operational Systems vs. Unified PayFac Platform

DimensionSeparate Operational SystemsUnified Platform with DigiPay.Guru
Sub-merchant dataFragmented across onboarding, processing, and funding systemsOne connected sub-merchant record
Funding accuracyManually reconciled across systemsCalculated directly from processed transaction data
Risk visibilityAssembled manually across sourcesUnified risk view across the sub-merchant portfolio
ReportingReconciled manually across disconnected toolsUnified reporting across the whole portfolio

Risk, Compliance & Operations

Risk & Fraud Management

Configurable rules and monitoring applied across the sub-merchant portfolio.

Dispute & Chargeback Management

Structured case handling for sub-merchant disputes and chargebacks.

Operational Dashboards

Live visibility into sub-merchant activity and portfolio health.

Audit Trails

Every configuration change and transaction event logged for review.

Reporting & Analytics

Unified reporting across sub-merchants, transactions, and funding.

Role-Based Access Control

Platform access controlled by role, across internal teams and sub-merchant users.

On sponsor banks and regulatory obligations: DigiPay.Guru provides the technology platform for sub-merchant onboarding, processing, funding, and reporting. Sponsor bank sponsorship, acquiring licenses, and the regulatory and compliance obligations that come with operating as a PayFac remain arrangements the PayFac establishes and maintains directly with its sponsor bank and applicable regulators — DigiPay.Guru does not provide sponsorship, licensing, or legal compliance services.

API-First Integration

The PayFac model works best when payments are embedded into your own software. DigiPay.Guru's API-first architecture is built for that integration pattern.

Your Software ProductDigiPay.Guru APIsOnboardingPaymentsFundingWebhooks · Real-time eventsNative embedded experience

REST APIs

Sub-merchant onboarding, processing, and funding exposed through REST APIs.

Webhook Notifications

Real-time event notifications for sub-merchant and transaction activity.

Developer Portal

Documentation and tooling supporting integration teams.

Third-Party Integrations

API-first architecture designed to integrate with other systems in your product ecosystem.

Embedded Payments

Sub-merchant onboarding and payment acceptance embedded directly into your own software.

Multi-Tenant Architecture

Manage multiple sub-merchant programs or verticals from one platform instance.

Business Benefits for PayFacs

Faster acquisition

Digital onboarding supports high-volume sub-merchant activation

Operational efficiency

Automated funding and settlement reduce manual reconciliation

Commercial flexibility

Pricing and fees configured per sub-merchant segment

Scalable operations

Sub-merchant portfolio grows without proportional operational strain

Better sub-merchant experience

Self-service visibility into transactions and funding

Ecosystem expansion

Embedded APIs support new verticals and product integrations

Example PayFac Use Cases

SaaS Platforms

Marketplace Platforms

Vertical SaaS Providers

Fintech Companies

Embedded Finance Platforms

Digital Commerce Providers

Why DigiPay.Guru for Payment Facilitators

DigiPay.Guru is built around the master–sub-merchant model as a first-class architectural decision, not a feature layered onto standard merchant acquiring. Sub-merchant onboarding, split settlement, funding, and reserve management are core to the platform, and the API-first design is built for PayFacs that want to embed payments directly into their own product rather than send sub-merchants to a separate acquiring experience.

Frequently asked questions

Payment Facilitator software is the platform a PayFac uses to onboard and manage sub-merchants under its master merchant account, process their transactions, split and fund settlement, and manage the commercial and risk relationship with each sub-merchant.

Sub-merchants are onboarded digitally with integrated KYC/KYB verification and configurable approval workflows, so a PayFac can activate sub-merchants quickly while applying consistent underwriting policy.

Yes. Split settlement distributes a transaction's funds across the sub-merchant, the PayFac's platform fee, and any other configured parties automatically.

Yes. Reserve models, including rolling reserves, are configurable per sub-merchant to manage exposure to chargebacks and refunds.

Yes. Pricing, fee structures, and commercial terms are configurable per sub-merchant or sub-merchant segment.

The platform's API-first architecture is built to support integration with the acquiring and settlement infrastructure a PayFac's sponsor bank relationship requires. DigiPay.Guru provides the technology platform; sponsor bank sponsorship, licensing, and regulatory obligations remain arrangements the PayFac establishes directly with its sponsor bank and relevant regulators.

Yes. Multi-tenant architecture supports PayFacs managing multiple sub-merchant portfolios or vertical-specific programs from one platform instance.

Yes. REST APIs and webhooks are designed to support embedding sub-merchant onboarding and payment acceptance directly into a PayFac's own software product.

By automating sub-merchant onboarding, funding, settlement, and reporting, the platform lets a PayFac grow its sub-merchant base without a proportional increase in operational effort.

Sub-merchant performance, transaction analytics, revenue analytics, funding reports, and operational KPIs are available through unified reporting drawn from the same underlying platform data.

Ready to Launch or Scale Your PayFac Business?

Talk to the DigiPay.Guru team about your sub-merchant portfolio and sponsor bank arrangement, or book a demo to see the platform configured for a PayFac use case.

Section Page CTA

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.