Business wallets & cards for e-commerce teams

Incard is an MVP fintech product that gives e-commerce merchants multi-currency business wallets, virtual cards per campaign, and simple reconciliation tools. The goal was to validate demand for a lightweight business wallet that makes ad spend tracking and cross-border receipts far easier for merchants.

‍Role:  Product Designer
Team: PM, Lead Engineer, Backend Engineer, UX Researcher
Timeline: 10–12 weeks (MVP sprint)

Merchants were losing time and margin managing multiple currency receipts, ad spend cards and bookkeeping. Finance teams relied on manual CSVs and messy card receipts; ad teams wanted per-campaign spend control. The business goal was clear: launch an MVP that proves demand and removes the bookkeeping friction preventing adoption.

‍Success metrics: merchant activation, $ processed, monthly active merchants (MAU), and time-to-reconcile.

We ran a focused, outcome-driven design sprint:

Discovery & research: competitor audit (Wise Business, Revolut, Stripe Issuing), surveys (≈220 responses) and 18 moderated merchant interviews.

Design & iterate: low-fi flows → interactive prototypes → usability testing (n≈10) → high-fi UI.

We prioritized the minimum feature set that would unlock value: multi-currency wallets, per-campaign virtual cards, and one-click reconciliation exports (CSV + Xero mapping).

Per-card campaign model - allow merchants to create virtual cards for each campaign or vendor. This made spend segmentation visible immediately and removed the need for manual tagging in bookkeeping.

Staged onboarding - merchants could create wallets and explore the product before full verification; verification was required only to issue cards, lowering initial friction.

Reconciliation-first UX - put exports and Xero mapping front-and-center so finance teams could evaluate time savings immediately.We rejected a full banking UX (loans/deposits) for the MVP because it would have delayed launch and required heavy compliance work.

Deliverables included: Figma prototypes and interactive flows for web and mobile.
Component library and design tokens (color, spacing, typography).
Developer handoff docs with acceptance criteria and React component specs.

Design handoff allowed the engineering team to implement iterative releases while we onboarded pilot merchants.