Portfolio / Hue Case study

Desktop eCommerce B2C 0→1 Product Digital Payments International Rollout

When a Feature becomes a Financial System

What started as "just add gift cards" became an eight-month deep dive into fraud prevention, cross-border compliance, and the invisible rules that make digital value systems work.

My role
Lead Product Designer
Timeline
8 months
Team
3 product designers, 1 scrum master, 4 engineers
Tools
Figma, Confluence

The brief

Philips Hue had no gift card infrastructure despite operating in a mature global eCommerce environment. This is how we built it from scratch.


From Feature to Financial System

The project started with what seemed like a straightforward request: Digital gift cards to the eCommerce platform. There was even a Magento plugin available as a baseline. The assumption was simple: this would be “just another PDP”.

But as I began exploring the requirements, benchmarking competitors, and mapping the full lifecycle of a gift card, it became clear that we weren’t designing a product page. We were introducing a financial instrument into a global ecosystem.

Very quickly, the scope expanded beyond UI decisions. Over fifty possible card configurations surfaced. Cross-border gifting raised taxation and currency concerns. Fraud scenarios emerged. Questions around liability accumulation, refund abuse, and gift-card-to-gift-card purchases required legal clarity.

What initially looked like a feature became a system of interdependent rules. Development feedback further exposed the structural weight of each decision. What sounded like “just a conditional” often implied architectural implications within checkout. The conversation shifted from screens to safeguards.

At that point, the real challenge became clear: defining boundaries. Instead of pushing for a fast MVP, I prioritized establishing financial and legal guardrails. This meant introducing purchase limits, preventing circular transactions, structuring redemption logic carefully, and advocating for a voucher-layer integration within checkout rather than a simple payment-method implementation.

It also meant thinking about digital stock as finite because unlimited code generation implies unlimited financial exposure. The initiative stopped being about adding a new feature. It became about designing a controlled digital value system that could scale globally without compromising compliance or operational integrity.

🔴 Problems found

Stored value introduced financial liability, fraud exposure, cross-border taxation challenges, and checkout architecture constraints: transforming a simple feature into a systemic challenge.

🟢 Our approach

I defined clear financial and structural guardrails, prioritizing long-term control and scalability over speed-to-market.


Buyer and Recipient Flows made in FigJam




How we got there

01

Mapping the system

Mapped the complete lifecycle of a gift card: from purchase and delivery to redemption and balance management, ensuring the system behaved consistently across markets.

02

Benchmarking beyond the industry

Conducted extensive benchmarking across competitors and other digital platforms offering stored value to understand best practices around gifting, fraud prevention, and discoverability.

03

Structuring edge cases

Identified and documented critical edge cases, including cross-border gifting, payment-provider constraints, partial redemptions, and guest balance management.

04

Designing a dual user journey

Designed the end-to-end experience for both buyers and recipients, structuring the journey to keep complex rules invisible while maintaining clarity and trust throughout the gifting and redemption process.

05

Aligning cross-functional teams

Collaborated closely with business, legal, and engineering teams to translate systemic constraints into a scalable and compliant experience.

PDP and Checkout screens




What I learned

Designing digital value systems means defining boundaries before designing screens. What initially looked like edge cases quickly revealed the real complexity of the product.

This project reinforced that great UX often comes from making complex systems feel effortless, even when the work behind the scenes is anything but. Sometimes the real design challenge isn't creating features, but protecting the system behind them.

Next project

🍜 Ninja App

View case study →