One Payments Pte. Ltd. logotype
© 2026 One Payments Pte. Ltd.

What Is a Payment Facilitator (PayFac)? A Plain-English Guide

A payment facilitator, or payfac, is a software platform, marketplace or app that lets its own users accept payments — as sub-merchants — under one master merchant account, instead of each user needing a separate merchant account of their own. The company running the platform becomes the facilitator: it onboards its users, embeds the checkout experience into its own product, and handles payment acceptance for them behind the scenes.

Payfac is often used interchangeably with payment aggregator, but the two describe slightly different things. An aggregator is the underlying model — one master account shared by many sub-merchants — and it is usually run by a payments company that onboards individual businesses directly. A payment facilitator is what you call it when a software platform adopts that same model to serve its own users, embedding payment acceptance as part of a marketplace, SaaS product or booking app. Every payfac works like an aggregator; not every aggregator is a payfac.

This guide breaks down how the payfac model works, how it compares with a payment service provider and a merchant acquirer, and where a platform like one.ooo fits if you want to give your own users payment acceptance without building the whole thing yourself.

A payment facilitator onboarding sub-merchants into its platform under one master account.

How the payfac model works

In the payfac model, the platform — say, a marketplace connecting freelancers with clients, or a booking app connecting hosts with guests — sits between its users and the underlying payment infrastructure. Instead of every seller or host applying for a merchant account of their own, the platform holds one master account and onboards each user as a sub-merchant underneath it.

The platform takes on the onboarding itself: collecting basic business details from each sub-merchant, running lightweight checks, and activating payment acceptance, often within minutes. Funds from a sub-merchant's sale flow into the master account first, and the platform is then responsible for splitting and paying out each sub-merchant's share, typically on an automated payout schedule.

This is a meaningful step up from a simple aggregator relationship: the platform is not just a payments customer, it takes on real operational responsibility for its own users — onboarding, monitoring for fraud, and keeping funds properly separated. In return, the platform can offer a smooth, in-product payment experience and often keep a small margin on the payment flow as part of its own monetisation.

Payment facilitator vs payment aggregator vs PSP vs merchant acquirer

With four similar-sounding terms floating around, it helps to place each one precisely.

A merchant acquirer is the bank or licensed institution that holds the relationship with card networks and ultimately settles funds. It sits underneath everything else in this list.

A payment aggregator is the model where one master merchant account, held with an acquirer, is shared across many sub-merchants — usually run by a payments company that lets individual businesses sign up directly and start accepting payments in minutes.

A payment service provider (PSP) is the broader umbrella term for a company that gives businesses the tools to accept and manage payments across channels — a PSP might run an aggregator model, hold individual merchant accounts for its customers, or both.

A payment facilitator (payfac) is what a software platform becomes when it adopts the aggregator model for its own users rather than for itself. Instead of a payments company onboarding individual businesses, a marketplace, SaaS product or app onboards its own sellers, hosts or clients as sub-merchants — usually by building on a PSP's API rather than arranging acquiring relationships from scratch.

Put simply: the acquirer settles the money, the PSP or aggregator gives a business a way to accept it, and the payfac is a platform extending that same ability to its own users.

Who becomes a payment facilitator, and why

Becoming a payfac makes sense for platforms that connect many independent sellers, providers or hosts with customers — marketplaces, booking platforms, field-service software, and SaaS tools used by freelancers or small businesses. If your product already has "one-to-many" users who each need to get paid, embedding payment facilitation keeps them inside your product instead of sending them off to sign up with a separate provider.

The benefits are real: a smoother, branded checkout experience, one integrated view of transactions across every user, and the option to add a margin on payment volume as a new revenue line. It also removes friction at the exact moment a new seller or host joins your platform — the faster they can start getting paid, the sooner they start transacting.

The trade-off is responsibility. A payfac takes on ongoing obligations around onboarding checks, transaction monitoring and payout accuracy for every sub-merchant on its platform. That's why most platforms build on top of an existing PSP's infrastructure and API rather than becoming a payfac from a blank slate.

Where one.ooo fits

one.ooo is built as an all-in-one, cost-effective payments platform: omni-channel acceptance across online checkout, payment links and in-person POS, plus multi-currency accounts across 13 currencies, all through a single dashboard. Most Singapore businesses use one.ooo the direct way — sign up, connect a bank account, and start accepting Visa, Mastercard, Amex, JCB, UnionPay, Apple Pay, Google Pay and PayNow — without needing to think about payfac or aggregator terminology at all.

If you're building a platform of your own — a marketplace, a booking product, a vertical SaaS tool — one.ooo's REST API and embedded finance capabilities let you extend payment acceptance to your own users directly inside your product, with batch payouts to split funds between sellers, hosts or clients. That's the practical route most platforms take toward the payfac model: build on an existing PSP's onboarding and API rather than negotiating acquiring relationships from the ground up.

Either way, the goal is the same: simplify payments so you spend less time managing infrastructure and more time on your product.

Important Information

Regulated payment services are provided by Airwallex (Singapore) Pte. Ltd., a MAS-licensed Major Payment Institution under the Payment Services Act 2019. ONE Payments acts as a technology provider and merchant service facilitator.

ONE Payments Pte. Ltd. (UEN 202324291R) is registered in Singapore and operates as a technology and merchant services platform. The platform, dashboard, API and embedded finance capabilities described on this page are provided by ONE Payments; payment processing, fund holding and settlement of regulated payment activities are carried out by the licensed regulated partner named above. Information on this page is provided for general guidance only and does not constitute financial, legal or regulatory advice. Please confirm the latest pricing and available services when onboarding. Contact the ONE Payments team for details.

Frequently Asked Questions

What is a payment facilitator in simple terms?
A payment facilitator, or payfac, is a software platform or marketplace that lets its own users accept payments as sub-merchants under one master account, instead of each user applying for a merchant account individually. The platform onboards its users, embeds checkout into its product, and handles payment acceptance for them, usually by building on top of an existing PSP's API and infrastructure.
What's the difference between a payment facilitator and a payment aggregator?
They describe the same underlying model — one master merchant account with many sub-merchants — from two different angles. A payment aggregator is usually a payments company that onboards individual businesses directly. A payment facilitator is a software platform, marketplace or app that adopts the same model to serve its own users. Every payfac works like an aggregator; not every aggregator is a payfac. See our guide to what a payment aggregator is for more detail.
What's the difference between a payfac and a PSP?
A payment service provider (PSP) is the broad term for a company that gives businesses tools to accept and manage payments — it might use an aggregator model, issue individual merchant accounts, or both. A payfac is more specific: it's a platform that takes on the facilitator role for its own sub-merchants, typically by building on a PSP's API. Read more in our guide to what a payment service provider is.
How is a payment facilitator different from a merchant acquirer?
A merchant acquirer is the bank or licensed institution that holds the underlying relationship with card networks and settles funds. A payment facilitator sits several layers above that — it's a platform that onboards its own users as sub-merchants and relies on a PSP, which in turn relies on an acquirer, to move the money. See our guide to what a merchant acquirer is for the full picture.
Do I need to become a payment facilitator to sell payments to my own users?
Not necessarily. If your product connects sellers, hosts or clients with their own customers, embedding payment acceptance can make sense — but you don't have to build the whole payfac model from scratch. Platforms typically extend payment acceptance to their users by building on an existing PSP's API rather than negotiating their own acquiring relationships.
Is one.ooo a payment facilitator?
one.ooo is an all-in-one payments platform most businesses use directly to accept payments online and in person. For platforms and marketplaces that want to extend payment acceptance to their own users, one.ooo's REST API and embedded finance capabilities support building that kind of setup on top of the platform.

Ready to give your users a smoother way to get paid?

Talk to sales