Platforms that move money for their customers eventually ask the same question: should we keep referring merchants to a processor, onboard them ourselves, or own the rails outright? Each step up gives you more revenue and control, and more liability with it.
ISO: you sell, the acquirer underwrites
An Independent Sales Organisation (ISO) is registered with the card networks through a sponsoring acquirer and brings merchants to it. Each merchant signs directly with the acquirer and gets its own merchant ID. The ISO earns residuals, a share of the processing margin, while the acquirer handles underwriting and settlement and carries most of the risk.
Best for: sales-led businesses and software platforms that want payments revenue without running risk and compliance teams.
PayFac: you onboard sub-merchants under your own ID
A payment facilitator (PayFac) holds a master merchant account with a sponsor bank and onboards its customers as sub-merchants. Onboarding takes minutes instead of days, and the PayFac sets its own pricing and keeps more of the margin.
The cost is responsibility. A PayFac runs KYC and KYB on every sub-merchant, monitors transactions, funds sub-merchants, and is liable for their chargebacks and fraud. It also needs registration with the card networks, PCI DSS Level 1 compliance and enough capital to absorb losses.
Best for: vertical software and marketplaces with many small merchants, where fast onboarding is part of the product.
Your own rails: processor-level control
At the top of the ladder, a business builds or licenses its own processing stack: direct acquiring relationships, its own gateway, local payment methods, payout rails and, where needed, its own licences. You control routing, pricing, data and settlement timing, and you can serve corridors and industries that off-the-shelf providers turn away.
This is a multi-year infrastructure project. It needs banking partners, compliance and risk operations, and engineering that does not go down. See how we structure independent rails for companies that want this level of ownership.
How to choose
- Under a few million a year in volume: an ISO or referral model is usually enough.
- Many small merchants and onboarding is your bottleneck: consider a PayFac, or a "PayFac-as-a-service" provider that takes on part of the compliance work.
- High volume, cross-border or hard-to-place industries: owning the rails starts to pay for itself through margin, approval rates and resilience.
Whichever model you start with, design your contracts and data so you can move up without re-onboarding every merchant. The gateway and processor layers are where that migration is easiest to plan.
Working through this for your business? Send us an enquiry or email support@smuvpay.com and we will map it to your volumes, markets and risk profile.