Embedded payments let an ISV or software platform offer payment acceptance inside its own product, under its own brand, instead of referring merchants to a third-party processor. On white-label payment infrastructure such as NORBr, ISVs get the provider connections, onboarding, routing and reporting needed to embed payments without building a payment platform or becoming a PSP.
For software companies, payments have moved from a referral partnership to a product line. This article, updated in October 2026, explains what embedded payments are, why ISVs embed them, how payouts fit in, the three ways to launch, what an ISV needs from its payment infrastructure, and how NORBr supports ISVs and the PayFacs that serve them.
What are embedded payments and how do they differ from embedded finance?
Embedded payments are payment acceptance built into a non-payment product: a booking tool, a practice management system or a marketplace takes payments in its own interface, and the software company, not a separate processor, owns the experience. Embedded finance is the wider category, which also covers lending, insurance, accounts and payouts offered inside non-financial software.
The category keeps growing. According to Juniper Research (September 2026), global embedded finance revenue will rise from 162.6 billion dollars in 2026 to 617 billion dollars by 2031, with the B2B segment growing fastest.
Why do ISVs and software platforms embed payments?
Three reasons: revenue, retention and data. Payments become a revenue line that grows with each merchant's volume, merchants who take payments inside the software are less likely to leave it, and the platform sees transaction data it can turn into reporting, financing or better product decisions.
The payment revenue page shows how an ISV sets its own pricing and keeps the margin, while the infrastructure cost stays predictable. Juniper's report makes the same point from the market side: vertical specialization, rather than horizontal breadth, is what differentiates success in embedded finance, which favors software built for one industry.
Where do embedded payouts fit?
Marketplaces, booking platforms and gig-economy software do not only collect money; they also pay it out to sellers, hosts or workers. Embedded payouts handle those disbursements inside the same product, often on fast or instant rails, so the platform controls both sides of the money flow.
For an ISV, payouts follow the same logic as acceptance: one connected network of providers, routing per corridor or method, and reconciliation that ties every payout to the payments behind it. The instant payments article covers the rails that make faster payouts possible in Europe.
Build, partner or white-label: how does an ISV launch embedded payments?
An ISV has three paths. Referring merchants to a processor is quick but gives away the experience, the data and most of the economics. Building in-house keeps full control but means a long cycle of integration, licensing and compliance work. Launching on white-label payment infrastructure keeps the brand, the experience and the margin while the infrastructure runs underneath.
The last path also avoids the heaviest burden: on NORBr, the ISV sets what its merchants pay without carrying the PSP status and its obligations, as described in payments without the PSP burden. The build vs buy comparison and the time-to-market page detail the trade-offs.
What does an ISV need from its payment infrastructure?
An ISV needs the layers a payment business runs on, delivered so it can configure rather than build them. The list is the same whether the platform serves ten merchants or ten thousand:
- Merchant onboarding with KYB forms and partner reviews, through the onboarding workflow.
- A connected provider network, with acquirers and local methods activated per merchant from the global payment network.
- Routing, fallback and network tokenization to keep authorization rates up across providers.
- A checkout embedded in the ISV's interface, online and in store with Matcher™.
- Reconciliation and reporting that give each merchant one statement and each finance team usable exports.
- Security and compliance handled at platform level, including PCI DSS validation, covered in the Visa registry article.
How does NORBr support ISVs and PayFacs with embedded payments?
NORBr is the white-label payment infrastructure behind the payment offer of ISVs, PayFacs, PSPs and ISOs. The ISV's merchants log into a console under the ISV's brand, the ISV configures providers, pricing and rules, and NORBr runs the platform, the provider integrations and the compliance underneath.
New providers requested by an ISV are integrated on demand with Mapper™, and the Payment Platform Builder sets up the structure, from program managers to merchant accounts. The article on ISV and ISO success covers the operating side of that model.
_%2520a%2520game%2520changer%2520for%2520digital%2520transactions_-Cover.webp){kind=spacer}
