03 / Alpe · Payments · 2022Financial product · Product design

Make money move visibly.

A financial ecosystem that turned balances, receivables and anticipation into a legible daily product.

Architecture · Interaction · Components · Motion

Explore ↓

01 / Product craft

One balance. Every state.

The interface made availability, alerts and completed actions readable at a glance before exposing operational detail.

Alpe home showing total balance and financial products
Balance as the anchor
Alpe home showing available receivables
Availability in context
Alpe home showing a product alert state
Actionable product states

02 / Context

A product for money already in motion.

Alpe brought together cash visibility, receivables and anticipation for businesses that needed to understand what was available now and what would become available next.

I connected the product architecture to a visual and interaction system, then worked hands-on across flows, high-fidelity states, component behavior and motion.

03 / Anticipation flow

Turn a financial operation into a clear sequence.

Each screen answered one question and kept the financial consequence visible.

  1. Start from available receivables, not from a generic service menu.
  2. Keep amount entry, fees and expected value in the same decision context.
  3. Use explicit review and completion states before returning to the balance.
Anticipation entry screen
Entry
Anticipation amount screen
Amount
Anticipation review screen
Review
Completed anticipation screen
Completion

04 / Operational depth

Design beyond the happy path.

The experience extended from the home into account statements and other card readers, with day and month views built on the same hierarchy.

05 / Validation

Completion was not enough. Comprehension mattered.

The retained research showed all 12 participants completing registration, while authorization language was initially understood by only 2 of 12.

That contrast redirected attention from task completion to financial comprehension, clarifying how confirmation, authorization and consequence should be written and staged.

Next case

Decathlon · Ecommerce View ↘