# CS-52: Understanding UPI autopay mandates

Category: Money & financial tools
Level: Beginner
Suggested duration: 2–3 weeks

Original UXCharan practice scenario. Validate assumptions; do not present it as a commissioned client project.

## Problem
A fictional payments app lets users approve autopay mandates for subscriptions, but many people don't know what they agreed to or how to stop it. Explore how to make active mandates, upcoming debits and cancellation clear and trustworthy.

## People to learn from
First-time UPI users who set up subscriptions or EMI autopay

## Core scope
- See active mandates
- understand the next debit
- pause or cancel a mandate

## Research questions
- How do people remember what they have set up for autopay?
- What would make them confident a cancellation worked?

## Edge cases
- Debit amount higher than expected
- mandate set up by mistake
- merchant name unclear

## Specific artefact
An upcoming-payments timeline with clear amounts and dates

## Evaluation question
Can users find, understand and cancel an unwanted mandate without help?

## Work to share
Problem and role; anonymised evidence; alternatives and rationale; task flow; prototype; accessibility considerations; testing findings; revisions and honest limitations.

## Request feedback
Share a viewable Figma, document or portfolio link with Saicharan on WhatsApp: https://wa.me/917093809350
Include CS-52, your name, project stage and your main feedback question. Confirm review scope, timing and any fee directly.

## Methods
- Research planning: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service
- Research consent: https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research
- Design exploration: https://www.designcouncil.org.uk/resources/the-double-diamond/
- Usability testing: https://www.nngroup.com/articles/usability-testing-101/
- Accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Portfolio storytelling: https://www.nngroup.com/articles/ux-design-portfolios/