A sub-merchant is a business that accepts card payments under a payment facilitator's master merchant account, instead of holding its own direct account with an acquiring bank. The facilitator sponsors you under its master MID and handles underwriting, onboarding, compliance and payouts on your behalf - which is exactly why a sub-merchant can be live in minutes to days rather than the weeks a traditional account takes.
The term only makes sense next to its parent. A payment facilitator (PayFac) holds one master merchant account and a master MID with an acquirer, then onboards many businesses beneath it. Each of those businesses is a sub-merchant: it transacts on the facilitator's account rather than opening its own. As Infinicept's definition puts it, the sub-merchant runs under the PayFac's umbrella while the PayFac owns the acquiring relationship.
A direct merchant account is your own contract and MID with an acquiring bank - powerful, but it means underwriting queues before you can charge a card. A sub-merchant skips that queue because underwriting happens at the master-account level. Industry write-ups note that payment facilitators approve new sub-merchants in minutes, while a traditional account can take one to two weeks. You trade a little control for a lot of speed.
Do not confuse "sub" with "not the seller". A sub-merchant is still the merchant of record for its own sales - your brand on the statement, your customer, your pricing. That is the reverse of an MoR provider like Paddle, which becomes the legal seller and owns the transaction. The PayFac sub-merchant model keeps the relationship yours while the facilitator handles the plumbing.
Being a sub-merchant is what lets a solo builder charge cards without opening a bank-grade merchant account first. paas.build is a productised PayFac on UniPaaS (an FCA-authorised Payment Institution, No. 929994): one prompt creates a real capped sub-merchant account, live the same day via progressive KYB, at 3.9% flat, no company needed. And because a platform's own users can each be onboarded as sub-merchants, this is the model behind "your users get paid too" - marketplaces, communities and agent-built apps that split payments to their members.
A merchant account is a direct contract with an acquiring bank and its own MID, which takes underwriting time to open. A sub-merchant instead operates under a payment facilitator's master merchant account, so it inherits an already-approved framework and can go live far faster.
Yes. In the PayFac model the sub-merchant remains the legal seller - its name on the receipt and its customer relationship - while the facilitator provides the account and infrastructure. This is the opposite of a Merchant of Record model, where the provider becomes the seller. On paas.build you are the sub-merchant, so you stay the merchant.
Because underwriting is handled at the master-account level, payment facilitators can approve new sub-merchants in minutes rather than the one-to-two weeks a traditional account takes. On paas.build you get a real capped sub-merchant account the same session, with verification running in the background via progressive KYB.
Not on paas.build. Because you onboard as a sub-merchant under UniPaaS's FCA-authorised master account, an individual or sole trader can go live without first registering a company - the facilitator's regulated framework covers you.