---
title: "xChange Financial Services — Maximilian Dahl"
description: "Product design case study by Maximilian Dahl: Wallet 1.5 and Credit Limit at Container xChange. Around 80% fewer finance support requests, +72% wallet payouts."
url: https://max.does.systems/en/work/xchange-financial-services/
lang: en
---

Product Design Case Study · Fintech

# Making financial logic clear, limiting credit risk

Container xChange is a B2B marketplace for shipping containers. Its wallet brought together credits, income, invoices and credit limits, and every month 150–200 support requests came in about not understanding it. As Lead Designer, I reorganised the financial overview and connected payments to risk limits across two projects.

Read the case

Key facts

- around 80%
   fewer finance support requests

- +72%
   wallet payouts

- Seven figures
   recovered outstanding customer receivables, joint initiative

Role · Lead Designer, Financial Services

Collaboration · Product, Engineering, CFO, Account Management

Projects · Wallet 1.5 · Credit Limit

In short ~1 min

1. 01 · Problem
   150–200 requests a month
   The wallet held credits, income, invoices and credit limits, and hardly anyone understood it.

2. 02 · Intervention
   Reordered, tied to risk
   Wallet 1.5 reordered the financial overview, Credit Limit tied payments to risk limits.

3. 03 · Outcome
   Foundation for 2.0
   Meant as a stopgap, Wallet 1.5 became the base for the next version.

Financial logic has to be readable. I ordered the wallet so customers understand it, and tied payments to risk limits.

xChange Financial Services

## At a glance

- −80%
   finance support requests, the goal was −15%
   **−80%**finance support requests, the goal was −15% · Wallet 1.5

- +72%
   wallet payouts, the goal was +20%
   **+72%**wallet payouts, the goal was +20% · Wallet 1.5

- Seven figures
   recovered receivables
   **Seven figures**recovered receivables · Credit Limit, a joint initiative

1. Problem
   150–200 requests a month
   The wallet held credits, income, invoices and credit limits, and hardly anyone understood it.

2. Intervention
   Reordered, tied to risk
   Wallet 1.5 reordered the financial overview, Credit Limit tied payments to risk limits.

3. Outcome
   Foundation for 2.0
   Meant as a stopgap, Wallet 1.5 became the base for the next version.

02 · Wallet 1.5

## Making financial logic traceable

More than 20 interviews and hundreds of support calls showed the same pattern: users did not understand their invoices or the categories and statuses of their transactions. Balances and open amounts were hard to follow, and there were no direct payment actions.

Context

The decision: 1.5 instead of 2.0

My target vision was Wallet 2.0: modular dashboards, AI-assisted overviews, new visualisations and flow patterns. Given the available scope and the existing codebase, we deliberately reduced it to 1.5: solve the pressing comprehension problems, touch the backend as little as possible, and lay a foundation for 2.0.

### The overview beside the details

A two-column system: a compact financial overview on the left, transaction details on the right. Invoices and statements have their own tabs, and explanation patterns show, for example, how the available payout is made up.

![Wallet 1.0 with balance and recent invoices above the transaction history](https://max.does.systems/assets/cases/xchange-financial-services/wallet-overview-1.0.png)

Wallet 1.0: balance and recent invoices above the transaction history.

![Wallet 1.5 with the financial overview on the left and transaction details on the right](https://max.does.systems/assets/cases/xchange-financial-services/wallet-overview-1.5.png)

Wallet 1.5: financial overview on the left, transaction details on the right.

In the invoice table we deliberately accepted higher density: status, amounts, due date and deal reference sit together with the payment action, so everything needed to handle an invoice is in one place.

Wallet 1.5 went live in stages, built with shared UI components and tokens. We tracked support requests and feedback through Zendesk, DataDog and Account Management.

### Outcome

Finance support requests · Goal: −15% · around −80% · Goal exceeded

Wallet payouts · Goal: +20% · +72% · Goal exceeded

Interviews also confirmed that users understood their credit limits better.

Learning

Versions give stakeholders a shared language: 1.0, 1.5 and 2.0 separate what gets built now from where it is heading. The company later adopted this language company-wide.

03 · Credit Limit

## Connecting payments to risk limits

At the end of 2023, high negative customer balances became visible. Credit limits were poorly defined, and customers could exceed them before Operations could step in. I initiated the project and designed the payment flow and the warning logic.

For Credit Limit we were a team of seven: the PM, the tech lead, me in design and four developers; later the same team for all of Financial Services. When our PM was out, I carried the role for a while. The PM and I proposed the credit limits for the launch; the CFO and Account Management set them.

Open invoices: please mind your credit limit

Level 1 · Notice

Dismissible. Points to open invoices and the credit limit.

Credit limit exceeded: payment required

Level 2 · Payment request

Stays in place, with restrictions until payment.

Schematic view of the two warning levels.

Context

The decision: a payment flow built from modules

I separated internal product steps from flows at external payment providers. The modal building blocks could be recombined for each payment occasion; only the checkout/summary step stayed fixed. This modularity was later used for further payment flows.

![Payment flow model with internal and external paths](https://max.does.systems/assets/cases/xchange-financial-services/payment-flow-architecture.png)

Flow model: internal product steps (“On Platform”) and external payment paths (“Off Platform”), shown for best-case scenarios. Click to enlarge.

![Compact checkout with payment method and payment overview](https://max.does.systems/assets/cases/xchange-financial-services/payment-checkout-simple.png)

Compact: payment method and amount.

![Extended checkout with top-up, invoice selection and payment method](https://max.does.systems/assets/cases/xchange-financial-services/payment-checkout-extended.png)

Extended, the same module: top-up, invoice selection and payment method.

### Outcome

First solution live · Team delivery · 4 weeks

Recovered outstanding receivables · six figures first, later · seven figures · joint initiative

Learning

I had been carrying a lot of the coordination. I handed it back to the project manager as their domain and focused on mine, the design. We kept making decisions together as a trio of product, engineering and design. That clearer split significantly improved the quality of the design solutions.

04 · Outcome and reflection

## What it achieved and what I would do differently

Finance support requests · Goal: −15% · Wallet 1.5 · around −80%

Wallet payouts · Goal: +20% · Wallet 1.5 · +72%

Recovered receivables · Credit Limit · joint initiative · seven figures

> Wallet 1.5 was meant as a stopgap and became the foundation for 2.0. Credit Limit reduced financial risk quickly and created building blocks that carried further payment flows.

### What I would do differently today

1. A smaller stakeholder group
   Too many participants slowed Credit Limit down. A more selective group would have been faster.

2. Protect focus
   Wallet 1.5 could have shipped in half the time. Side projects with higher priority stretched the plan.

3. Refine earlier
   The first warning UI needed adjustments after launch to become clearer.

**Case notes · How to read this case.**

Evidence · My own case documentation for both projects and a letter of recommendation.

Images · All screens show demo data. The warning levels are a schematic rebuild.

Team effort · Financial results come from joint initiatives.

Last updated · October 2026
