Embedded Lending: How the Marketplace Model Works

More UK business loans now arrive through a banking app than through a direct application to a lender. A challenger bank’s interface shows the offer, the account and the repayment schedule — but a separate company, plugged in through an API, is often the one underwriting the loan, funding it, and holding the credit risk. For a founder comparing options, that distinction rarely appears above the fold. It matters anyway: who you’re contractually bound to shapes what happens when a payment fails, a covenant is triggered, or terms need renegotiating. This lesson explains how the embedded lending model works, and what to check before you sign.

The mechanism

Embedded lending works through a straightforward architecture: a bank or platform with an existing customer relationship — a challenger bank, an accounting platform, a payments processor — integrates a specialist lender’s product directly into its own interface via an API. The customer sees a loan offer inside their banking app or software dashboard and applies without leaving that interface. But the entity actually assessing creditworthiness, extending the funds, and carrying the loan on its balance sheet is the specialist lender behind the integration — commonly a business-focused non-bank lender such as iwoca, rather than the bank or platform itself.

This differs structurally from a bank originating and holding its own loan book. In a direct model, the bank underwrites, funds and owns the credit risk end to end. In the embedded model, the interface and the balance sheet are split across two companies, connected by an API rather than a single institution. The commercial logic runs both ways: the specialist lender gains distribution without building consumer-facing banking infrastructure, and the bank or platform offers a lending product without carrying the credit risk itself. For the customer, the visible experience — application, decision, repayment schedule — looks identical regardless of which model sits underneath it.

What this means for you

The distinction matters at three specific moments. First, at underwriting: the criteria used to approve or decline your application are the embedded lender’s, not the bank’s — a rejection inside a banking app reflects the lender’s model, not the bank’s. Second, at a problem: if a payment fails, you need a covenant waiver, or you want to restructure, the right call is to the lender managing the loan, not the bank’s general customer service line — misdirecting the call costs time you may not have. Third, at pricing: an embedded offer can carry a partner margin that a direct application to the same lender doesn’t, so the convenience of a single interface isn’t always the cheapest route.

Where it doesn’t matter: your day-to-day banking relationship, your current account terms, and your existing facilities with other lenders are unaffected by any single embedded partnership. This is a distribution question, not a signal about the overall UK credit market or about whether now is a good time to borrow.

Diagnostic

Before your next application, run this check on any loan offer that appears inside a banking app, accounting platform, or payments dashboard rather than through a lender’s own site:

1. Does the loan agreement name a lending entity different from the platform showing the offer?
2. Is there a direct-application route to that same lender, and does it quote a different rate?
3. Do you know which company’s customer service line to call if the repayment schedule needs to change?

If you can’t answer question three with confidence, you don’t yet know who you actually borrowed from.

What to do this week

• First — foundation. Pull the loan agreement for any active facility that arrived through a banking app, accounting platform, or payments dashboard rather than a direct lender application, and identify the actual contracting entity in the small print. Do this regardless of whether the loan is performing well; the point is knowing who to call, not fixing a problem.
• Second — layering. Update your facility or loan register — whether that’s a simple spreadsheet or a dedicated tool — to record the true lending entity against each facility, separate from the platform brand it appeared under. A five-minute fix now saves a frantic search later.
• Third — optionality. If you’re weighing a new embedded offer, request a direct quote from the underlying lender where one exists. Compare the two rates before accepting the embedded convenience; the difference, if any, tells you what the marketplace margin is costing you.

Why this matters now

Embedded finance is not a temporary trend — it’s becoming the default distribution model for SME credit in the UK, and the pattern will only deepen as more banks and platforms choose partnership over building lending capability in-house. The 2028 financial literacy implementation date assumes a baseline of operator competence that includes knowing who actually holds your credit relationships, not just which app you log into. Founders who build the habit now — checking the contracting entity, tracking it properly, comparing embedded pricing against direct quotes — will find it compounds as embedded products spread from lending into insurance, payments and working capital tools over the next two years. The founders caught out won’t be the ones who borrowed poorly; they’ll be the ones who never knew who they’d borrowed from.