Embedded payments for SaaS platforms are payments your users take and manage without leaving your product. The nursery owner collects the month's fees from parents, the gym takes memberships by Direct Debit, the plumber gets paid by QR code on the doorstep, and every one of those payments lands in the dashboard they already use to run the business. Your brand is on the checkout. Your platform earns on the volume.
That last sentence is the point. Plenty of platforms have "payments" in the sense that a customer can pay somewhere. Far fewer own the payment relationship, and owning it is what turns payments from a feature into a revenue line.
Embedded payments are payments delivered inside a software platform's own workflow, where the platform's users are the merchants and the platform controls the experience end to end.
Three things have to be true for that to hold:
Behind those three sits a licensed payment institution that holds the regulatory permission, safeguards the funds, carries the risk and runs payouts and disputes. That is the layer you are actually buying, and it is the part nobody sees.
That is the practical meaning of embedded payments for platforms: the merchant, the pricing and the brand are yours, and the licence is someone else's.
Most platforms already have an integration. Here is what embedding changes, point by point.
Who onboards the merchant. With an integration, the provider does, and each merchant holds their own provider account. With embedded payments, you do, inside your UI, with the provider running KYB and KYC behind it.
Whose brand the merchant sees. With an integration, a mix: your UI, their statements, their support. With embedded payments, yours, end to end.
Who sets merchant pricing. With an integration, the provider. With embedded payments, you.
What you earn. With an integration, little or nothing. With embedded payments, a margin on every transaction.
Who holds the regulatory permission. The provider in both cases. Under PayFac-as-a-Service that is the point: the licence stays with them while everything the merchant sees is yours.
Two of those carry most of the weight. Who onboards the merchant decides whether the merchant is yours or the provider's. Who sets pricing decides whether payments make you money. An integration gives you a nicer checkout and leaves both of those with the provider.
The confusion between embedded and integrated is fair, because from the payer's side they look identical. The difference is entirely on the merchant's side, and on your P&L.
Follow one embedded payment. A parent pays a nursery's monthly fee through the nursery's management software.
Step 3 is the one that matters most. The firm that holds the funds carries the obligations that come with them: keeping them separate, reconciling them and returning them if anything goes wrong. If that firm is your provider, that work is theirs. If you ever hold the funds yourself, it is yours.
So "who holds the money" is a commercial question before it is a compliance one.
Embedded B2B payments follow the same model with a different mix of methods.
For an accounting platform or a field service tool the payment is usually an invoice rather than a checkout. The payment link is embedded in the invoice or sent with it, the customer settles in one click by card or open banking, and the payment is matched to the invoice automatically instead of arriving as a bank transfer someone reconciles by hand on Monday.
Recurring B2B collection runs on Direct Debit, which is what most UK platforms use for memberships, subscriptions, rent and fees. Open banking suits one-off settlement: an overdue invoice, a member clearing a failed collection. Cards and wallets cover both.
A platform that embeds the payment link into the invoice closes the invoice-to-cash gap for every one of its merchants at once. That is harder to sell than a checkout, and much stickier once it is in.
Owning payments and holding the licence are two separate decisions. Most vertical platforms want the first and hand the second to a provider that already has it.
A registered PayFac holds its own card network registration and acquiring sponsorship, underwrites every merchant itself and carries the losses. It also needs an FCA permission, a risk team and capital held against chargebacks. For most vertical platforms that overhead costs more than the margin it saves.
PayFac-as-a-Service gives you the merchant onboarding, the branded experience, the pricing control and the revenue share, while a licensed provider holds the permission and does the regulatory work. Platforms go live in 3 to 6 weeks on that model, against 6 to 12 months for an in-house build that then still needs a sponsor.
The cost is real, though. You share margin with the provider, and your sub-merchants sit under its permission, so ask early what happens to them if you ever leave. The seven questions to put to a provider before signing are in the guide to PayFac as a Service in 2026.
The mechanics are the same everywhere. What changes is which method carries the volume and where the operational pain was.
You take a margin on the payment volume your merchants process, and you choose the structure. A flat transaction fee with your margin inside it. Tiered rates by volume. Different rates by merchant segment. Or payments bundled into a higher subscription tier, so the merchant sees no per-transaction fee at all, which is the model that most often lifts the software price too.
Unlike a referral commission, the revenue grows with your customers' businesses rather than with your sales team's quota. It also compounds retention: a merchant whose card tokens, Direct Debit mandates and payment history live in your platform has a real cost to leaving.
Referral is a fair answer at low volume. The economics turn once enough merchants process enough that a margin beats a flat commission.
Unipaas is an embedded payments platform for vertical SaaS in the UK, Europe and the US, delivered on a PayFac-as-a-Service model. Platforms launch a white-label payments offering under their own brand, typically in 3 to 6 weeks, using pre-built onboarding, checkout and dashboard components, while Unipaas runs KYB and KYC, risk, payouts, reconciliation, disputes and merchant support behind it.
Unipaas Financial Services Limited is an FCA Authorised Payment Institution and PCI DSS Level 1 certified, so platforms integrating it stay within SAQ A.
The vertical detail is where the managed model earns its place: Tax-Free Childcare for nurseries, POS terminals and QR codes for field teams and front desks, Direct Debit for memberships and rent. And as more merchant admin gets done by an assistant, Unipaas MCP lets AI agents create payment links, search transactions and manage payouts over Model Context Protocol.
Every payment your merchants take today already runs through your workflow. The only open question is whose name is on it, and who keeps the margin.
Payments accepted and managed inside a software platform, where the platform's users are the merchants, the platform's brand is on the experience, and a licensed provider holds the regulatory permission behind it. The payer never leaves the product, and the platform earns a margin on the volume.
Your customers take payments from their customers inside your software: a nursery from parents, a gym from members, an accountant's client from theirs. You onboard them and set their pricing, and a payment institution behind you safeguards the money and runs risk and payouts.
Integrated payments put a provider's API inside your product, but each merchant still holds their own account with that provider, who sets their pricing and owns the relationship. Embedded payments onboard the merchant inside your product under a provider's permission, so you set the pricing and keep the margin.
Your merchant switches payments on inside your UI, the provider runs KYB and KYC behind the scenes, and your merchant's customers pay on checkout, links or invoices you brand. Funds settle to the licensed provider, which safeguards them, pays your merchant, pays you your margin and handles disputes.
The same model applied to business invoices and recurring collections: payment links embedded in invoices, Direct Debit for subscriptions and fees, open banking for one-off settlement, all reconciled automatically against the invoice inside the platform.
Under PayFac-as-a-Service the licence sits with the provider, which holds the regulatory permission and safeguards the funds. You carry contractual obligations about how you present the service, but you do not need to become a licensed payment institution or a registered PayFac.
Three to six weeks with a managed provider, against six to twelve months to build in-house before network registration. Most of those weeks go on your onboarding journey and reporting screens, not on the payment rails.
By taking a margin on the payment volume their merchants process, structured as flat fees, tiered rates, segment pricing or a bundled subscription tier. The revenue scales with your merchants' businesses rather than with your own sales effort.
.png)
.png)
.png)
.png)
.png)
