Software platforms that want to earn revenue from payments face a structural choice. They can register as a payment facilitator (PayFac), or they can partner with an embedded payments provider. Both models let the platform offer payments inside its product. They differ in who registers with the card networks, who underwrites merchants, who carries risk and who runs payments operations day to day.
Key Takeaways
- A registered payment facilitator owns merchant underwriting, compliance, liability and chargeback risk; an embedded payments provider carries that work while the platform still earns on every transaction.
- With a PayFac model, the merchant agreement is between the merchant and the software platform; with an embedded payments provider, merchant agreements vary by provider, so confirm who holds them.
- Running a PayFac means building a credit and risk team, maintaining certifications with a processor and more complex integrations; an embedded model lets the platform stay focused on building vertical software instead of a payments division.
- Hosted payment pages redirect the customer; hosted fields and embedded components keep checkout inside the platform’s interface while card data stays off its servers.
What does it take to become your own payment facilitator?
Becoming a payment facilitator means registering with card networks through a sponsor bank and taking on underwriting, risk, KYC/AML, PCI DSS Level 1 and chargeback liability for every sub-merchant. A PayFac holds a master merchant account and boards its users as sub-merchants under it, so the platform is responsible for the merchants it brings onto the network. Card network rules set the registration and oversight requirements; Visa and Mastercard publish them in their payment facilitator rules.
The difference between payment facilitators and traditional processors comes down to where responsibility sits. With a traditional processor, each merchant applies for its own merchant account, and the processor or acquirer handles compliance, risk and underwriting. If a platform becomes a PayFac, the platform takes on those duties and liabilities for its sub-merchants. An embedded payments provider takes a third path: it can carry some or all of the registration, underwriting and risk, depending on the provider, and the platform integrates through APIs.
| Registered PayFac | Embedded payments (PaaS) | |
|---|---|---|
| Who registers with card networks | The platform, through a sponsor bank | The provider |
| Who does underwriting | The platform | The provider |
| Who carries chargeback risk | The platform | The provider |
| Merchant agreement signed with | The platform | The provider |
| Time to launch | Longer: registration, sponsor bank and processor certification come first | Shorter: integration with the provider’s APIs |
The operational overhead of a PayFac registration stays roughly fixed whether a platform processes a little or a lot, which is why volume decides the trade-off. Platforms typically evaluate becoming a PayFac once processing volume is large enough to fund a dedicated payments, risk and compliance team. Below that point, providers such as Zift ([Zift branded URL]) help platforms monetize payments and look like payment facilitators without registering as a payment facilitator.
Hosted page, iframe or true embedded: how does white-label checkout differ?
Checkout design is a separate decision from the PayFac question, and it shapes both user experience and PCI scope. Software platforms usually choose between three options.
| Hosted payment page | Iframe | True embedded (hosted fields / elements) | |
|---|---|---|---|
| UX | Redirects the customer to a provider page | No redirect; a provider form loads inside the platform’s page | No redirect; individual card fields sit inside the platform’s own form |
| Brand control | Limited to provider styling options | Partial; the frame follows provider layout | High; the platform controls layout and styling |
| PCI burden | Lowest; card data never touches the platform | Low; card data is entered in the provider’s frame | Low; fields are hosted by the provider, card data stays off the platform’s servers |
A hosted payment page is the simplest to launch, but the redirect takes the customer out of the product. An iframe keeps the customer on the page, though the form can look and behave differently from the rest of the interface.
Hosted fields, sometimes called elements, place each sensitive input in a small provider-hosted field inside the platform’s own form. The platform designs the checkout, and the provider receives the card number and returns a token. A direct API integration that sends raw card data from the platform’s servers gives full control, but it brings those servers into PCI scope. When evaluating a provider, ask whether it supports hosted fields or elements without a redirect, and how tokens are stored for repeat payments.
Zift offers white-label payment solutions that allow platforms to embed checkout flows directly into the application interface. Its JavaScript library turns payment forms into hosted payment fields, and tokenization keeps card and bank account numbers off the platform’s servers. White-label infrastructure also covers merchant-facing settings, such as payout and deposit reporting, under the platform’s brand.
Who holds the merchant agreement, and what does a PayFac have to maintain?
With a PayFac model, the merchant signs the merchant agreement with the platform, and the platform runs onboarding and underwriting. With an embedded payments model, underwriting and merchant agreements vary by provider, so confirm who holds them. Where the provider runs underwriting, it verifies the business and the identity of its owners, then activates the account. The platform still controls the onboarding experience. It can collect the application in its own forms through an onboarding API or use a hosted, branded application form. Moving an existing customer base follows the same flow, so the time to migrate depends on how quickly merchants complete onboarding.
A PayFac must also maintain certifications with its processor and build and support more complex integrations for onboarding, funding, reporting and disputes. Each processor change or rule update becomes the platform’s engineering work.
The trade-offs are real on both sides. A PayFac model gives more control over the merchant relationship. The embedded model reduces operational load and time to launch, and lets the platform keep its engineering and operations focused on its vertical software rather than building and staffing a payments division.
Frequently asked questions
What is the difference between a PayFac and an ISO?
An independent sales organization (ISO) resells a processor’s merchant services: each merchant gets its own merchant account, and the acquirer underwrites it. A PayFac boards merchants as sub-merchants under its own master merchant account and takes on underwriting, compliance and chargeback liability for them.
Can a platform earn from payments without registering as a PayFac?
Yes. Through an embedded payments provider, the platform offers payments inside its software and earns on transactions, while the provider manages compliance, underwriting and risk. The platform does not need its own card network registration or sponsor bank relationship.
Who signs the merchant agreement in an embedded payments model?
It varies by provider, so confirm who holds the merchant agreement. Where the provider holds it, the merchant accepts the provider’s processing terms and conditions, and the provider verifies the business and its owners. The platform still runs the onboarding experience through its own forms or a hosted, branded application.
What are hosted fields?
Hosted fields are individual payment inputs, such as card number and expiration date, served by the payment provider but placed inside the platform’s own checkout form. The customer never leaves the page, the platform controls the user experience, and card data goes directly to the provider, keeping it off the platform’s servers.
How long does it take to launch with each model?
A registered PayFac must first secure a sponsor bank, complete card network registration and certify with a processor, so launch takes longer. With an embedded provider, launch time depends mainly on integrating its APIs and onboarding flow, because registration and underwriting are already in place.
Conclusion
The PayFac versus embedded payments decision is a question of ownership. Registering as a payment facilitator gives a software platform direct control over the merchant relationship, onboarding and underwriting, along with responsibility for compliance, chargeback risk, processor certifications and the integrations behind them. An embedded payments provider takes on all that work, while the platform keeps control of the user experience and earns on transactions.
Platforms that want payment revenue without building a payments division can evaluate Zift’s Payments-as-a-Service for software platforms, which combines white-label checkout, hosted payment fields and API-driven onboarding. Platforms that expect to own every part of the merchant relationship should weigh registration against the team, volume and time that it requires.















