A multi-role product becomes confusing quickly when the same transaction looks different to each participant. While building QwickPe, an Android technology marketplace for eligible card-linked shopping offers in India, we learned that clarity matters more than feature density.

This post shares the product-design principles behind separating Buyer and Cardholder journeys. It is not financial advice, and it does not promise that an offer, saving, earning, or settlement will be available for every transaction.

1. Start with the user’s role

The first screen should answer one question: What am I here to do?

A Buyer needs to:

discover a supported shopping journey;

review the live offer and transaction amount;

follow the payment route shown in the app;

track the matched deal, order, return, or refund status.

An eligible Cardholder needs to:

review a matched request and disclosed earning;

decide whether to participate;

complete the supported merchant checkout;

provide the requested order…