Embedded payments vs embedded finance: what they are and how to choose a solution
Embedded payments are payment features built into software that is not itself a bank or payments app: a checkout in a booking tool, seller payouts in a marketplace, supplier payments inside an ERP. They are one part of embedded finance, which also covers accounts, cards, lending and insurance. This guide explains how embedded payment solutions work, who is regulated, and how to choose one.
The short answer
- Embedded payments put payment features inside software that is not a bank: a checkout in a booking tool, seller payouts in a marketplace, supplier payments in an ERP.
- Embedded finance is the wider family: payments plus accounts, cards, lending, insurance and investing, all offered inside non-financial software.
- An embedded payment solution is the provider, API and regulated infrastructure behind those features. The platform owns the experience; the provider moves and usually holds the money.
- The key questions are which money flows you need, who holds the funds, who is regulated for what, and what your users will pay.
What are embedded payments?
Embedded payments are payment features built into software whose main job is something else. The user stays inside the product while the money moves:
- A property management app collects rent from tenants and pays out to landlords.
- A marketplace charges buyers and pays sellers after delivery.
- An accounting or ERP system pays approved supplier invoices without a separate bank login.
- A platform for freelancers pays contractors in their own currency.
- A booking tool takes a deposit at the moment of booking.
In each case a payments provider runs the regulated part: holding funds, sending payments over the rails and screening transactions. The platform designs the experience and decides when money should move.
Embedded payments vs embedded finance
Embedded payments are a subset of embedded finance. Our guide to what embedded finance is covers the whole field; the table shows where payments sit within it.
| Embedded payments | Embedded finance (wider) | |
|---|---|---|
| What it covers | Accepting payments, paying out, converting currency, collecting by bank transfer | Payments plus accounts, cards, lending, insurance and investing |
| Typical examples | Checkout in a booking app, seller payouts, supplier payments in an ERP | Business accounts inside an accounting tool, cards for a platform’s users, invoice finance at checkout |
| What the platform gets | A smoother way to pay and get paid, and often a share of payment revenue | A wider set of financial products under its own experience |
| Regulatory weight | Payment services rules; card scheme rules for card acceptance | Adds banking, e-money, credit or insurance rules, depending on the product |
The distinction matters when you plan. An embedded payments project can start small, for example with payouts only. Adding accounts or cards brings more regulation, more onboarding work for your users and more questions about who holds their money.
Types of embedded payment solution
| Type | What it does | Watch for |
|---|---|---|
| Embedded checkout (acceptance) | Lets customers pay by card or wallet inside your website or app | Card scheme rules, card data security and chargebacks |
| Embedded payouts | Pays sellers, suppliers or contractors from the platform, domestically or abroad | Recipient details, the rails used, returns and cut-off times |
| Embedded accounts and virtual accounts | Gives the platform, or its users, account details to receive money and identify who paid | Whose name is on the account and who holds the funds |
| Embedded FX | Converts currency inside the product before a payment or payout | The margin over the mid-market rate and how long a quote lasts |
| Embedded collections | Collects by bank transfer or direct debit against invoices | Matching each payment to the right invoice |
Searches for embedded online payment solutions usually mean the first type, embedded checkouts. For business-to-business platforms the payouts, accounts and FX types often matter more, because most of the money moves between businesses by bank transfer. Our guide to B2B payments covers those methods.
How embedded payments work
Most embedded payment set-ups have three parties:
- The platform owns the product and the user relationship. It decides when a payment should happen and shows the result to its users.
- The payments provider supplies the API, the dashboard and the operations. It screens payments, moves money over the rails and reports status back to the platform, usually by webhook.
- The regulated institution holds the money and is responsible for the regulated activity. Sometimes this is the payments provider itself; sometimes the provider works through partner banks or e-money institutions.
A typical payout flow: the platform approves a seller’s balance, calls the provider’s API with an idempotency key, the provider screens and sends the payout, and a webhook tells the platform when the seller has been paid. Our payment API integration guide covers the technical side: sandbox testing, idempotency keys, webhook verification and reconciliation.
Who holds the money is the most important design decision. If the provider or its regulated partner holds it, the platform usually stays out of the regulated activity. If the platform receives funds into its own account and passes them on, it may itself be providing a payment service.
Who is regulated, and for what
The rules depend on the country and on what the platform actually does. Three examples:
- European Union. Payment services are regulated under the Payment Services Directive (Directive (EU) 2015/2366). Its exclusions include payments made through a commercial agent acting for only the payer or only the payee, so a marketplace that acts for both sides cannot simply rely on it.
- United Kingdom. The Payment Services Regulations 2017 set out the payment services that need authorisation or registration, and the activities that are excluded, in Schedule 1.
- Canada. Payment service providers that perform retail payment activities register with the Bank of Canada under the Retail Payment Activities Act; the Bank publishes a PSP registry.
Card acceptance adds the card schemes’ own rules, and providers often onboard a platform’s users as sub-merchants under the provider’s arrangement with an acquirer. In every model, the provider will run know-your-business checks, and often checks on the platform’s own users too. This is general information, not legal advice: take advice on your specific money flow before you launch.
How to choose an embedded payment solution
Put these questions to each embedded payments platform on your shortlist:
- Money flows. Does it support the flows you need, such as checkout, payouts, accounts, FX and collections, in your currencies and corridors?
- Who holds funds. Where is the money held, by which regulated entity, and is it kept apart from the provider’s own money?
- Your users. Who onboards your users, who runs their checks, and what will they see? Can your users be served in the countries where they are?
- Regulation. Which entity holds which authorisation or registration, and where can you check it on a public register?
- The API. Is there documentation, a sandbox, idempotency keys, signed webhooks and clear error codes? See the integration checklist in our payment API guide.
- Pricing and revenue. What does each payment cost, what can you charge on top, and how is any revenue share paid?
- Operations. Who handles returns, held payments, disputes and support, and how fast?
- Exit. If you change provider later, can you move your users and their data?
Build or buy?
Building payments in-house means becoming, or partnering closely with, a regulated institution, and running screening, reconciliation and support yourself. Most platforms buy an embedded payments platform and spend their effort on the experience instead. Building can make sense at very high volumes or for unusual money flows, but it is a regulated business in its own right.
Where KwiikPay fits
KwiikPay is not an embedded checkout: it does not offer card acceptance. What it offers a platform is the account, FX and payout side, by API:
- Accounts. Named GBP, EUR and USD accounts (virtual IBANs) in your company’s name, held apart from KwiikPay’s own money.
- FX. Conversion between 40+ currencies, with the margin shown before you confirm.
- Payouts. Payments to suppliers, sellers and contractors across 30+ corridors to 80+ countries, through regulated banking partners. Eligible customers can also use stablecoin settlement: USDC and EURC on Ethereum, and USDT on Ethereum, BSC and Tron.
- The API. REST with JSON, idempotency keys on every request that creates or changes something, webhooks signed with HMAC-SHA256, and a free sandbox. API access depends on your plan; see the pricing page, the developer page and API payouts.
If you want your own customers to hold balances or accounts through your product, talk to us before you design for it. That is a different arrangement from paying out from your own accounts, with its own checks.
KwiikPay onboards companies incorporated in the European Economic Area, the United Kingdom, Gibraltar, Switzerland and Canada, where any authorisation their activity requires is current. Companies elsewhere are assessed individually, with no presumption of approval. Account opening is by invitation: request an account and the team replies within one business day.
KwiikPay is a trading name of KWP Finance Limited — registered in Canada as a Payment Service Provider under the Retail Payment Activities Act (RPAA), supervised by the Bank of Canada, and as a Money Services Business with FINTRAC (MSB registration number C100000942), including dealing in virtual currency. These are registrations, not licences. KwiikPay is not authorised by the FCA. KwiikPay is not a bank; banking and e-money services are provided by regulated partner institutions.
Building payouts or FX into your platform?
Tell us your money flows, currencies and volumes and the right person will reply within one business day.
Talk to sales See the developer pageSources
Checked on 25 October 2026. This is general information, not legal advice.
- European Union: Directive (EU) 2015/2366 on payment services, including the exclusions in Article 3.
- United Kingdom: Payment Services Regulations 2017, Schedule 1.
- Canada: Bank of Canada, PSP registry, under the Retail Payment Activities Act.
FAQs
What are embedded payments?
Embedded payments are payment features built directly into software whose main job is something else: booking, invoicing, accounting, a marketplace or a platform for contractors. The user pays, gets paid or pays others without leaving the product, while a payments provider behind the scenes moves the money.
What is the difference between embedded payments and embedded finance?
Embedded payments are a subset of embedded finance. Embedded finance is any financial service offered inside non-financial software: payments, but also accounts, cards, lending, insurance and investing. Embedded payments cover only the movement of money: accepting payments, paying out and converting currency.
What is an embedded payment solution?
An embedded payment solution is the provider and technology a platform uses to offer payments inside its product: usually an API, webhooks and sometimes ready-made components, plus the regulated infrastructure that holds and moves the money. Embedded payments software and embedded payments platforms are other names for the same thing, sometimes with dashboards and onboarding tools for the platform's own users.
What are embedded online payment solutions?
Usually, embedded checkouts: payment forms or components that let a website or app accept card and wallet payments from customers without sending them to another site. They are one kind of embedded payment solution. Others handle payouts, accounts and currency conversion rather than checkout.
Does a platform need a licence to offer embedded payments?
It depends on the model and the country. In many set-ups the payments provider is the regulated party and the platform does not hold customers' money. If the platform itself receives, holds or transfers other people's money, it may need its own authorisation, registration or licence, and exclusions such as the commercial agent exclusion in EU and UK payment rules are narrow. Take legal advice on your specific flow before you launch.
How do platforms make money from embedded payments?
Typically through a fee or markup on transactions, a share of the provider's fees, subscription tiers that include payment features, or better retention because payments sit inside the product. Whatever the model, the price your users pay should be clear to them before they pay.
Does KwiikPay offer embedded payments?
KwiikPay offers accounts, FX and payouts by API that a platform can build into its own money flows, such as holding GBP, EUR and USD, converting currency and paying suppliers, sellers or contractors. It does not offer card acceptance, so it is not an embedded checkout. If you want your own customers to hold balances through your product, talk to us before you design for it.
