Back

Back

Back

Lydia Money Requests

Lydia is one of the main fintech startup in Europe, with 8 million users. It started as a pioneer in P2P mobile payments and gradually evolved into a comprehensive banking application. With Lydia, you can receive, spend, invest, save, and manage all your money more simply, with a single app. Available on the Apple Store and Google Store.

Product Design

User Research

B2C

Lydia Money Requests

Lydia is one of the main fintech startup in Europe, with 8 million users. It started as a pioneer in P2P mobile payments and gradually evolved into a comprehensive banking application. With Lydia, you can receive, spend, invest, save, and manage all your money more simply, with a single app. Available on the Apple Store and Google Store.

Product Design

User Research

B2C

Lydia Money Requests

Lydia is one of the main fintech startup in Europe, with 8 million users. It started as a pioneer in P2P mobile payments and gradually evolved into a comprehensive banking application. With Lydia, you can receive, spend, invest, save, and manage all your money more simply, with a single app. Available on the Apple Store and Google Store.

Product Design

User Research

B2C

3 highlights from Money Requests

Relying on Existing Peer-to-Peer Payment Patterns

Lydia users shared the following use case: when they pay for someone, they sometimes wish they were able to send a reimbursement request directly via Lydia, often at the moment of purchase (or in the hours that follow). By doing so, they hand over the responsibility to the friend who owes them and move one with their life.

3 highlights from Money Requests

Relying on Existing Peer-to-Peer Payment Patterns

Lydia users shared the following use case: when they pay for someone, they sometimes wish they were able to send a reimbursement request directly via Lydia, often at the moment of purchase (or in the hours that follow). By doing so, they hand over the responsibility to the friend who owes them and move one with their life.

3 highlights from Money Requests

Relying on Existing Peer-to-Peer Payment Patterns

Lydia users shared the following use case: when they pay for someone, they sometimes wish they were able to send a reimbursement request directly via Lydia, often at the moment of purchase (or in the hours that follow). By doing so, they hand over the responsibility to the friend who owes them and move one with their life.

Sending money to a friend is the most used action on the app, so we decided to build upon this existing flow, which we know is understood by the vast majority of users. It also makes sense to have a request flow that is perfectly symmetrical to the payment flow.

We therefore kept the following order :

  • Contact selection

  • Display of the Summary view

  • Amount input

  • Optional change of debited or credited account

  • Confirmation

We then simply needed to adapt the summary screen while keeping the same logic: writing a simple sentence where the user “fills in the blanks.” Which gives us:

  • Payment: Send Amount to Contact from Debited Account for Reason

  • Request: Request Amount from Contact to Credited Account for Reason

Multiple Requests sent at once

Inspired by user interviews, we took this opportunity to add the ability to request and send to multiple users at once. Here’s how it works for requests : Imagine a user who paid for a round of beers for 3 friends at a bar: if they want to be reimbursed using Lydia's request feature, they shouldn’t have to repeat the exact same action 3 times in a row. So we had to account for this scenario without compromising the main use case: a single simple request.

Multiple Requests sent at once

Inspired by user interviews, we took this opportunity to add the ability to request and send to multiple users at once. Here’s how it works for requests : Imagine a user who paid for a round of beers for 3 friends at a bar: if they want to be reimbursed using Lydia's request feature, they shouldn’t have to repeat the exact same action 3 times in a row. So we had to account for this scenario without compromising the main use case: a single simple request.

Multiple Requests sent at once

Inspired by user interviews, we took this opportunity to add the ability to request and send to multiple users at once. Here’s how it works for requests : Imagine a user who paid for a round of beers for 3 friends at a bar: if they want to be reimbursed using Lydia's request feature, they shouldn’t have to repeat the exact same action 3 times in a row. So we had to account for this scenario without compromising the main use case: a single simple request.

We also displayed the total amount requested on the confirmation button to avoid confusion: Total amount = Requested amount × Number of contacts selected, and not Requested amount ÷ Number of contacts. This may seem obvious, but the division logic corresponds to a different use case.

Long-Click Interaction for Advanced Users

There was one remaining issue: our solution didn’t allow users to directly select multiple contacts before reaching the Summary view. This is a minor problem that concerns only a small number of users, but we still wanted to address it. So we opted for a more advanced behavior: the long-click. This is similar to what you do in the Gmail app to select multiple messages: You press and hold on an item until a checkmark appears. You can then select/deselect each item in the list (and, for example, mark them all as read or delete them). Since this interaction occurs at the very first step of the flow, it lets experienced users shortcut the process and achieve their goal more quickly. Limitation: This gesture is only meant for users already familiar with this advanced interaction pattern.

Long-Click Interaction for Advanced Users

There was one remaining issue: our solution didn’t allow users to directly select multiple contacts before reaching the Summary view. This is a minor problem that concerns only a small number of users, but we still wanted to address it. So we opted for a more advanced behavior: the long-click. This is similar to what you do in the Gmail app to select multiple messages: You press and hold on an item until a checkmark appears. You can then select/deselect each item in the list (and, for example, mark them all as read or delete them). Since this interaction occurs at the very first step of the flow, it lets experienced users shortcut the process and achieve their goal more quickly. Limitation: This gesture is only meant for users already familiar with this advanced interaction pattern.

Long-Click Interaction for Advanced Users

There was one remaining issue: our solution didn’t allow users to directly select multiple contacts before reaching the Summary view. This is a minor problem that concerns only a small number of users, but we still wanted to address it. So we opted for a more advanced behavior: the long-click. This is similar to what you do in the Gmail app to select multiple messages: You press and hold on an item until a checkmark appears. You can then select/deselect each item in the list (and, for example, mark them all as read or delete them). Since this interaction occurs at the very first step of the flow, it lets experienced users shortcut the process and achieve their goal more quickly. Limitation: This gesture is only meant for users already familiar with this advanced interaction pattern.

Adapting Impacted Sections & Tracking

The final part of the work involved listing all the impacts across the rest of the application:

Adapting Impacted Sections & Tracking

The final part of the work involved listing all the impacts across the rest of the application:

Adapting Impacted Sections & Tracking

The final part of the work involved listing all the impacts across the rest of the application:

  • Update the “Split the Bill” feature, to maintain visual and functional consistency with this neighboring feature.

  • Update the list of possible error messages for sending a multi-request: What happens if the error concerns all contacts? Or only one? This case is more complex than it seems in terms of development, as several types of errors are possible (with different back-end implications).

  • Create display rules for sent requests and their follow-ups or cancellations (for example, if a contact has already paid their share).

We also implemented a tracking plan to measure the effectiveness of this new feature and to decide—based on data—whether it should be kept, modified, or removed in the future. Among the tracked data:

  • Number of requests sent

  • Number of long-clicks performed

  • Nb of simultaneous requests sent vs. nb of identical requests sent one after another

  • Use of Multi-request vs. use of Split the Bill

Contact

Back to top

Copyright Maxime Lemoine © 2025

Created in Lyon

Linkedin

Instagram

Contact

Back to top

Copyright Maxime Lemoine © 2025

Created in Lyon

Linkedin

Instagram

Contact

Back to top

Copyright Maxime Lemoine © 2025

Created in Lyon

Linkedin

Instagram

Back

Back