# CS-08: Payment status and recovery

Category: Money & financial tools
Level: Intermediate
Suggested duration: 3–4 weeks

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

## Problem
A fictional payment prototype shows a generic error after confirmation. Investigate how a person could understand pending, failed and completed states and seek help without accidentally repeating a payment.

## People to learn from
People checking an uncertain digital payment

## Core scope
- Check status
- inspect a receipt
- request help

## Research questions
- What evidence makes a status believable?
- When would someone retry a payment?

## Edge cases
- Delayed confirmation
- duplicate attempt

## Specific artefact
A payment-state map and support handoff

## Evaluation question
Can participants choose the next step without an unnecessary retry?

## 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-08, 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/