Turn regulatory complexity into a simple, human-centered experience, showing enterprise-level strategic thinking across three touch points:
- The Challenge & Strategic Opportunity
- Prototyping & Flow Design
- Revocation & Critical Error Handling
The Challenge & Strategic Opportunity
Section 1
Dashboard UX
Front End UI
Back End Data Systems
Take a cluttered data dump and re-org with applied IA principles to prioritise key metrics. Understand API constraints and latency through the developers eyes, ensuring the UI is designed gracefully while loading large datasets.
Goal
Implement the Account Information Service Provider (AISP) flow for Open Banking on desktop to provide users with aggregated financial insights within a complex data Dashboard from multiple sources.
Secondary Goal: To demonstrate strong understanding of front-end interactive design solutions for back-end data systems.
The Problem
Open Banking consent (esp. consent duration, renewal, and revocation) is inherently complex and intimidating for users, leading to high drop-off rates and potential regulatory fines.
Strategic Opportunity: Design a Consent Management Dashboard that not only meets legal requirements (i.e. PSD2, CMA) but also builds trust, by making the flow transparent and effortless.
Business & User Goals
User Success Metric: Allow users to manage their third-party connections with confidence and clarity.
Defining the Gold Standard Row Content
Shift the data from static information to high-trust insights that prioritises transparency. By balancing security indicators, such as timestamps and verified credit boost potential, the interface transforms complex Open Banking API calls into a true financial dashboard.

Gathering the principal players
This case study hinges on transforming a fragmented jigsaw of data and key UI elements, into a cohesive, high-trust narrative that fosters familiarity and security.
Thinking entity that symbolise Open Banking
As for modern AI-UX designer employing the hybrid model by prioritising the human skills is key:
Human
Journey designing, API and BE driven integrations, and user needs
A simple AI prompt
Create an abstract image graduated amorphous ‘thinking’ entity for a desktop financial dashboard using gradient blues and green
Navigation
An Open Banking action-oriented navigating sidebar needs to balance financial utilities like linked accounts and permission-driven consent with managing who has access to what.
This is unified by a collapsible, vertical navigation widget designed for scalability.

Prototyping & Flow Design
Section 2
Active consent
Data transparency
Design to steer strategy and make complexity feel simple.
Consent Management Dashboard
A clear, sectioned dashboard to manage connections

Active Consents List
- Designed a clean row view for currently active connections.
- Key Data Points – Recipient (AISP Name), Account Connected, Days Remaining (e.g., < or > 90 Days), Data Shared. PISP indicators, see: Gold Standard
- Inactive/Expired Consents List (>90 and < 90 days)

Notification design
- Visually separate expired consents
- Distinct iconography and colour for consents that just expired (e.g., < 90 days) vs. historical data (> 90 days)
- Revoke – Option to Re-authorise with a single click, simplifying the renewal process.
The Core Flow
Selecting & Confirming Account

Design Solution
How to clearly explain what data is being shared and for how long before the user is redirected to their bank.
Consolidate Account Identity with real-time Transactional Intelligence and transform fragmented data into a clear feedback that surfaces categorised spend and Live Balances for smarter budgeting, while removing the friction of manual entry.
Prototyping the solution
Goal
A clickable mid-fidelity prototype used to test the clarity of the pre-consent screen, specifically the messaging around account selection (e.g., allowing multi-account selection vs. single-account).
Introduced a concise, step-by-step journey summarising the flow, using a Just-in-Time disclosure model to manage information overload.
Revocation & Critical Error Handling
Section 3
Revoking
Micro-interactions
Attention to detail in critical flows.
3.1 Revoking Permission (The Off-Ramp):
- Design Focus: Making revocation (official cancellation of a decree, decision, or promise) frictionless but requiring clear confirmation.
- Solution: A two-step confirmation modal when a user clicks “Revoke Permission.” The modal clearly restates the consequences (e.g., “You will lose access to X, Y, Z insights. Do you wish to continue?”).
- Prototyping: Used a micro-interaction prototype to test the speed and visual feedback of the successful revocation state.
3.2 Error Handling & Resilience:
- Design Focus: Addressing common integration failures (e.g., bank connection timeout, token expiry).
- Solution: Designed specific error states that are human-centered and actionable:
- Instead of “Error Code 404,” use: “Connection Lost: Your bank session has expired. Please click here to re-authorize the connection.”
- Included a fallback mechanism on the dashboard to clearly mark a connection as “Action Required” if an intermittent error occurs.
Outcomes

Conclusions
The project proved that prioritising transparency and control in regulatory design is the highest leverage move. The focus on clear separation of active/inactive, <90/>90 day consents, and explicit error states transformed a legal requirement into a trust-building feature.

Leave a Reply