Use bank operations as the mental model
Lead with balances, counterparties, risk, and reports so bank operators can work in familiar terms.
A bank-facing stablecoin payments concept
Problem
Banks needed stablecoin transfers to fit existing custody, compliance, reconciliation, and fiat payout processes.
Approach
Keep cash and stablecoin balances in one workspace, with explicit risk, status, and next actions so operators can follow each transfer.
Concept outcome
Delivered brand and product concepts for receive, send, and fiat payout flows, plus a component library and Money20/20 demo direction. Exploratory trial work; not a shipped engagement.
Key decisions
Lead with balances, counterparties, risk, and reports so bank operators can work in familiar terms.
Keep payment failures, funding gaps, compliance checks, and review actions beside the transactions they affect.
Pair a restrained bank interface with direct campaign language about transfer speed.
Use one workspace for custody, transfers, fiat payouts, history, and reporting.
Project chronology
The trial deck proposed an August–October engagement: establish the product and brand language, test a scoped receive flow, then extend it into send. The dates and milestones below describe that proposal, not completed delivery.
01
Cash and stablecoin balances sit alongside counterparties, transfer status, risk, and reporting.
02
Failed payments have clear next actions; the same clarity carries into bank onboarding.
03
The eight-page trial deck covers identity, UX/UI, alerts, onboarding, typography, and research.
04
The comparison distinguishes my exploratory concept from the interface visible a year later.