Embedded Lending Platforms Explained: Who Holds the Risk, the License and the Customer?
In embedded lending, the brand the borrower sees is rarely the one holding the license or the losses. Here's how risk, permissions, conduct duties and data really split, and how that changes across the EU, UK, India and Southeast Asia.
Three parties, one loan: the split most buyers misread
Before you sign with an embedded lending platform, ask four questions. Who is legally the lender? Who absorbs defaults? Who answers to the regulator when a borrower complains? Who owns the borrower relationship after the loan is repaid? Buyers often assume one party holds all four answers. It rarely does.
Most embedded finance lending setups involve three roles:
- The lender of record: a bank, licensed non-bank lender or NBFC whose name is on the credit agreement and whose license the loan is made under.
- The distribution platform: the marketplace, software company, retailer or payments provider whose customers see the offer inside its own checkout, dashboard or app.
- The technology vendor: the lending as a service provider that runs decisioning, origination workflows, servicing and sometimes collections, usually through APIs the platform embeds.
Sometimes one company plays two roles. A payments firm with its own lending license is both distributor and lender. But obligations attach to the role, not the logo. Regulators in every major market look past white-label branding to whoever extends credit and whoever arranges it. Your contract structure should do the same.
Who carries the credit risk: four common structures
Credit risk follows the balance sheet, and contracts can move it around. Buyers usually meet one of four structures. Each changes your economics and your regulatory exposure.
| Structure | Who funds the loan | Who bears losses | Typical fit |
|---|---|---|---|
| Lender balance sheet | Bank or licensed lender | Lender, priced into rate or merchant fee | Platforms wanting revenue share without credit exposure |
| Originate-and-sell (forward flow) | Lender originates, then sells to platform or investor | Buyer of the receivables after a short hold period | Larger platforms with capital and data advantages |
| Risk share or first-loss guarantee | Lender | Platform covers first losses up to a cap; lender takes the rest | Platforms with proprietary data that want better approval rates |
| Platform as lender | Platform's own capital or credit facility | Platform | Firms that hold their own license, often for merchant financing |
Merchant cash advance software adds a twist. In many markets an MCA is structured as a purchase of future receivables rather than a loan, which can put it outside lending rules. The funder still carries risk, recovered through a share of daily card or payout volume. That works well when the platform controls settlement, as payment processors and marketplaces do. Don't assume the receivables framing protects you everywhere. Some jurisdictions recharacterize these products as credit when repayment terms look fixed.
Our view: for a first program, take no credit risk, or at most a capped first-loss share. You need a year or more of performance data before you can price risk better than the lender can. Uncapped exposure on an untested book can erase years of revenue share.
Who needs the license: EU, UK, India and Southeast Asia compared
Regulators draw a similar line almost everywhere: lending is one activity, and arranging or introducing credit is another. The details vary a lot, and they decide whether your platform needs its own authorization.
| Region | Lender of record | Distribution platform | Points buyers miss |
|---|---|---|---|
| European Union | National license; some member states reserve lending to credit institutions, others license non-bank lenders | May qualify as a credit intermediary under consumer credit rules | The revised Consumer Credit Directive (EU) 2023/2225 begins applying from late 2026 and widens scope to many interest-free, deferred-payment and small-value products, with national transposition details differing. DORA puts ICT third-party obligations on regulated lenders, which flow down to vendors. |
| United Kingdom | FCA authorization for consumer credit lending | Credit broking is a regulated activity; firms are authorized directly or act as an appointed representative of an authorized principal | Consumer Duty reaches the whole distribution chain. Deferred payment credit is moving into FCA regulation. Lending to limited companies is largely outside the consumer regime. |
| India | Bank or RBI-regulated NBFC | Lending service provider (LSP) acting under contract with the regulated entity | RBI digital lending rules generally require disbursals and repayments to flow directly between borrower and regulated entity, require a key fact statement, and limit default loss guarantees (currently to 5% of the portfolio). |
| Southeast Asia | Varies: bank, licensed moneylender, financing company or licensed P2P operator | Often unregulated as a distributor, but increasingly scoped in | Indonesia's OJK regulates P2P lending and BNPL closely. Singapore relies on moneylender licensing plus an industry BNPL code. Malaysia is bringing non-bank and BNPL credit under a dedicated consumer credit regime. |
The practical consequence: in India and the UK, a platform that merely embeds a lender's offer is still regulated, or contractually supervised, as a distributor. You can't treat the program as "the bank's problem." In parts of Southeast Asia and some EU states, the same activity may need no authorization today, but the rules are tightening. Build the program as if distributor obligations will apply. Have local regulatory counsel confirm the position in each market before launch, because the answer differs by product, borrower type and country.
Consumer-protection duties don't transfer with the branding
When a borrower complains about an unaffordable loan or aggressive collections, the regulator goes to the lender of record. The lender then goes to its contracts with the platform and the vendor. Conduct duties sit with the licensed party, but whoever controls each touchpoint performs them in practice.
Map every consumer-facing duty to an owner before you sign:
- Pre-contract disclosures: cost of credit, APR or equivalent, and fees, shown in the platform's interface but approved by the lender.
- Creditworthiness and affordability checks: run by the vendor's decision engine under the lender's credit policy. In the EU, AI-based credit scoring of individuals is classed as high-risk under the AI Act, which adds documentation and oversight work.
- Marketing and financial promotions: usually drafted by the platform, which is where most breaches start. A checkout button reading "pay later, no strings" can break promotion rules in several markets.
- Cooling-off and withdrawal rights: India's digital lending rules and EU consumer credit law both give borrowers exit windows your servicing flow must support.
- Complaints, hardship and collections: the lender owns the outcome, but the platform's support team often hears about the problem first.
For B2B programs, such as a point of sale financing platform for merchants or working capital inside accounting software, consumer rules mostly fall away. Sole traders and very small partnerships are the exception. Several jurisdictions, including the UK, can treat them as consumers for credit purposes. If your merchant base includes them, you're running a consumer program for part of your book.
Who owns the customer and the data after the loan
This is where the commercial value lives, and where contracts are often vague. The borrower is the platform's customer before the loan and usually wants to stay that way. The lender, though, has legal duties that require it to keep and process the borrower's data.
Under GDPR, UK GDPR, India's Digital Personal Data Protection Act and Singapore's PDPA, roles follow who decides why and how data is used, not who holds the database. In most programs the lender is a controller for credit decisioning and regulatory record-keeping, the platform is a controller for its own customer relationship, and the technology vendor is usually a processor. Treating the platform as a mere processor of loan data is a common mistake. It can stop the platform from using repayment behavior to improve its own products, or expose it if it does so anyway.
India goes further. Its rules restrict what an LSP may collect and store, and expect explicit, purpose-specific consent. Platforms there should expect to see less loan data than in the UK or EU.
Get these points into the contract:
- Which data fields flow back to the platform, how often, and on what legal basis.
- Whether the lender may market other products directly to borrowers it met through your platform. Insist on a non-solicitation clause.
- Portability on exit: whether you can move the active book or future originations to another lender without re-consenting every customer.
- Where data is hosted, given localization expectations in India and Indonesia and cross-border transfer rules under GDPR.
Cost drivers, red flags and a decision rule for choosing a structure
Pricing for lending as a service varies widely by contract. As typical 2026 market ranges, expect implementation fees from tens of thousands to a few hundred thousand USD, platform fees from a few thousand to tens of thousands of USD a month, and per-application or volume fees that run from low single-digit dollars per application or roughly under 2% of originated volume. Lender partners take their margin through the rate, merchant discount or a split of interest income. Local pricing differs, especially in India and Southeast Asia, so confirm figures with each vendor.
The costs that catch buyers out are rarely the headline fees:
- Compliance work for each new market, including disclosure templates, local-language documents and regulatory reporting.
- Credit bureau and KYC data costs, which grow with application volume rather than approvals.
- Collateral or reserve accounts that lenders require from platforms in risk-share deals.
- Exit costs if your lender relationship sits inside the vendor's contract.
Red flags in proposals: a vendor that can't name the lender of record for each market; first-loss guarantees with no cap; funds flowing through the platform's or vendor's own accounts where local rules require direct flows, as in India; marketing copy the lender hasn't approved; and contracts where the vendor, not you, holds the lender agreement.
A workable decision rule: if you're launching in one or two markets with no lending track record, choose a structure where a licensed lender funds and holds the risk, you act as introducer or broker, and the vendor is a processor under a direct three-way agreement. Move to risk share or your own license only once you have at least a year of loss data and a clear view of each market's licensing path. Before shortlisting vendors, ask each to fill in a one-page matrix showing who holds risk, license, conduct duties and data in every target country. A vendor that can't complete it isn't ready for your program.
Quick answers
Does my platform need a lending license to offer embedded loans?
Usually not, if a licensed lender extends the credit and you only distribute it. You may still need permission as a credit intermediary or broker. In the UK that means FCA authorization or appointed-representative status, and in India you operate as a contracted lending service provider. Rules vary by product, borrower type and country, so have local regulatory counsel confirm your position.
Who is liable if a borrower complains about an embedded loan?
The lender of record answers to the regulator and the borrower. It will usually pass liability back to the platform or vendor through contract indemnities when their actions caused the problem, such as non-compliant marketing or a faulty affordability check. Your contracts should say who handles complaints and who pays redress.
Is merchant cash advance software regulated like lending?
In many markets, MCAs are structured as purchases of future receivables and fall outside consumer lending rules, especially when the recipient is a company. Some jurisdictions recharacterize them as credit when repayment is effectively fixed, and sole traders may get consumer-style protections. Get a legal opinion for each market before relying on the receivables framing.
Can we use loan repayment data to improve our own products?
Only if your contracts and privacy notices support it. Under GDPR, UK GDPR, India's DPDP Act and similar laws, you'll generally need to be a controller for that purpose, with a valid legal basis or consent. India puts extra limits on what lending service providers can collect and store.
What is a first-loss guarantee, and should we offer one?
It's an agreement for the platform to cover an initial slice of defaults, often expressed as a percentage of the portfolio, before the lender takes losses. It can raise approval rates and your revenue share, but some regulators limit it (India caps it at 5% of the portfolio under current RBI guidelines) and lenders elsewhere often require cash reserves. Keep it capped, and avoid it until you have performance data.
How long does it take to launch an embedded lending program?
With a vendor that already has a lender partner in your market, a single-product launch often takes a few months, including legal, compliance and integration work. Adding a new country or bringing in your own lender commonly takes longer, mostly because of contracts and regulatory review rather than technology. Ask vendors for timelines from comparable launches.
Written by the Wealth Deskplus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.