Context

The growing demand for seamless payment solutions underscores the need for tools that empower both individuals and professionals to thrive in dynamic, social environments. QR codes provide an intuitive and accessible method to simplify transactions, removing unnecessary complexity and friction.

For those who don’t require the full flexibility of a cagnotte, the QR code feature offers a streamlined alternative for receiving funds. It is especially useful for street performers, small-scale artisans, or anyone providing services in a professional or semi-professional context, delivering a fast, simple, and transparent way to manage payments.

</aside>

<aside>

Purpose

To drive greater engagement, we aim to place QR codes at the heart of the user experience, making them frictionless and intuitive for P2P transactions and Money Pots.

P2P transactions are gradually declining, both on Lydia and Sumeria, presenting an opportunity to reposition the QR code experience as a core feature rather than a secondary one.

On the Money Pots side, the new fees policy has increased user expectations. We need to add features that bring more value to Money Pot owners, as current options fall short.

</aside>

Placements

<aside>

Money Pots

<aside>

Observations

Money pots are often tied to specific real-life events.
Owners face challenges keeping contributors informed and engaged.

Possible Solutions

Add a dedicated QR code.
Make the QR code easily shareable and printable.

Expectations

Increase Money Pots adoption. (”money_pots_withdrawed_destination”) iOS
Increase revenue from Money Pots. (”money_pots_withdrawed_social_wallet”) iOS </aside>

</aside>

<aside>

Lydia Account

<aside>

Why for Lydia account and not Lydia wallet

Simplifies user understanding: one personal QR code per Lydia account, no overthinking.
Currently, personal QR codes could redirect scanners to a prefilled summary view. In the future, they could redirect to user profiles, enabling scalability towards social features.
Lydia Wallet should evolve to become more intuitive with less interactions. With auto-forward and top-up features, the Lydia wallet could eventually operate seamlessly: funds are automatically used for payments, and remaining balances are transferred to the user’s bank account daily.

Observations

Receivers lack an easy way to initiate transactions beyond the “Request” flow.

Possible Solutions

Add a unique QR code linked to the Lydia account.
Enable prefilled summary views.
Develop a Universal QR Code (App : free, Web: CB form).

Expectations

Increase overall P2P transaction volume. (”send_P2P_confirmed” and “payment_request_state”)
Increase “Scan” feature adoption. Undefined
Reduce median time in the summary view. (”summary_view_opened”) Clean properties
Reduce delays between requests and payments. (”payment_request_state” </aside>

</aside>

<aside>

P2P

<aside>

Exploratory Analysis

Summary view is the most accessed feature
Unexplored post-entry behaviors
Completion time inconsistencies
Underutilized payment requests
Our power users
Significant user inactivity
Misaligned payment request timing </aside>

<aside>

Summary QR

Observations

The “Request” feature is 18 times less used than “Send,” suggesting a need for design enhancements.
The “Scan” feature is buried within the “Request” flow, making it hard to access or discover.
Significant delays exist between when requests are sent and payments are made, highlighting room for improvements.

Possible Solutions

Unify behaviors between “Request” and “Send” by generating a QR code for both.
Add “Scan” as a quick action.
Introduce a widget for faster “Scan” access.
Develop a Universal QR Code (App : free, Web: CB/IBAN form).

Expectations

Increase overall P2P transaction volume. (”send_P2P_confirmed” and “payment_request_state”)
Increase “Request” feature adoption. (”payment_request_state”)
Reduce median time in the summary view. (”summary_view_opened”) Clean properties
Reduce delays between requests and payments. (”payment_request_state”)

</aside>