UNIT 1
Fin-Tech Product Design: The
App That Worked… But
Confused
Welcome to this exploration of Fin-Tech product design and user experience. Through a
real-world case study, we'll examine how digital payment apps function, where user
experience can break down, and why understanding matters as much as technology. This
journey will reveal the delicate balance between speed, functionality, and user trust in
financial technology.
Stage 0: The Incident
The Case Trigger
"Everyone Uses
The Critical Moment: On her first attempt to
It… So Why Am I
pay at a café, the app displays "Payment
Struggling?"
Pending." Money is debited from her bank
Meet Riya Mehta, a 24-year-old account, but the merchant confirms they
postgraduate student navigating haven't received it. What should have been
her first digital payment experience. simple has become stressful.
After persistent encouragement
from friends who insist "Just use the
app, it's very simple," she
downloads a popular Fin-Tech
payment application.
The setup seems straightforward:
she completes registration, links her
bank account, and feels ready for
the convenience everyone
promised.
Stage 0: Investigating the Incident
1 2 3
What Was Riya's Expectation? Why Is This Stressful for First- Technology Failure or
Time Users? Experience Failure?
Riya expected an instant, seamless digital
payment experience. Based on her friends' For a first-time user, uncertainty about This question lies at the heart of Fin-Tech
recommendations and the app's marketing money creates immediate anxiety. The design. While the underlying technology may
promises, she anticipated a transaction that "pending" status offers no clarity about eventually work correctly, the user
would be faster and simpler than cash or whether the payment succeeded, failed, or is experience has already failed. The lack of
card payments. The expectation was clear: still processing. Meanwhile, real money has clear communication, reassurance, and
tap, confirm, done. left her account, and the merchant is guidance during an uncertain moment
waiting. This ambiguity transforms a simple represents an experience failure, even if the
transaction into a crisis of confidence. technology ultimately processes the
payment.
Stage 0: Initial Conclusions
Expected Simplicity Created Uncertainty
Riya's expectation was reasonable: The incident immediately created
instant, simple digital payment that uncertainty and anxiety. Without clear
removes friction from everyday information about what "pending"
transactions. This expectation was means or when resolution will occur,
shaped by marketing messages and Riya is left in an uncomfortable limbo
peer recommendations that with her money.
emphasized ease of use.
Shaken Confidence
The first Fin-Tech interaction has already damaged confidence. This initial experience
will color all future interactions with the app, making Riya more cautious and
skeptical even after the issue resolves.
Stage 0: Early Learnings
First Impressions Matter Deeply
Key Jargons Introduced
In Fin-Tech, first impressions carry extraordinary weight. Users are
• Fin-Tech App: A technology-enabled financial service that
entrusting their money—one of their most sensitive concerns—to a
uses digital platforms to deliver banking, payment, or
digital system. A negative first experience can create lasting
investment functionality
hesitation, even if subsequent interactions work perfectly.
• Digital Payment: The electronic transfer of money from one
account to another, eliminating the need for physical cash
or cards
Speed Without Clarity Creates Distrust
Fast processing is valuable, but not at the expense of Next, we examine how the app actually operates behind the scenes.
understanding. When speed prioritizes transaction completion
over user comprehension, the result is confusion and anxiety rather
than satisfaction and confidence.
Stage 1: Fin-Tech Ecosystem in Action
Evidence 1: Understanding Payment Flow
When Riya explores the app's support pages looking for answers, she discovers an explanation of how
payments actually work. The reality is far more complex than the simple interface suggests.
User's Bank
The source of funds where Riya's money is held
Payment Network
UPI infrastructure that routes the transaction
Merchant's Bank
The destination where payment should arrive
The app itself is just the interface. Behind that simple "pay now" button, multiple systems must
communicate and coordinate in real-time. Multiple systems are involved in one payment—and each
represents a potential point of delay or failure.
Stage 1: Investigating the Ecosystem
1 2 3
Is the App Acting Alone? Why Does Fin-Tech Depend on Where Can Delays Occur?
Multiple Players?
No. The app is merely the visible interface Delays can happen at any connection point:
layer. Behind it, a complex network of banks, Financial transactions require multiple bank processing times, network congestion,
payment processors, and regulatory systems parties for security, regulation, and merchant system responsiveness, or
must work in concert. The app initiates the infrastructure. Banks hold actual funds, communication failures between systems.
transaction but depends entirely on these payment networks provide the routing Even when all components function
backend systems to complete it. infrastructure, and regulatory bodies ensure correctly, synchronization issues can create
compliance. This distribution prevents any "pending" states that confuse users.
single point of control and builds in
safeguards, but also creates dependencies.
Stage 1: Ecosystem Conclusions
Ecosystem Systemic Front-End vs.
Dependency Vulnerability System
Fin-Tech apps operate Failure or delay in any The app is a front-end
within a broader layer of this ecosystem interface, not the entire
ecosystem of affects the entire system. This distinction is
interconnected entities. transaction. A slow crucial: users interact
No app functions in response from a bank, with the app, but the
isolation—each relies on network congestion, or a actual work happens
banking infrastructure, merchant system issue across multiple systems
payment networks, and can all manifest as that the app merely
regulatory frameworks problems in the app, even coordinates.
that exist outside its when the app itself works
direct control. perfectly.
Stage 1: Ecosystem Learnings
Front-End Simplification Ecosystem Understanding
Fin-Tech apps excel at simplifying the front-end interface, creating the Understanding the ecosystem explains many user-facing issues. When users and
appearance of simplicity. However, this doesn't simplify the backend designers comprehend that multiple independent systems must coordinate,
complexity—it merely hides it from view. The underlying infrastructure remains "pending" states and delays become more understandable. This knowledge is
complex, with all its dependencies and potential failure points. essential for creating realistic expectations and better communication.
Key Jargons: The Technical Foundation
• Ecosystem: A network of connected entities that work together to deliver a service, where each component depends on others
• Payment Network: The system infrastructure enabling transfers between different banks and financial institutions (like UPI, VISA, or Mastercard)
• API (Application Programming Interface): The system connector that allows different software applications to communicate and share data
Now we explore how users are onboarded into this complex system and what they actually understand about their consent.
Stage 2: Onboarding & User Understanding
Evidence 2: The Registration Journey
During her registration process, Riya moved through several critical steps quickly. Like many users, she
was focused on completing the setup rather than deeply understanding each permission or agreement.
01
Granted App Permissions
Access to contacts, SMS, and phone state
02
Linked Bank Account
Verified via OTP from her bank
03
Accepted Terms
Scrolled and clicked "I agree" without reading
"I didn't really know what I was agreeing to. I just wanted to start using the app
like my friends."
— Riya's honest reflection
Stage 2: Investigating Onboarding
Was Riya Adequately Informed? Is Consent Meaningful If Not Who Bears Responsibility for
Understood? User Education?
Technically, information was presented:
permission dialogs explained access needs, This raises a fundamental ethical question in The responsibility is shared but weighted
terms of service outlined responsibilities, Fin-Tech design. Legal consent requires toward the service provider. While users
and OTP processes were standard. However, agreement, but meaningful consent requires should take time to understand what they're
"presented" doesn't equal "understood." The comprehension. When users click "I agree" agreeing to, Fin-Tech companies must
volume of information, legal language, and without reading or understanding terms, design onboarding that encourages and
pressure to complete setup quickly all they've provided legal consent but not enables understanding. Simply providing
worked against genuine comprehension. informed consent. The gap between these dense legal documents doesn't fulfill an
Riya received data but not understanding. two types of consent creates vulnerability educational responsibility. The design itself
and potential for future conflict. must teach, not just inform.
Stage 2: Onboarding Conclusions
1 Technical Consent Obtained
From a legal and technical standpoint, consent was properly obtained. Riya
clicked the necessary buttons, verified her identity, and completed all
required steps. The company can demonstrate that she agreed to terms and
granted permissions.
2 Understanding Was Minimal
Despite technical compliance, Riya's actual understanding was extremely
limited. She doesn't know what data the app can access, what rights she's
granted, or what protections she has. The consent was procedural, not
meaningful.
3 Speed Over Clarity
The onboarding design prioritized speed of completion over depth of
understanding. This choice optimizes for user acquisition metrics but
potentially undermines long-term trust and appropriate usage.
Stage 2: Onboarding Learnings
The Speed-Comprehension Informed Usage Drives Success
Tradeoff
Fin-Tech success depends on informed usage, not just
Fast onboarding reduces friction and increases adoption. Users who understand how systems work,
conversion rates—metrics that businesses prioritize. what can go wrong, and what protections exist become
However, speed can reduce comprehension, leaving more confident and resilient when issues occur. They're
users unprepared for problems when they arise. When also more likely to use features appropriately and
Riya encountered the payment issue, she had no maintain long-term engagement.
framework for understanding what went wrong because
her onboarding focused on "getting started" rather than Key Jargons: The User Journey
"understanding how this works."
• Onboarding: The first-time user setup
and introduction process designed to
help users begin using a product
effectively
• Consent: User permission granted for
specific data access or actions, ideally
informed and voluntary
• OTP (One-Time Password): A temporary
security code sent via SMS or app to
verify user identity
Next, we examine what happens when users need help and how customer support shapes the experience.
Stage 3: Customer Support &
Experience
Evidence 3: When Users Need Help
Stressed and confused about her pending payment, Riya turns to the app's customer support feature.
Her journey through the support system reveals critical gaps in how Fin-Tech companies communicate
with users during moments of crisis.
Opened In-App Chat
Navigated to the support section and initiated a chat, hoping for quick clarification about her
pending payment and missing money.
Received Automated Responses
The chatbot offered pre-programmed answers that addressed generic scenarios but
didn't speak to her specific anxiety and confusion.
Got Standard Message
"If amount is debited, it will be reversed within 48 hours." This procedural information
answered the "when" but completely ignored the "why" and "what."
Stage 3: Investigating Support Quality
Is This Response Reassuring? What's Missing from This How Does This Impact Trust?
Interaction?
The 48-hour reversal promise provides some Rather than building trust through
relief—Riya will get her money back. Several critical elements are absent: an transparency and education, this
However, reassurance requires more than explanation of why the payment is pending, interaction potentially erodes it. Riya learns
procedural information. It requires what "pending" actually means in technical that the system will fix the problem, but she
acknowledgment of the user's confusion, terms, how the money is currently held, doesn't learn how the system works or why
explanation of what happened, and context what caused this particular instance, and it failed. This leaves her feeling that the
for understanding the situation. The how Riya might avoid similar situations in system is unreliable but unavoidable—a
response treats the symptom (her concern the future. The support provides a process- relationship of dependence rather than
about money) but ignores the disease (her oriented answer without educational confidence. Future problems will trigger the
lack of understanding). context or empathy for her first-time user same anxiety because she still lacks
confusion. understanding.
Stage 3: Customer Experience
Conclusions
Process vs. Clarity Anxiety Amplification
The app provided process Without explanation, the support interaction actually
information—what will happen and increased Riya's anxiety rather than reducing it. She now
when—but failed to provide knows she'll wait 48 hours, but she doesn't know why
clarity—why it happened and what she's waiting or whether this will happen again. The lack
it means. This distinction is crucial of explanation leaves her feeling powerless and
in customer support design. concerned about future transactions.
System vs. Experience
This case illustrates a critical truth: customer experience
failed even though the system works correctly. The
money will be reversed, the technical process will
complete successfully, but Riya's experience has been
negative. CX encompasses more than functional
outcomes—it includes understanding, communication,
and emotional response.
Stage 3: Customer Experience Learnings
Communication Over Automation Explaining Failures Clearly
Customer experience is about meaningful communication, not automation Fin-Tech must explain failures clearly and comprehensively. When money is
alone. Automated support can handle volume efficiently, but it often fails at involved, users need to understand not just the resolution process but also
the human elements: empathy, context-appropriate explanation, and the root cause, the safeguards in place, and how to interpret system states.
educational dialogue. The goal shouldn't be to automate support, but to Clear failure communication transforms anxious users into informed users
automate the right support—support that educates and reassures, not just who trust the system more, not less, because they understand its
processes. boundaries and recovery mechanisms.
Key Jargons: Support and Experience
• CX (Customer Experience): The overall user perception and emotional response resulting from all interactions with a product or service
• Automated Support: Bot-based assistance systems that provide responses without human intervention, optimized for efficiency over
personalization
Now we consider how trust develops in regulated Fin-Tech environments and what users should understand about protection.
Stage 4: Trust, Regulation &
Responsibility
Evidence 4: The Role of Regulatory Safeguards
Searching for reassurance, Riya explores the app's "About" and "Safety" sections. She finds several
statements about regulation and protection that should inspire confidence but instead raise new
questions.
Regulated by RBI "If it's regulated, why does this still
happen?"
The Reserve Bank of India oversees operations and
enforces compliance with banking and payment — Riya's reasonable question
regulations.
Follows Payment Guidelines
Adheres to established protocols for transaction
processing, security, and dispute resolution.
Customer Funds Protected
Multiple safeguards ensure that user money is secure and
recoverable in case of issues.
Stage 4: Investigating Regulation
1 2 3
What Does Regulation Actually Does Regulation Eliminate All How Should This Be
Guarantee? Failures? Communicated?
Regulation provides oversight, No. Regulation cannot prevent every Users need realistic expectations about what
accountability frameworks, and recourse technical glitch, network delay, or system regulation protects. Communication should
mechanisms. It ensures that companies interaction issue. Digital systems are clarify that regulation ensures safety and
follow established standards, maintain complex and involve multiple independent recourse, not perfection. Apps should
proper security, handle funds appropriately, parties. What regulation does is ensure that explain: what protections exist, how users
and provide channels for dispute resolution. when failures occur, there are proper can access recourse mechanisms, what
However, regulation doesn't guarantee processes for resolution, that user funds are timeframes to expect for resolutions, and
perfection or eliminate all technical issues. It ultimately protected, and that companies how to distinguish between normal technical
creates safety nets and consequences, not are held accountable for systemic problems. issues and serious problems. Transparency
infallibility. Regulation manages failure consequences about regulatory boundaries builds
rather than eliminating failure possibilities. informed trust rather than false confidence.
Stage 4: Regulation Conclusions
Digital System Failures
Failures can still occur in even well-regulated
digital systems. The complexity of
interconnected services, network
Safety & Recourse dependencies, and real-time processing
Regulation ensures safety mechanisms and creates inherent possibilities for delays,
recourse channels, not elimination of all pending states, and occasional errors.
problems. When issues occur, regulated
systems provide clear paths to resolution and Regulatory Boundaries
protect user interests through established Users must understand regulatory
frameworks. boundaries—what is and isn't guaranteed. This
understanding prevents false expectations and
builds realistic confidence in system
protections and recovery mechanisms.
Stage 4: Trust and Regulation Learnings
Confidence Through Compliance Trust Through Transparency
Regulation builds confidence, not convenience. While Trust grows through transparency about both
users might wish regulation meant "everything always capabilities and limitations. When Fin-Tech companies
works perfectly," its actual value is in ensuring clearly communicate what regulation protects, how
accountability, proper security practices, and reliable systems can fail, and what safeguards exist, users
dispute resolution. This more modest but realistic develop informed trust—a more resilient form of
promise actually provides stronger long-term confidence confidence than blind trust based on marketing
than false guarantees of perfection. promises.
Key Jargons: Regulatory
Framework
• Regulator: A government authority (like
the RBI) that oversees financial service
operations, enforces rules, and ensures
consumer protection
• Compliance: Adherence to regulatory
rules, standards, and guidelines that
govern how financial services must
operate
Finally, we reflect on how this experience affects Riya's perception and future Fin-Tech adoption decisions.
Stage 5: User Perception & Adoption
Evidence 5: The Aftermath
Two days later, Riya's money is reversed to her account. The system worked as promised. The technical
issue resolved correctly. Yet her relationship with the app has fundamentally changed.
"The app works… but I'm still hesitant Behavior Changes
to use it again."
Kept the App Installed
— Riya's telling reflection
She didn't delete it—recognition that it may be
necessary or useful in certain situations.
Avoids Large Payments
She now limits usage to small transactions
where potential problems feel less risky and
stressful.
Maintains Alternatives
She continues carrying cash and cards as
backup, unwilling to rely fully on the digital
payment app.
Stage 5: Investigating Adoption Barriers
Has the Fin-Tech Solution Failed Technically?
No. From a technical standpoint, the system performed correctly. The payment processed through
the complex ecosystem, encountered a temporary issue (which happens in distributed systems),
and resolved through established protocols. The money was protected and returned. By technical
measures, this represents a success—the safeguards worked.
Why Is Adoption Now Cautious?
Adoption has become cautious because the experience damaged Riya's confidence, even though
the technology ultimately worked. She experienced stress, confusion, and lack of control during her
first use. These emotional and psychological factors now outweigh the rational knowledge that the
system eventually resolved the issue. The gap between technical success and user confidence
reveals adoption depends on experience, not just functionality.
What Could Improve Future Confidence?
Several factors could rebuild confidence: clearer explanation of what "pending" means and why it
occurs, proactive communication during transaction processing, educational content about how
the ecosystem works, transparent indicators of transaction status, and support that teaches rather
than just processes. Most importantly, acknowledging the confusing experience and demonstrating
that the company understands and is addressing communication gaps would show that user
experience matters as much as technical functionality.
Stage 5: Adoption Conclusions
Technical Success 1
The system worked eventually.
Money was protected, the
transaction resolved correctly 2 Experience Damage
through established protocols, and
all technical safeguards functioned The experience damaged confidence
as designed. By infrastructure through lack of clarity, inadequate
standards, this represents proper communication, and failure to
operation. address user anxiety. These
experience failures outweigh
technical success in determining user
Trust Dependency 3
perception and future behavior.
Adoption depends on trust, not just
functionality. Users must feel
confident, informed, and in control—
not just assured that systems will
eventually work. Trust is emotional
and experiential, not merely
technical.
Stage 5: Final Adoption Learnings
Emotional Dimensions of Adoption Clarity as Competitive Advantage
Fin-Tech adoption is emotional as well as functional. Users must not only believe the system works but also feel comfortable, Clarity converts users into advocates. When users understand how systems work, why issues occur, and what protections exist,
confident, and empowered when using it. Technical reliability is necessary but insufficient for driving sustained adoption. they become resilient during problems and enthusiastic in recommendations. They can explain to others, contextualize
difficulties, and maintain confidence through challenges.
Conversely, confusion creates hesitant users who may continue using a service but won't champion it. They become users by
necessity rather than choice—a weak foundation for long-term growth.
Key Jargons: Long-Term Success
• Adoption: Continued usage and integration of a technology into regular behavior patterns, indicating true
acceptance and value perception
• Trust: User confidence in system behavior, based on understanding, reliability, and positive experiences over
time
Final Closure: Unit 1 Synthesis
The Complete Picture
Understanding
1
2 Technology
3 Simplification
Fin-Tech Simplifies Finance Technology Enables Speed Understanding Enables Trust
At its foundation, Fin-Tech removes friction Digital infrastructure enables unprecedented Understanding enables trust—the critical
from financial services, making complex transaction speed and convenience. What once insight that separates successful Fin-Tech from
banking operations accessible through simple required bank visits and paperwork now merely functional Fin-Tech. Speed and
interfaces. This simplification has democratized happens in seconds through smartphone apps. simplicity attract users, but understanding
financial access. sustains adoption.
Final Takeaway: When Imperfection Matters Most
Success in Imperfection
Through Riya's journey, we've discovered a profound truth about Fin-Tech product design:
Fin-Tech succeeds not when apps work perfectly, but when users understand what is happening when they don't.
Perfect systems don't exist. Technical issues will occur—pending states, delayed transactions, network problems, and system communications challenges are inherent to complex distributed systems. The
question isn't whether problems will happen, but how users experience and interpret them when they do.
3 1 5
Touchpoints Core Insight Key Stages
Where experience failed: onboarding, incident handling, and Understanding matters more than perfection in building lasting From incident through ecosystem, onboarding, support, regulation,
support communication user confidence to adoption
The most successful Fin-Tech products will be those that educate, communicate clearly, and build understanding alongside functionality. They'll transform moments of technical imperfection into opportunities
for building resilient, informed trust. This is the future of user-centered Fin-Tech design.
Thank you for engaging with this case study. May your designs always prioritize understanding alongside innovation.