Gaia

Automatic digital receipts and smart reminders powered by secure transaction data

Role

UX Researcher · Systems Designer · Product Designer

Industry

Sustainability · FinTech · Retail Systems

Duration

10 Weeks

Rethinking Receipts as Infrastructure

Gaia began with a simple observation. Receipts are treated as disposable artifacts, yet they contain structured financial information that users repeatedly need.

I reframed receipts not as paper outputs, but as financial data events that could be captured, organized, and extended into long-term value.

The ambition was not to design a cleaner receipt app.
It was to design a system that works quietly in the background.

Remove friction. Preserve trust. Make sustainability invisible but measurable.

Understanding Waste, Trust, and Fragmentation

To validate the opportunity, I surveyed 44 participants and conducted interviews across students, professionals, and small business owners.

A clear contradiction emerged.

• 94 percent discard paper receipts immediately.
• Only 25 percent knew thermal receipts are not recyclable.
• 95 percent would adopt an automatic system if it worked seamlessly and securely.

The barrier was not digital adoption. It was fragmentation and broken trust.

Participants described losing warranty records, missing renewals, searching inboxes for proof of purchase, and feeling uneasy about spam.

The real issue was cognitive load.

Defining the System Principles

Research clarified that users value trust, automation, and clarity. Privacy and simplicity were prerequisites, not features.

This led to three guiding principles.

Zero Effort Capture

Receipts should be generated automatically without behavioral change.

Instead of relying on NFC or email forwarding, Gaia integrates directly with banks and card networks to retrieve secure transaction metadata in real time. This positions receipt generation at the infrastructure layer rather than the checkout interface.

Privacy by Architecture

Participants were skeptical of inbox-based solutions.

Gaia eliminates email dependency. Receipts are generated securely and stored on device, synchronized only with explicit user permission. The system organizes existing financial data without creating additional tracking layers.

Trust is reinforced through structural decisions.

Meaningful Feedback

Users were interested in environmental impact only if it felt grounded.

Gaia translates digital receipt adoption into measurable indicators such as paper saved and CO2 prevented. Sustainability becomes a passive outcome of better system design.

Improving Clarity and Legitimacy

Usability sessions revealed that early versions of the receipts view felt dense and visually heavy.

Rather than redesigning the concept, I refined the information hierarchy and recognition cues.

I introduced:

• Merchant recognition signals
• Clearer transaction grouping
• Stronger structural alignment with familiar receipt formats

These changes increased perceived financial legitimacy and reduced hesitation when reviewing transaction data.

Iteration focused on removing ambiguity, not adding complexity.

Extending the System

Once core clarity was established, I expanded Gaia into two intelligence layers.

Contextual Reminders

By analyzing transaction metadata, Gaia identifies purchases that include warranties, subscriptions, or registration deadlines. The system schedules reminders before expiration.

This transforms static purchase data into time-sensitive support.

The lock screen notification demonstrates how the system integrates beyond the app interface, becoming part of everyday device interaction.

Environmental Insights

Eco Insights visualizes aggregated environmental impact over time. The emphasis is not on gamification. It is calm accountability.

Impact becomes visible without demanding attention.

Expanding Beyond NFC

The initial concept explored NFC-based automation at checkout. As I mapped payment infrastructure more deeply, I recognized that retailer-dependent solutions would limit scalability.

I shifted the architecture toward direct bank and card network integrations.

This shift introduced real-world constraints. Financial integrations require regulatory compliance, secure API partnerships, and standardized transaction schemas across institutions. Scalability depends not only on design decisions, but on ecosystem alignment.

This enabled:

• Compatibility across payment types
• Independence from merchant-level implementation
• Integration at the financial infrastructure layer

Reframing Gaia as a financial data layer strengthened its long term viability.

The opportunity is not a receipt app.
It is a receipt network embedded within existing financial ecosystems.

Designing for Invisible Convenience

Gaia strengthened my perspective on system-level product design.

I learned that real convenience often means invisibility. Users do not want better tools to manage receipts. They want receipts to manage themselves.

The most impactful products remove friction at the infrastructure layer rather than adding surface-level features.

Designing Gaia pushed me to think beyond interface polish and toward scalable, integrated systems that automate quietly and build trust through clarity.

A version of the concept prototype can be accessed here:

Gaia_Prototype