OneMoney

I re-designed the core user experience for India’s largest account aggregator while ensuring compliance with the changing government financial regulations.
Mobile screen showing a consent approval page for sharing personal finance management data, including two bank accounts selected and statement period from January 20, 2025 to January 20, 2027.

The challenge of compliance

OneMoney processes 1.2B+ financial data transactions annually, where strict compliance with RBI(Reserve Bank of India) regulations is a core differentiator. The existing platform had outdated branding and a function-heavy, clunky user experience. The challenge was to improve the UX and align it with the latest brand design, while ensuring every screen remained fully compliant with government guidelines.

Strict Regulation

Clunky UX

Approval Bottlenecks

The Goal

1. Re-design the OneMoney AA flows and standardize them across multiple use cases.

2. Ensure every screen is compliant with RBI regulations

The Process

Overview:
OneMoney AA has several platforms with different use cases. I worked across several of these products and led two key projects:

1. Designing end-to-end Loan journeys (OneMoney Lending)

2. Redesigning our standard WebRD, a web app for getting consent to fetch financial data.

Since we provided custom UX to our clients, a core challenge across all OneMoney use cases was maintaining consistency and compliance across all of them, while also leaving room for specific client requirements.
Two smartphones show LendSphere consent screens requesting approval to share financial data for loan evaluation, monitoring, and collections with approve and reject buttons.
Mobile screen showing consent form for fetching user data including deposit, account statement, data fetching frequency, consent validity, storage duration, and loan underwriting purpose with Proceed and Back buttons.
OneMoney Lending - Loan Application App:
Lending had several sub-categories of use cases, such as Credit Line, Loan Monitoring, Collection, Evaluation etc. I designed user flows for seven such use cases while ensuring consistency in spacing, fonts, branding.


I used outdated OneMoney flows as reference for the content and compliance that needed to be included in the design. Re-designing this was sensitive as any mistake could cause severe damage to the organization.
An unexpected hurdle:
The consent approval screen was the most tightly regulated part of the flow.

Regulations required all consent-related detail, such as data validity, legal entity, and purpose, to be displayed on the same screen where consent was requested, with no dropdowns or additional steps allowed.

All possible variations resulted in a dense, text-heavy interface that risked overwhelming users and reducing clarity at a critical decision point.
Mobile screens showing consent approval requests for sharing bank account data from HDFC Bank and ICICI Bank with details for loan evaluation, monitoring, and collection by LendSphere powered by OneMoney.
Mobile screen showing LendSphere app requesting user approval to share consent for ICICI Bank accounts with options to approve or reject consent.
Making it work:
Our team sat with the head of compliance for several hours, discussing regulations and design, until we found the most optimal balance between keeping it compliant and minimal strain on the users, with maximum clarity. 


We achieved this by displaying key information as a short paragraph (which went through a lot of reworks and approvals too), with the other details below it split in a two-column layout.


The whole process of optimizing this screen based on regulations took us several days and 30+ iterations! But we finally got it to be compliant without being text-heavy.
Standardizing OneMoney WebRD:
OneMoney makes customized UX flows for each client to link financial accounts of their users - unique according to their branding and requirements.

Sometimes this caused discrepancies between the different designers, developers, and also between certain repeating elements of the flows themselves.

I created a re-designed user flow that would be the holy grail for all designers and developers to refer to when creating any custom flows for a client. This standard flow had all possible edge cases and was part of a design system to ensure consistency during development. 


Mobile screen showing consent approval interface for sharing personal finance management data from two bank accounts with statement period, frequency, and consent validity details, with options to approve or reject.

The Outcome

Once approved by leadership, the standard flow became a reusable foundation for future implementations, significantly reducing approval cycles and compliance checks. The redesigned WebRD and Lending flows were well received both internally and externally, improving product performance and ensuring consistent design across platforms.
500k+

New App Downloads

28%

Improved Lending Accuracy

5%

Improved Bad Loan Prevention

Reflections

  • Every single screen had to be designed with utmost sensitivity, since any mistake that caused a compliance issue would have had major consequences to the business.
  • Since the business had so many sub-platforms, co-ordinating with several different team of developers to keep the design consistent across the board proved to be a challenge.

Other Projects

Want to work together?

Let's connect!