Use bank operations as the mental model
Lead with balances, counterparties, risk, and reports so bank operators can work in familiar terms.
Tesser
A bank-facing stablecoin payments concept
01
Translate stablecoin rails into bank operations
Cash and stablecoin balances sit alongside counterparties, transfer status, risk, and reporting.
02
Design for exceptions and adoption
Failed payments have clear next actions; the same clarity carries into bank onboarding.
03
Complete consultation deck
The eight-page consultation deck covers identity, UX/UI, alerts, onboarding, typography, and research.
04
Concept and later production direction
The comparison distinguishes my exploratory concept from the interface visible a year later.
Project evidence & details
Project evidence & details
View the consultation presentation ↗
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. Independent consultation concepts; the later engagement plan remained a proposal.
- Evidence · product + brand direction
- ConsultationThe deck and UI studies document proposed work, not a completed three-month engagement.
- Scope · operating flows
- 2Receive and send concepts share one bank-facing workspace.
ScopeBrand Direction, Product Framing, Receive Flow, Send Flow, UX/UI Concept, Dashboard, Alert & Reporting States, Component Library
Key decisions
Keep failure and risk in the workflow
Keep payment failures, funding gaps, compliance checks, and review actions beside the transactions they affect.
Make speed the brand promise
Pair a restrained bank interface with direct campaign language about transfer speed.
Make receive and send one system
Use one workspace for custody, transfers, fiat payouts, history, and reporting.
Project chronology
Proposed path from bank context to a payment demo
The consultation 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.
- Aug 1–501 · Proposed foundation
Review the brand and website
Audit Tesser's existing brand guide and marketing site for clarity, responsiveness, hierarchy, and the credibility required by financial institutions. - Aug 5–Sep 1502 · Proposed checkpoint
Ship a scoped receive flow
Design the first-customer path: email entry, OTP / magic link / passkey authentication, wallet setup, receiving addresses, and the reporting process around a fiat off-ramp. - Sep 15–Oct 3103 · Proposed demo
Build the send flow for Money20/20
Extend the same architecture into onboarding, KYB, first funding, single-payment execution, crypto or fiat termination, compliance checks, transaction signing, realtime status, history, filtering, and exports.