A payment facilitator or marketplace earns on payments made to businesses it signs as sub-merchants. The model only pays if signing them is quick and cheap, since a platform may onboard hundreds a week, and it only stays safe if every one of them is still checked properly.
That tension shapes everything about sub-merchant onboarding and management. This page covers onboarding as an API flow with its checks, then sub-merchant settlement with split payouts and what happens after go-live.
Sub-merchant onboarding as an API flow
For a software platform, the sign-up has to happen inside its own product. Speed matters. A customer of a booking tool or an invoicing app should start taking payments from a settings page, not from a separate form with another company's logo. The flow below is how that usually works.
- The user signs up for payments inside your product.
- Your product sends the business and owner details to the onboarding API.
- KYB and KYC checks run through your verification provider.
- The risk score is calculated against your rules.
- A webhook returns the decision: approved, more information needed, or declined.
- On approval, the sub-merchant account and its pricing are created.
- The sub-merchant takes its first payment, and payouts follow once all checks are complete.
Ask your sponsoring acquirer early which checks must finish before the first payment and which before the first payout. The answer decides how much of this flow can happen in the first few minutes.
A KYB and KYC workflow for sub-merchants
A submerchant onboarding KYC/KYB workflow runs the checks any merchant gets, only through an API. The table shows who decides at each stage.
| Stage | Data collected | Check | Who decides |
|---|---|---|---|
| Business | Legal name, registration number, address, website | Registry lookup, sanctions screening | Automated |
| People | Owners and directors, with identity details | Identity verification, sanctions and PEP screening | Automated, with escalation |
| Activity | Products, expected volume, average payment | Category and risk scoring | Rules, then a person for edge cases |
| Bank account | Account in the business's own name | Ownership check | Automated |
| Review | Anything flagged above | Manual review with the full file | Your risk team |
Most sub-merchants should never reach the last row. If a large share does, the rules are too strict or the data collected at sign-up is too thin.
Sub-merchant settlement and split payouts
Settlement for sub-merchants often involves splitting one payment between several parties. Marketplaces are the clearest case, since one shopper's order can include items from several sellers.
Here's a hypothetical order of $200, with $120 from seller A and $80 from seller B. The marketplace takes a 10% commission and pays processing costs of 2.9% plus $0.30 per order.
| Party | Calculation | Amount |
|---|---|---|
| Seller A | $120 - 10% commission | $108 |
| Seller B | $80 - 10% commission | $72 |
| Marketplace commission | $12 + $8 | $20 |
| Processing cost | $200 x 2.9% + $0.30 | -$6.10 |
| Marketplace net | $20 - $6.10 | $13.90 |
Refunds test it. If the shopper returns seller B's item, the refund of $80 has to come back from seller B's balance, and the commission on it may or may not be refunded depending on your terms.
Sub-merchant management after go-live
Approval starts the relationship. Each sub-merchant needs its own limits and reserves, because one bad sub-merchant's disputes count against the facilitator and then against its sponsor.
Growth needs watching too. Under Visa's rules, a sponsored merchant whose annual Visa sales pass US$1,000,000 needs the acquirer added to its merchant agreement, as the payment facilitator guide explains, so large sub-merchants have to be flagged before they cross that line. When a sub-merchant leaves or is terminated, its reserves and open disputes stay with you until they're settled.
A sub-merchant management platform
Our merchant management system handles sub-merchant onboarding through an API you can build into your own product, with KYB and KYC through the verification provider you choose and risk scoring against your rules. Webhooks report status changes and risk flags as they happen, along with onboarding milestones and settlement updates.
After go-live, the platform monitors each sub-merchant, applies fees per sub-merchant, group or product, and settles behind rolling reserves and holdbacks. Split payments and payouts across several sellers and providers are built in, so a marketplace order pays each seller its share.
Questions
What is sub-merchant onboarding?
The process a payment facilitator or marketplace uses to sign businesses under its own setup with a sponsoring acquirer: collecting their details, running KYB and KYC checks, scoring risk and creating their accounts.
Can sub-merchant onboarding be automated?
Mostly. Data collection, registry and identity checks, screening and scoring can run automatically through an API, while a person reviews the cases the rules flag.
How does sub-merchant settlement work?
The facilitator receives the funds from its acquirer, deducts its fees, reserves and any split for other parties, then pays each sub-merchant its share on a set schedule.
Who is responsible for a sub-merchant's chargebacks?
The sub-merchant first, but the payment facilitator if the sub-merchant can't pay. That's why reserves and monitoring matter for every sub-merchant, not only the large ones.