An embedded-finance partnership needs an evidence design before launch: who manufactures and distributes, which firm controls each customer interaction, how total price and value are assessed, what outcome data crosses the chain, where complaints and vulnerability signals go, and how firms act when a partner's process creates foreseeable harm.
- Key takeawaysMap regulated roles and customer-control points rather than relying on branding.
- Decision frameworkAn embedded-finance partnership needs a shared view of customer outcomes across the relevant distribution chain.
- Establish the actual chainThe FCA explains that the Consumer Duty can apply to firms with a key role in retail customer outcomes even without a direct customer relationship.
- Price the complete customer journeyThe Duty's price-and-value provisions address distribution arrangements and remuneration, not only the manufacturer's headline price.
- Agree data before the launch campaignSpecify the information each party provides, its definition, frequency and escalation route.
Answer first: An embedded-finance partnership needs an evidence design before launch: who manufactures and distributes, which firm controls each customer interaction, how total price and value are assessed, what outcome data crosses the chain, where complaints and vulnerability signals go, and how firms act when a partner's process creates foreseeable harm.
Key takeaways
- Map regulated roles and customer-control points rather than relying on branding.
- Assess total customer price and value across the distribution chain.
- Agree event-level outcome data, cohorts, ownership and escalation before launch.
- Test support, restriction and exit as joint customer journeys.
Decision framework
| Decision area | Evidence to require | Risk it controls |
|---|---|---|
| Role | Manufacturer/distributor/control point is explicit | Responsibility gap |
| Value | Cumulative price and benefit assessed | Layered fees obscure poor value |
| Data | Definitions, frequency, lawful basis and owner agreed | No outcome evidence |
| Issue | Complaint, vulnerability and incident route tested | Customer bounced between firms |
| Exit | Restriction and termination protect existing customers | Orphaned servicing |
An embedded-finance partnership needs a shared view of customer outcomes across the relevant distribution chain. The regulated provider may hold product and pricing information while a software platform controls presentation, onboarding and much of the support. Neither side can assess the complete experience from its own dashboard alone.
The practical task is to identify each firm's role, the evidence it needs and the action it can take when something goes wrong. A contract saying both parties will comply is a beginning, not an operating model.
Establish the actual chain
The FCA explains that the Consumer Duty can apply to firms with a key role in retail customer outcomes even without a direct customer relationship. It also asks regulated firms to consider risks introduced by participants outside the Duty. 1 Applicability depends on the activity, customer and role; embedded finance is not itself a single legal category.
Draw the chain from product manufacture through distribution, customer support and exit.
Mark who sets charges, approves wording, determines eligibility, handles complaints and can suspend sales. Distinguish a technology supplier from a distributor where the facts support that distinction.
This map often exposes a gap. The provider assumes the platform explains exclusions; the platform assumes the provider's terms do that work. The customer encounters a short sales screen and never sees the explanation either party intended.
Price the complete customer journey
The Duty's price-and-value provisions address distribution arrangements and remuneration, not only the manufacturer's headline price. 23 Partners need enough information to assess how the complete arrangement affects value.
List mandatory fees, optional charges, commissions and conditions that can change the cost.
Connect them to customer usage. An apparently modest charge may become material when a customer performs the same action repeatedly.
Use illustrative customer journeys to test the arithmetic, clearly labelled as examples. A customer making two transactions and one making fifty can experience different effective prices. Avoid presenting an average that conceals a poorly served group.
Agree data before the launch campaign
Specify the information each party provides, its definition, frequency and escalation route.
Useful fields may include abandonment, declined applications, complaints, support delays, cancellation difficulties and outcomes for relevant customer groups.
Keep measurement consistent. One partner's complaint may mean a formally logged case; another may count every unhappy chat. Without a shared definition, an impressive consolidated dashboard can conceal incompatible populations.
Design information sharing with privacy and necessity in mind. Often the first useful exchange is an aggregate pattern or a case reference, rather than a complete personal-data export. Determine lawful handling and access controls for any identifiable information.
Give an issue somewhere to go
Every material pattern needs an owner who can change something. A manufacturer may alter product design, while a platform changes presentation or removes a confusing sales step. The governance group should have authority beyond circulating reports.
Set escalation triggers and record decisions. If complaints suggest customers misunderstood eligibility, establish whether new sales continue during investigation and who approves any remediation.
Do not let the revenue split determine the conclusion. A partner earning a substantial commission may have useful distribution capabilities, but that does not by itself demonstrate fair value. The assessment needs evidence about what the customer receives.
Test support and exit across firms
Run a customer scenario from the platform into the provider's support process and back. Can staff identify the product, legal entity, complaint history and next action? Does a cancellation request reach the party able to stop the relevant service?
The most revealing test is often a customer with an unusual circumstance. Standard cases follow the designed route. Exceptions show whether the partnership can exercise judgement without sending the customer between organisations.
Review incentives at the point of distribution
Map which behaviours the commercial arrangement rewards. A partner paid for completed applications may prioritise volume, while the provider carries support and remediation costs later.
That does not establish misconduct. It identifies where monitoring should test whether customers understand the offer and whether applications are appropriate for the intended market.
Use a hypothetical case review: customers attracted by a simple headline benefit repeatedly discover a material condition only after joining. Ask which party approved the message, which could see abandonment and complaints, and who had authority to change the journey.
The answer reveals whether governance follows the actual influence each party has.
Make small populations visible
An aggregate outcome can look acceptable while a smaller customer group encounters repeated difficulty. Choose meaningful segments and show counts, but avoid interpreting unstable percentages from a handful of cases.
Where data is thin, use targeted case review and record the limitation. Missing evidence should prompt a proportionate investigation rather than an unsupported assurance that no problem exists.
Keep a shared action log with evidence of completion. If the platform changes wording, the provider should know which version went live and when. If the provider changes eligibility, the platform needs that information before customers encounter the new rule. A distribution chain becomes manageable when product changes travel as reliably as sales data.
What should the partnership review?
Review outcomes by product version and distribution channel, not just total sales and revenue. Record what changed after the review and whether the change worked.
Give the partnership one shared action log connecting outcome evidence to a product or process change. Revenue reporting already crosses organisational boundaries; evidence of confusion, poor support or unsuitable distribution needs an equally reliable route.
A practical 90-day implementation plan
- Walk the customer journey and mark the legal entity controlling each decision and communication.
- Create a shared outcome-data contract with cohort fields and escalation thresholds.
- Run complaint, vulnerability, refund and partner-exit simulations before growth spend.
- Hold a joint governance review that records actions, owners and proof that interventions improved outcomes.
Frequently asked questions
Does each firm need to redo every other firm's value assessment?
Not necessarily. FCA guidance distinguishes responsibilities, but distributors need relevant information and each firm remains accountable for the price, service and outcomes it controls.
What data should partners share?
Share the minimum lawful data needed to monitor defined outcomes: journey completion, decline reasons, support, complaints, vulnerability indicators, arrears, refunds and cohort differences.
Who owns a complaint?
The operating design should route it to the responsible firm without making the customer diagnose the distribution chain. Handoffs and response ownership should be explicit.
Reporting by Shoreditch Talk




