EMBEDDED PAYMENTS

Embedded payments, and who answers for your sellers.

Embedded payments put money movement inside your product without turning you into a payments company. What changes is who signs your sellers, who carries their losses and how much compliance work lands on your team.

Updated · 9 min read

In short

  • Embedded payments means building payment acceptance and payouts directly into your software, so your users get paid without leaving your product.
  • Platforms usually choose between referring users to a processor, registering as a payment facilitator (payfac) or using a managed provider that runs the payfac infrastructure behind an API.
  • Under card network rules the acquiring bank is responsible for its payment facilitators and their sub-merchants, so onboarding, underwriting and monitoring sub-merchants is the core of the work.
  • Platforms that serve complex or regulated industries need KYB, watchlist screening, transaction monitoring and screened payouts on top of payment acceptance.
  • FrameOS gives platforms one API for payments, payouts, identity and compliance, including co-branded sub-merchant onboarding and ongoing monitoring.

What embedded payments look like

Embedded payments are payment capabilities built into a software product, so customers pay and get paid inside the product they already use.

A booking platform that lets clinics charge patients, a marketplace that pays out sellers and a SaaS tool that bills on behalf of its users are all running embedded payments. The user never opens a separate processor account or logs in to a second dashboard. The software company owns the experience and, in most models, earns a share of the revenue.

Stripe's own explainer makes the commercial case: payments add a revenue layer on top of software pricing, raise switching costs once businesses build workflows around them and produce transaction data that informs new products1. It is just as clear about what comes with it: platforms still have to plan for KYC and KYB, PCI DSS, sanctions screening and anti-money laundering controls, and for how funds flow through fees, payouts and refunds1.

For platforms whose users are in complex industries, such as telehealth, gaming, creator monetization or travel, that compliance layer is most of the work. It decides whether your sponsor bank approves the program and whether your sellers stay live once they start processing.

Three ways to offer embedded payments

There are three common ways to offer embedded payments, and the real difference between them is who signs the merchant and therefore who answers for its losses.

Referral or integration

You integrate with a processor and refer your users to it. Each user signs its own merchant agreement. It is the least work, and you get the least control and usually a modest referral share.

Become a payment facilitator

You register as a payfac with a sponsor bank, sign sub-merchants yourself and receive and distribute their funds. You keep the most margin and control, and you take on the compliance team and the liability that come with them.

Managed payfac (PFaaS)

A provider runs the payfac infrastructure, underwriting and risk program behind an API while you own the product experience. This is what people usually mean by payfac-as-a-service.

Visa defines a payment facilitator as a third-party agent that can sign a merchant acceptance agreement with a seller on behalf of an acquirer, receive settlement funds for that seller, or both. The seller is a sponsored merchant2. That definition matters because of what follows from it: Visa states that acquirers are responsible for the acts of both payment facilitators and their sponsored merchants, and must perform due diligence on the payfac and monitor its compliance with Visa rules3.

In practice, every embedded payments program is a chain of accountability: sponsor bank, then payfac or managed provider, then platform, then sub-merchant. Whoever sits in the payfac seat must prove to the bank that every sub-merchant is real, permitted and monitored. For a deeper comparison of the roles, read payfac vs ISO and our page on payment facilitation as a service.

What a platform takes on per seller

When you embed payments you also embed the obligations attached to them, and the model you choose decides how many of those sit with your team.

  • Sub-merchant onboarding: collect business and owner details, verify identity (KYB and KYC), screen against sanctions and watchlists and check bank accounts before anyone is paid.
  • Underwriting each seller: which ones are permitted, which need licenses or certifications and which need limits or reserves.
  • Watching transactions for fraud, unusual volume and prohibited activity after launch, and re-screening sub-merchants over time.
  • Routing chargebacks to the right sub-merchant, responding within network deadlines and keeping fraud and dispute ratios under Visa and Mastercard thresholds.
  • Moving funds to sub-merchants on schedule, with screening on every outbound payment.
  • Keeping card data out of your systems with tokenization and hosted fields, and maintaining PCI DSS compliance.
  • An audit trail your sponsor bank, the card networks or a regulator can review.

Ratios are where one seller's problem becomes the platform's. Visa's VAMP flags a US merchant as excessive at a 1.5% combined fraud and dispute ratio, and measures acquirer portfolios at 0.5% and 0.7%4, and one poorly screened sub-merchant can move the whole portfolio. If you also pull funds by ACH, Nacha rules set an unauthorized return threshold of 0.5%5.

Embedded payments models compared

Which model fits mostly comes down to two things: how much volume you process and what your users sell.

Referral vs registered payfac vs FrameOS
Referral to a processorRegister as a payfacFrameOS
Who signs the sub-merchantThe processorYour company, on behalf of the sponsor bank2Contact Frame
Branded onboarding in your productPartlyYesYes
Sub-merchant KYB, KYC and watchlist screeningProcessorYou build or buy itAvailable on the platform
Sub-merchant monitoringProcessorYou build or buy itIncluded: Sonar, plus monitoring after approval
Liability to the sponsor bankProcessorYou, as the payfac3Contact Frame
Payouts to sub-merchantsProcessor's railsYou integrate payout rails300+ payout rails, screened
Support for complex industriesDepends on processor policyDepends on your sponsor bankReviewed case by case
Time and cost to launchLowHigh: bank sponsorship, risk team, PCIOne integration; sandbox on day one

This is a simplified comparison; a registered payfac's actual obligations come from its sponsor bank agreement and the card network rules.

Most platforms start with referral or a managed model and only consider registering as a payfac at significant volume. If you are comparing managed providers, our guide to the best embedded payments providers goes provider by provider.

What embedded payments earn and cost

Embedded payments revenue is the spread between what your users pay and what your provider charges you, and platform-level fees come out of that spread before you see any of it.

Provider pricing varies by model, and Stripe Connect is a useful published reference point. It charges platforms nothing extra when Stripe bills connected accounts directly. When the platform sets its own pricing, Stripe Connect charges $2 per monthly active account and 0.25% + 25¢ per payout, plus 1% for Instant Payouts6. Those platform fees sit on top of payment processing costs. Because the account fee is charged per active seller rather than per dollar processed, a long tail of small sellers costs more, relative to their volume, than a handful of large ones.

Processing margin

What your users pay per transaction minus what your provider charges you. It is the number most revenue models start from.

Platform fees

Per-account, per-payout and onboarding fees charged by your provider, which scale with seller count as well as volume.

Payout fees

Users will pay for instant and same-day payouts, and each one is also a cost you carry.

Loss exposure

Disputes, fraud and negative balances from sub-merchants. Strong onboarding is the cheapest way to reduce it.

FrameOS pricing is published on the pricing page: card payments from 2.0% + $0.39 per successful transaction, ACH at 0.8%, instant payouts at 1.5%, $25 per dispute and $0.05 per 3D Secure attempt, with Sonar fraud monitoring included at no additional cost7. There are no setup fees or monthly minimums. For platform pricing beyond those published rates, talk to Frame.

Launching embedded payments

Most of a good launch is decided before anyone writes code, and the funds flow comes first because every later decision depends on it.

  1. Map your funds flow

    Who pays whom, when your fee is taken, how refunds and chargebacks are recovered and how sub-merchants are paid out.

  2. Define your sub-merchant policy

    Which business types you will accept, which licenses they need and what limits apply to new accounts.

  3. Choose onboarding depth

    Hosted, co-branded onboarding gets you live fastest, while a fully API-driven flow gives you more control over the experience.

  4. Integrate and test edge cases

    Test declines, disputes, failed payouts and negative balances in a sandbox before real money moves.

  5. Launch in cohorts

    Start with a group of known users, watch dispute and return ratios, then open more widely.

The technical side, including onboarding endpoints, webhooks and payouts, is covered on our embedded payments API page.

How FrameOS covers those obligations

Each obligation on that list usually means another vendor, and most embedded payments stacks end up as five stitched together. FrameOS runs them on one platform and one API for payments, payouts, identity and compliance.

Onboarding and identity

A co-branded, mobile-optimized embedded onboarding flow with KYB, KYC, document verification, liveness and bank account verification, all kept in a full exportable audit trail.

Monitoring after launch

Monitoring and reporting continue after approval, Sonar scores card and bank payments for fraud in real time, and Creator Shield continuously screens individual creators and sellers against adverse media and Frame's risk indexes8.

Card data out of your systems

Hosted checkout and Frame.js iframes keep card details off your servers, with 3D Secure available. Cards, Apple Pay, Google Pay, Cash App Pay, ACH, RTP and wallets settle to one balance, and PCI compliance is included.

Paying sub-merchants

300+ payout rails, with identity and location verified and compliance screening on every outbound payout.

Billing for platforms

Usage metering, hybrid plans, prepay wallets, invoicing and proration.

Checking each seller

KYC, KYB and identity checks run in the background as you onboard sub-merchants, before any of them transact.

If you build vertical software for one industry, see how embedded payments work for vertical SaaS.

FAQ

What are embedded payments?
Embedded payments are payment features built directly into a software product or platform. Users never get sent to a separate processor: the platform lets them accept payments, get paid out and manage transactions inside its own interface. The platform usually earns revenue on each transaction, while a payments provider or sponsor bank handles card network access, settlement and much of the compliance.
What is the difference between embedded payments and a payment facilitator?
Embedded payments describes the product experience: payments inside your software. A payment facilitator is one way to deliver it. Under Visa's definition, a payfac signs merchant agreements with sellers on behalf of an acquirer and can receive their settlement funds2. You can offer embedded payments by becoming a payfac, by referring users to a processor, or through a managed provider that runs the payfac program.
Do I need to become a payfac to offer embedded payments?
You don't have to become one. Registering as a payment facilitator gives you the most control, but it requires a sponsor bank, an underwriting and risk team, PCI compliance and liability for your sub-merchants. Many platforms use a managed model instead, where a provider carries the payfac infrastructure and compliance while the platform owns the experience. Frame supports platforms through one integration, with sub-merchant onboarding, payments, payouts and compliance on the same API.
How do platforms make money from embedded payments?
Mainly from the margin between what their users pay per transaction and what the platform's provider charges, plus fees for premium features such as instant payouts. Revenue depends on volume, pricing model and loss rates. Platform-level fees, such as per-account and per-payout charges, and losses from sub-merchant disputes or fraud reduce the margin, so onboarding quality affects profit directly.
Who is liable for sub-merchant chargebacks and fraud?
Liability runs up the chain, and Visa states that acquirers are responsible for the acts of both payment facilitators and their sponsored merchants3. The acquirer typically passes that responsibility to the payfac contractually, and the payfac recovers losses from the sub-merchant where it can. The exact split in any program is set by its agreements, so read them closely.
Can platforms in regulated industries offer embedded payments?
Yes, but the bar is higher. The platform's program is reviewed against its users' industry, so a platform serving telehealth providers or game operators needs the licensing evidence, onboarding checks and monitoring those industries require. Frame reviews categories such as telehealth and travel case by case, and its Merchant Processing Agreement makes card acceptance depend on sponsor bank participation9.

Sources

  1. What are embedded payments? (Stripe), accessed November 2, 2026.
  2. Visa acceptance entities (Visa), accessed November 2, 2026.
  3. The Visa Payment Facilitator Model (Visa), accessed November 2, 2026.
  4. Visa Acquirer Monitoring Program (VAMP) fact sheet, 2025, accessed November 2, 2026.
  5. Risk and Quality Rules fact sheet (Nacha), accessed November 2, 2026.
  6. Stripe Connect pricing (Stripe), accessed November 2, 2026.
  7. Frame: Pricing, accessed November 18, 2026.
  8. Frame: Creator Shield (Frame developer docs), accessed November 18, 2026.
  9. Frame: Merchant Processing Agreement, accessed November 18, 2026.

Third-party details reflect each source as of the date accessed and can change. This page is general information, not legal or financial advice. Not every business is automatically approved: underwriting still matters, and a processor and its sponsor bank both decide whether to take on a business.

About the author

Youssef Guirguis, Head of Brand and Marketing

Youssef Guirguis leads brand and marketing at Frame, where he shapes how the company communicates about payments, compliance, and risk to the merchants navigating these issues.

Payments in your product, compliance in ours.

Start in the sandbox and launch embedded payments with onboarding, monitoring and payouts on one API.