The Embedded Finance Entry Decision: Financial-Services-Led vs Commerce-Led Routes for Non-Fintech Brands
Every large non-fintech brand that gets serious about embedded finance eventually hits the same fork in the road, usually somewhere between the second and third planning workshop.
One camp wants to build financial products: wallets, accounts, cards, buy-now-pay-later, lending, insurance. The brand becomes, in effect, a fintech operating under its own name, using Banking-as-a-Service (BaaS) rails to plug into regulated infrastructure it does not want to build or own outright.
The other camp wants none of that, at least not yet. They want to fix the buying journey first: better product discovery, smarter payment routing, AI-assisted checkout, and only then start layering loyalty-linked payments, embedded BNPL, and rewards programmes on top of a commerce experience that already works.
Both are legitimate entry points into embedded finance. Both fail when a brand tries to do both at once, or picks the wrong one for its actual capabilities and risk appetite.
Why This Decision Gets Made Badly
Most organisations do not consciously choose a route. They inherit one, usually because a vendor pitched it, a competitor announced it, or a board member read about it on a flight.
The result is a programme that tries to be a fintech launch and a commerce transformation simultaneously, run by a team resourced for neither. Compliance timelines collide with product timelines. Procurement cannot decide whether it is buying a BaaS platform or a payment orchestration layer. Nobody can answer, cleanly, what the embedded finance programme is actually for.
A cleaner starting point is to treat this as a genuine strategic choice with two distinct entry motions, evaluate your organisation honestly against each, and commit.
Route One: Financial-Services-Led Entry
This route suits consumer brands and platforms that already have a large, trusted, engaged user base and want to monetise that trust by becoming a financial services provider in their own right.
The brand does not become a bank. It partners with a Banking-as-a-Service provider, and in the UK that partnership typically routes through an FCA-authorised e-money institution or a bank with an existing FCA/PRA dual-regulated licence, which issues the underlying regulated product (an e-money account, a card programme, a lending facility) while the brand owns the customer experience, the app, and the commercial relationship.
Who this fits
- Consumer platforms with high engagement frequency and strong first-party data on spending or saving behaviour
- Retailers or marketplaces with a loyalty base large enough to justify building a wallet or card product around it
- Brands whose core proposition benefits directly from owning the payment or credit relationship, not just facilitating it
What it actually requires
This is the higher-commitment route. A financial-services-led entry means accepting an ongoing compliance surface: safeguarding requirements, financial promotions rules, consumer credit regulation where lending is involved, and a BaaS partner relationship that has to be actively managed, not just switched on. It usually means a dedicated Head of Embedded Finance or equivalent owner, because the programme touches legal, risk, product, and engineering in ways a single product manager cannot coordinate alone.
The upside is real: a properly executed financial-services-led launch creates a new, durable revenue line and materially increases customer lifetime value, because the brand now sits inside the customer's financial life rather than at the edge of it.
Route Two: Commerce-Led Entry
This route suits large retailers and commerce businesses whose immediate opportunity is not becoming a financial services provider, but fixing and modernising the buying journey itself, with embedded finance arriving later as a second phase rather than the opening move.
The starting point here is AI-driven buying automation: structured product discovery, smarter payment routing across acquirers and payment methods, fraud and authorisation optimisation, and increasingly, agentic checkout flows where an AI agent completes parts of the purchasing journey on a customer's behalf. Our Agentic Commerce & Payments work sits squarely in this space.
Once that foundation is in place, and only once it is in place, a commerce-led organisation is well positioned to land-and-expand into embedded finance: loyalty-linked payment instruments, point-of-sale BNPL, cashback or rewards wallets, and eventually broader financial products, all built on a payments and data foundation that already works reliably at scale.
Who this fits
- Retailers and commerce platforms whose immediate pain is checkout conversion, payment authorisation rates, or fragmented payment infrastructure across channels
- Organisations led by a Director of eCommerce or CDO whose mandate is commerce performance first, financial services second
- Brands that want to test embedded finance appetite with a lower-commitment, loyalty-linked product before considering a full BaaS partnership
What it actually requires
The technical bar here is different. Commerce-led entry demands strong payment orchestration capability, the ability to route transactions intelligently across providers and methods, and increasingly, an architecture that can support agent-initiated payment flows as agentic commerce protocols mature. It demands less immediately in regulatory overhead, because the initial phase does not require issuing regulated financial products. But that overhead arrives later, when the loyalty-linked payment instrument or BNPL layer gets added, and organisations that treat that expansion casually often discover the compliance requirements they deferred rather than avoided.
A Decision Framework: Which Route Fits Your Organisation
Six questions, honestly answered, do most of the work of choosing.
- Where does your value sit today? If it sits in trust and engagement with an existing user base, financial-services-led entry has a clearer monetisation path. If it sits in transaction volume and buying journey quality, commerce-led entry is the natural starting point.
- What is your risk appetite for regulatory surface? Financial-services-led entry means accepting an ongoing compliance relationship from day one. Commerce-led entry defers most of that surface, but does not eliminate it.
- Who owns the mandate internally? A Head of Embedded Finance or CDO with a financial services remit points towards route one. A Director of eCommerce with a conversion and payments remit points towards route two.
- How mature is your payment infrastructure? A commerce-led entry assumes your payment orchestration is not yet where it needs to be. If it already is, you may be closer to route one than you think.
- What does your board actually expect? A promise to "launch a wallet" sets different expectations, timelines, and success metrics than a promise to "improve checkout conversion and lay groundwork for embedded finance."
- Can you resource one route properly, or would you spread a team too thinly across both? Under-resourcing either route is worse than choosing the smaller of the two.
Neither route is inherently superior. The financial-services-led route tends to generate a bigger strategic prize with a bigger upfront commitment. The commerce-led route tends to generate faster, lower-risk wins with a longer runway to the same eventual destination, especially where AI-driven payment orchestration is already a live priority. Our Embedded Finance & Digital Wallets practice supports both entry motions, because the right answer genuinely depends on where an organisation starts.
What Changes When AI Enters the Picture
Both routes are increasingly shaped by the same underlying shift: payment initiation is moving from purely human-triggered actions to a mix of human and agent-initiated transactions. For commerce-led organisations, this shows up first, in agentic checkout and automated buying journeys. For financial-services-led organisations, it shows up in how wallets, cards, and lending products need to support agent-initiated authorisation and spend controls as agentic commerce protocols mature across the industry.
Organisations that treat AI-driven orchestration as a bolt-on to either route, rather than a foundational design consideration, tend to rebuild that layer within eighteen months of launch.
Frequently Asked Questions
What is the difference between financial-services-led and commerce-led embedded finance entry?
Financial-services-led entry means a non-fintech brand partners with a Banking-as-a-Service provider to launch a regulated financial product, such as a wallet, card, or lending facility, and becomes a financial services provider under its own brand. Commerce-led entry means a retailer or commerce business first modernises its buying journey and payment orchestration using AI, then expands into embedded finance, typically loyalty-linked payments or BNPL, as a second phase.
Which route is right for a large UK retailer?
Most large UK retailers without an existing financial services mandate are better served starting commerce-led: fixing payment orchestration and buying journey performance first, then expanding into embedded finance once that foundation is proven. Retailers with a very large, highly engaged loyalty base and an internal mandate to build financial products may be better served starting financial-services-led.
Do we need a Banking-as-a-Service partner for both routes?
A BaaS partner is required for financial-services-led entry from the outset, since it provides the regulated infrastructure behind any wallet, card, or lending product. Commerce-led entry does not require a BaaS partnership initially, but typically needs one once the organisation adds loyalty-linked payments or BNPL in its second phase.
What UK regulatory bodies are relevant to embedded finance entry?
The Financial Conduct Authority (FCA) authorises and supervises e-money institutions and payment institutions that underpin most embedded finance products in the UK. The Prudential Regulation Authority (PRA) and Bank of England are relevant where a bank-issued product is involved. Open Banking Limited governs the account-to-account and data-sharing standards that increasingly intersect with embedded finance and agentic payment flows.
How long does a commerce-led embedded finance entry typically take to reach its second phase?
This varies significantly by organisation, and any specific timeline should be validated against your own payment infrastructure maturity and regulatory scope rather than treated as a fixed benchmark; the honest answer is that it depends on how much orchestration and data foundation work is required before a loyalty-linked payment or BNPL layer can be added responsibly.
Can an organisation switch routes after starting?
Yes, and it happens regularly. A commerce-led organisation that proves out its payment orchestration often evolves toward a financial-services-led posture once it has the data, trust, and internal case to justify a BaaS partnership. The reverse is less common, because financial-services-led entry carries commitments that are harder to unwind.
Conclusion
The embedded finance entry decision is not a branding exercise or a vendor selection exercise. It is a question of where your organisation's value already sits, what regulatory surface you are genuinely prepared to own, and who inside your business actually holds the mandate to make it work.
Get that decision right, and the version of embedded finance you launch, whether it starts with a regulated wallet or a smarter checkout, will compound. Get it wrong, and you will spend a year building the wrong first phase.
Speak With Our Team
Innovify works with both financial-services-led and commerce-led organisations to design and build the right embedded finance entry point, from BaaS-backed wallet and card programmes to AI-driven payment orchestration ahead of an embedded finance expansion. If you are weighing this decision for your organisation, speak with our team to work through the framework against your own starting position.
