Fintech & open banking2 min read

UX Challenges in Embedded Finance

Embedded finance puts a financial service inside a non-financial product: a payment option in a marketplace, a loan offer in a software tool, an insurance quote in an app. The user experiences one brand, but several parties are involved. That split creates UX challenges that a single-brand product never faces.

Whose brand is the user trusting?

The user may see your brand, a partner bank's brand and a regulated provider's disclosure in the same flow. Decide early which brand leads each step, and make the handoffs visible. A user who suddenly sees a different name on a payment screen can feel misled, even when the arrangement is legitimate.

Split responsibility in the interface

Each party has obligations: disclosures, consent, refunds, support. Map which party owns each moment, and make sure the interface reflects it. Support routing is a common failure point. A user with a payment problem should know whether to contact you or the provider, before they are stuck.

Disclosures in context

Regulated information must be visible when it matters, not only in terms and conditions. Place the cost, the repayment schedule or the cancellation rule where the user decides. Test whether users can state the key term after reading the screen.

Designing for a partner's product

When the financial step is delivered by a partner's system, you control only part of the experience. Agree on the design rules, the states the partner must support, and the error messages they will show. Without this, the flow is a patchwork of styles and behaviours.

Timing and expectation

Embedded offers often appear at a moment the user did not plan for, such as checkout or a form submission. Show the offer as an option, not a gate, and let the user continue without it where the product allows. An offer that blocks the main task creates resentment.

Measure the journey across parties

Track the handoffs as well as the outcomes: offer shown, offer opened, application started, decision received, product used. Include partner-side drop-off in the review, so you see where the experience breaks between systems.

A quick review

QuestionWhat to check
Which brand is visible at each step?Clear and expected
Who handles which support request?Stated in the interface
Are key terms visible in context?Yes, at the decision point
Can the user continue without the offer?Yes, where allowed
Are partner states designed?Yes, including failure

Embedded finance can feel seamless, but the seams are where users get lost. Design the seams on purpose, and the experience can be simple without hiding who is responsible for what.

Next step

Get help improving conversion

Send me the page or flow that loses people. I will tell you where the friction is and what to change first.

Open the conversion page