A sub-merchant is any business that accepts card payments through a payment facilitator rather than maintaining a direct relationship with an acquirer. Instead of undergoing traditional bank-level underwriting, the sub-merchant is onboarded, monitored, and processed under the PayFac's master merchant account. This model powers the payment capabilities of platforms ranging from freelance marketplaces to vertical SaaS products.
How Sub-Merchant Works
Understanding the sub-merchant model requires tracing the full flow of a payment from card swipe to settlement. Each step involves a distinct handoff between parties.
Business applies to a PayFac
A business (the future sub-merchant) applies to a payment facilitator — not an acquirer directly. The PayFac collects KYC information, business details, and banking credentials through its own onboarding flow.
PayFac runs real-time underwriting
The PayFac screens the applicant against sanctions lists (OFAC, EU), checks the MATCH/TMF database, verifies business identity, and applies its own risk scoring — often in seconds using automated decisioning engines.
Sub-merchant ID (SMID) is assigned
Upon approval, the PayFac assigns a unique Sub-Merchant ID that maps the business to the PayFac's master MID. The acquirer sees all transactions from that sub-merchant grouped under the PayFac's umbrella account.
Transactions route through the master MID
When a customer pays a sub-merchant, the transaction flows through the PayFac's processing infrastructure to the acquirer and card networks. The PayFac's name typically appears in the merchant descriptor alongside the sub-merchant's name.
PayFac settles funds to the sub-merchant
The acquirer settles funds to the PayFac's account. The PayFac then disburses net funds (gross amount minus fees, reserves, and any held amounts) to the sub-merchant's bank account on its own settlement schedule.
Ongoing monitoring and compliance
The PayFac continuously monitors sub-merchant transaction velocity, chargeback ratios, and risk signals. Card network rules require PayFacs to report and manage their sub-merchant portfolio proactively.
Why Sub-Merchant Matters
The sub-merchant model fundamentally changed how businesses access payment acceptance, lowering the barrier to entry for millions of companies worldwide. It is one of the primary engines behind the growth of the platform economy.
Traditional merchant account underwriting could take five to seven business days and required significant documentation. Under the PayFac model, sub-merchant approval can happen in under five minutes. A 2023 report by the Strawhecker Group estimated that payment facilitators process more than $2 trillion in annual payment volume globally, with sub-merchant portfolios growing at roughly 20% year-over-year as software platforms embed payments into their products.
For small and mid-sized businesses, the operational overhead of maintaining a direct acquirer relationship — dedicated compliance programs, direct PCI scope, individual rate negotiations — is substantial. Sub-merchant arrangements allow businesses to offload this complexity. Nilson Report data shows that PayFac-style aggregated processing now accounts for more than 30% of all card-present and card-not-present SMB volume in the United States. For platforms with embedded payments, sub-merchant monetization through payment markup is increasingly a larger revenue line than software subscription fees.
Card network visibility
Visa and Mastercard require payment facilitators to register formally and report sub-merchant data — including name, address, MCC, and processing volume — as part of their merchant monitoring programs. Non-compliance can result in fines or loss of PayFac registration.
Sub-Merchant vs. Direct Merchant Account
These two models represent opposite ends of the payment acceptance spectrum. Choosing between them depends on the business's risk profile, volume, and operational resources.
| Factor | Sub-Merchant | Direct Merchant Account |
|---|---|---|
| Onboarding time | Minutes to hours | Days to weeks |
| Who underwrites | Payment facilitator | Acquirer directly |
| Merchant ID | Shared master MID (SMID assigned) | Dedicated MID |
| PCI DSS scope | Reduced (PayFac manages most scope) | Full scope |
| Pricing | PayFac-set rates (often flat or blended) | Negotiated interchange-plus |
| Chargeback liability | PayFac absorbs first; passes back contractually | Merchant holds directly |
| Volume cap | Typically $1M/year before graduation required | No cap |
| Best for | Startups, SMBs, platform users | High-volume, established merchants |
Types of Sub-Merchant
Not all sub-merchant arrangements are identical. The risk profile, vertical, and platform type drive meaningful variation in how sub-merchants are structured and managed.
Standard e-commerce sub-merchants are the most common type — online retailers, service providers, and digital goods sellers onboarded by horizontal PayFacs like Stripe or Square. They typically process below $500K annually and benefit most from the simplicity of the model.
Marketplace sub-merchants are sellers or service providers operating within a two-sided platform — think individual Etsy sellers, Uber drivers, or Airbnb hosts. The merchant of record distinction here matters: in some models the platform is the MoR, in others the individual sub-merchant is.
SaaS-embedded sub-merchants arise when vertical software platforms (e.g., a dental practice management system, a gym scheduling app) enable their customers to accept payments. These sub-merchants are often non-payments-native businesses for whom payment acceptance is incidental to their core activity.
High-risk sub-merchants are businesses in elevated-risk verticals (travel, nutraceuticals, firearms accessories) that require additional underwriting scrutiny, higher reserve requirements, and often separate PayFac licensing or acquirer approval before the PayFac can onboard them at all.
Best Practices
For Merchants
Start by confirming that your expected annual processing volume stays below the card network caps — typically $1 million — before committing to a sub-merchant arrangement. If you anticipate growing past that threshold within 12 to 18 months, ask your PayFac about their merchant graduation process upfront.
Review the PayFac's reserve policy carefully. Rolling reserves of 5–10% held for 90–180 days are standard for new sub-merchants and can materially affect cash flow. Negotiate reserve release timelines before signing.
Maintain accurate and current business information with your PayFac at all times. Changes to your legal entity, bank account, or business model need to be reported promptly — failure to do so can result in account suspension or increased scrutiny from the PayFac's risk team.
For Developers
When building a PayFac-in-a-box or embedding payments into a SaaS platform, design your sub-merchant onboarding flow to collect all card-network-required data fields from day one: legal business name, DBA name, address, MCC, ownership structure, and beneficial ownership information. Retrofitting these data requirements after launch is costly.
Implement sub-merchant volume monitoring at the application layer. Set alerts well below the $1M card network threshold — around $800K — to give operational teams time to prepare documentation for merchant account graduation without service interruption.
Store Sub-Merchant IDs (SMIDs) in a dedicated data model with versioning, as PayFacs sometimes reissue SMIDs during platform migrations. Losing the SMID mapping breaks transaction reconciliation.
Common Mistakes
Confusing the PayFac and the sub-merchant's tax obligations. The PayFac reports aggregated settlement activity to the IRS (Form 1099-K), but tax remittance responsibility lies with the sub-merchant. Many sub-merchants incorrectly assume the PayFac handles their tax obligations entirely.
Ignoring acceptable use policy drift. Sub-merchants sometimes expand their product or service offerings post-onboarding into categories prohibited by the PayFac's AUP (e.g., adding CBD products to an otherwise standard retail business). This violates the sub-merchant agreement and can trigger immediate account termination.
Underestimating chargeback exposure. New sub-merchants frequently exceed Visa's 1% or Mastercard's 1.5% chargeback thresholds within the first few months due to insufficient fraud controls, leading to PayFac-imposed volume restrictions or account holds.
Failing to update business information. Changes to bank accounts, ownership, or business address that are not reported to the PayFac can trigger AML flags or payment freezes, particularly under enhanced due diligence programs.
Assuming sub-merchant status is permanent. High-volume sub-merchants that do not proactively engage with their PayFac about transitioning to a direct merchant account risk abrupt termination once network volume thresholds are exceeded, creating a payment continuity risk.
Sub-Merchant and Tagada
Sub-merchant orchestration is a core use case for platforms building payment infrastructure on top of Tagada. When a platform needs to onboard multiple sub-merchants under a single processing relationship — routing each merchant's transactions to the optimal acquirer while maintaining per-sub-merchant reporting and settlement — Tagada's payment orchestration layer handles the complexity.
Tagada enables platforms to route sub-merchant transactions across multiple acquirers based on geography, card type, or risk profile — without rebuilding the routing logic for each PayFac relationship. This is especially valuable for platforms operating across multiple countries where a single acquirer rarely delivers optimal authorization rates everywhere.
For platforms managing large sub-merchant portfolios, Tagada also provides consolidated reconciliation across processors, making it easier to produce per-sub-merchant settlement reports and maintain clean audit trails — a requirement under most card network PayFac registration programs.