It's a board meeting, and someone has a slide up. Your merchants process €400 million a year through your platform, and every euro of it earns a fee for a payment provider that isn't you. The room goes quiet, then someone says 'PayFac'. Six months later, the same company is hiring a risk team, arguing with its sponsoring bank about reserves, and absorbing €80,000 in chargebacks from a sub-merchant it onboarded in four minutes.The opportunity on that slide was real, but the model choice was the mistake.A platform can handle payments in three ways: use a merchant of record (MoR), become a payment facilitator (PayFac), or run a white label payment solution. On a slide, all three read as 'we handle payments'. In practice, they put different names on the transaction and different bills on your desk.The quickest way to tell them apart is to ask whose name is on the transaction, and who pays when it goes wrong. Tax, chargebacks, margin, speed, and control all follow from the answers. Below I go through what each model involves, where they differ, and how I'd pick the one that fits your platform now without locking you out of the next one.What is a merchant of record?A merchant of record is the legal seller of the product. Its name appears on the customer's card statement. It collects and remits sales tax or VAT, handles refunds, fights chargebacks, and answers to the card schemes.When you use a third-party merchant of record, it formally buys your product and resells it to your customer. You get the revenue, minus a fee. It takes the liability, the tax registrations, and the paperwork in every country you sell into. In effect, you're paying someone else to be the party that customers, tax authorities, and card schemes call.Tax is usually what makes that worth it. Under EU VAT rules, digital services sold to consumers are taxed in the customer's country, not the seller's. A subscription sold to someone in Lisbon carries Portuguese VAT; one sold in Warsaw carries Polish VAT. Add every non-EU country with its own regime, and a software company selling subscriptions in 60 countries suddenly needs a tax department it never planned for.The cost comes every month, as a share of revenue. The fee grows with your sales, and because the MoR's name is on the statement, its rules shape your checkout, your refund policy, and part of your customer relationship.It's also a model for selling your own product. If your users sell their products through you, a merchant of record doesn't answer your question.What a payment facilitator signs up forA payment facilitator lets other businesses accept payments under its own master account with a sponsoring acquirer.Under the Visa Rules, a PayFac contracts with an acquirer, deposits transactions, and receives settlement on behalf of its sponsored merchants. In practice, you take over the acquirer's job for your own user base: underwriting, KYC, transaction monitoring, funds flow, and payouts.The appeal is easy to see:Onboarding goes from weeks to minutes, because you approve the merchant instead of sending them to a bank.You earn the spread between what you charge and what you pay.Payments move from the cost column to the revenue column, which is why that slide gets made in the first place.What the slide tends to leave out is that liability moves with the money. When a sub-merchant disappears with unpaid chargebacks, the acquirer doesn't chase the sub-merchant. It chases you. You need people reading risk alerts every day, a compliance stack to match, and most likely a reserve you'd rather be spending on product.The model also has a built-in ceiling. Under Visa's rules, once a sponsored merchant passes $1 million in annual Visa volume, it has to sign directly with the acquirer. The PayFac model was built for the long tail, and your biggest customers will eventually outgrow it and take that margin with them.White label: someone else's infrastructure, your brandWhite label is the commercial shortcut. You take a provider's payment infrastructure, put your brand on it, and offer it to your users as your own product.The provider keeps the licenses, the contracts with acquiring banks, and most of the risk. You keep the interface, the relationship with your merchants, and a revenue share.Often, a PayFac sits behind it, which the industry sells as PayFac-as-a-service. It's how most platforms start offering embedded payments, because it gets you live in weeks rather than the months a full PayFac registration takes.The trade-offs are predictable. Margins are thinner because the provider carries the risk and charges for it. Its onboarding rules, risk appetite, and list of supported markets become yours. And when it declines one of your merchants, you're the one explaining why, with your logo on the screen. None of that is a reason to avoid white label, but it is a reason to know exactly what you're renting.Merchant of record vs payment facilitator: not competing modelsMerchant of record and payment facilitator usually get compared side by side, as if they were two versions of the same thing. They're closer to opposites.A merchant of record is the seller; a PayFac enables other sellers. One takes liability off your hands in exchange for a fee. The other puts liability on you in exchange for revenue and control. White label sits in between: some of the revenue, some of the control, and most of the risk still with someone else.How I'd chooseFive questions, in this order:Who's selling: you or your users? If you sell your own software, content, or digital goods, a merchant of record is the natural starting point, and the PayFac debate mostly doesn't apply. If your users sell through you, you're choosing between PayFac and white label.Who would handle tax in 30 countries? If the honest answer is a nervous look at your finance lead, the MoR fee is cheaper than the alternative.Are payments a revenue line or a feature? For vertical SaaS with thousands of small merchants, payments margin can rival subscription revenue, and that's the case for PayFac. If payments simply complete the product, a white-label payment gateway gives you most of the benefit for a fraction of the risk.Who would run the risk operation? Our research found that nearly 60% of companies still manage payments as general admin or a secondary responsibility. Under a white-label partner, that works fine. As a PayFac, it becomes a number somebody has to explain to the acquirer.How fast do you need to be live? White label can launch this quarter. Becoming a PayFac means sponsorship, scheme registration, compliance, and the build itself, which adds up to many months and real capital.The pattern I see most often from platforms that get this right: start with white label, prove that merchants adopt payments, then move to PayFac once the volume justifies carrying the liability. The ones that get it wrong skip straight to PayFac because the spreadsheet looked brilliant in year one.Switching, the part nobody plans forWhichever model you pick, it won't be your last. A merchant of record that was ideal at $5 million in revenue starts to look expensive at $50 million. The white-label partner that got you to launch can end up blocking your next region. A PayFac built for small merchants starts losing its largest ones to direct contracts.The platforms that move between models without pain share one thing: they kept their payment layer portable from day one. Their flows aren't hard-coded to a single provider; they own their transaction data, and they can add or swap acquirers without rebuilding checkout.That portability is what a payment orchestration layer provides. The commercial model can change while the technical foundation stays the same.Pick the model that fits the company you are today. Just make sure that changing it later means renegotiating a contract, not starting a replatforming project. No#PaymentSolutionsOleg Ishchenko Sales ManagerCorefy03 Nov, 2026