cardmeleon · concept
Virtual Cards
Giving users more control over subscriptions through flexible virtual cards.
01 — The problem
One card was being asked to do too much
Managing subscriptions across multiple services meant repeatedly sharing and storing the same payment credentials across different platforms.
Users had limited control over how individual merchants could charge them, making recurring payments harder to manage independently.
The opportunity was to give users more granular control over where, when, and how much could be charged.
02 — the product vision
A virtual card for each spending need
The product was designed around flexible virtual cards that could be created for either recurring subscriptions or one-time purchases.
Users could:
Create dedicated virtual cards
Set spending limits
Define payment schedules
Review transactions
Manage or update cards as their needs changed
The goal was to turn the card itself into a control layer between the user and each expense.
03 — The constraints
Designing Nanopay’s first customer-facing product
Nanopay’s existing expertise was primarily in backend financial infrastructure, making Cardmeleon its first significant customer-facing application.
That meant close collaboration with Engineering was especially important as we translated new interaction patterns and UI requirements into the product.
At the same time, the experience depended on finding a card provider that could support the required functionality—a constraint that ultimately prevented the product from launching.
04 — the solution
More control at the card level
I designed the experience around making individual virtual cards easy to create, understand, and manage.
Each card could represent a specific subscription or spending purpose, allowing users to separate expenses rather than relying on a single payment credential across every service.
The experience brought together:
Card creation and controls
Spending limits and schedules
Transaction visibility
Subscription and expense management
A dashboard for understanding activity across cards
The product direction focused on giving users clear, direct control without adding unnecessary financial complexity.
Card-level control across subscriptions and expenses
Virtual cards, spending controls, transaction visibility, and account management brought into one experience.
05 — branding
Building a consumer identity around flexibility
Because Cardmeleon was nanopay’s first customer-facing product, the work also required a distinct consumer brand.
I created the Cardmeleon name by combining card and chameleon, using adaptability as the central brand idea.
That concept informed the logo, visual identity, and flexible color system—giving individual cards their own personality while keeping the overall product cohesive.
The branding became a supporting layer of the product rather than a separate exercise: the visual system reinforced the idea that each card could adapt to a different purpose.
From card + chameleon to Cardmeleon
The identity combined the adaptability of a chameleon with the form of a payment card.
A flexible visual system for a flexible card product
Neutral foundations allowed individual cards and subscription categories to take on distinct visual identities.
Extending the identity beyond the product
Early marketing explorations carried the adaptable visual language into launch concepts.
06 — design outcome
A complete product foundation, despite an unreleased launch
Cardmeleon established the product and design foundation for a new type of customer-facing experience at nanopay, spanning product flows, card management, dashboard patterns, design system, and brand identity.
Although the product did not launch because the required card-provider partnership could not move forward, the work demonstrated how nanopay’s financial infrastructure could translate into a more approachable consumer experience.
Key Insight
Giving users more control didn’t require adding more financial tools—it meant making each payment relationship easier to isolate and manage.