PRODUCTBRAND· Jul 2025

Tesser

Brand and UX/UI concept for compliant stablecoin rails built for financial institutions

Timeline
Jul 2025
Role
Design trial - brand & product UX
planned engagement
3 months
operating flows
2
Process & contextStrategy, decisions, outcomes, chronology, and sources

Context

Stablecoins gave financial institutions a faster, lower-cost alternative to traditional cross-border rails, but the product still had to fit existing controls. Tesser supported three corridors: letting customers pay in stablecoins, using stablecoins to pay out in fiat where banking rails are slow or expensive, and receiving stablecoins before off-ramping locally while retaining FX revenue.

Product decision

I treated Tesser as a complete operating layer for banks rather than a crypto exchange: custody, wallet and address setup, funding, payment execution, compliance checks, transaction signing, reconciliation, error handling, reporting, and realtime status all belonged in one desktop workspace. The interface keeps cash and stablecoin balances together, makes risk and action states explicit, and uses a restrained black, white, and electric-blue identity to make speed feel credible.

Concept outcome

A brand and product concept that moved from a scoped receive flow for a first customer to a demo-quality send flow for Money20/20, including crypto and fiat/off-ramp paths. The work also defined the component library, reporting direction, frontend implementation input, and a shared architecture for the Next.js build. This was exploratory trial work, not a shipped product engagement.

3 months
planned engagement

Brand review, receive-flow checkpoint, then the fully implemented send flow.

2
operating flows

Receive and send were designed as two sides of the same bank-facing workspace.

~80%
faster time to value

Tesser's platform promise for financial institutions adopting stablecoin rails.

ScopeBrand Direction, Product Framing, Receive Flow, Send Flow, UX/UI Concept, Dashboard, Alert & Reporting States, Component Library

Key decisions

Use bank operations as the mental model

The interface starts with balances, counterparties, status, risk, and reports rather than exposing blockchain mechanics as the primary navigation. Stablecoin rails stay available without becoming the mental model.

Keep failure and risk in the workflow

Failed payments, compliance issues, funding gaps, in-progress states, risk levels, and review actions stay visible where an operator is already monitoring transactions.

Make speed the brand promise

The identity pairs a restrained enterprise UI with direct, high-contrast campaign language about faster bank and cross-border movement.

Make receive and send one system

A single desktop architecture supports wallet setup, receiving addresses, funding, payment execution, fiat off-ramp, history, exports, and monthly reporting instead of splitting the product into disconnected tools.

Project chronology

From bank context to a demo-ready payment corridor

The trial was scoped as a three-month progression: establish the product and brand language, prove a live receive flow for one customer, then carry the same architecture into the full send experience.

The brand premise: institutional trust expressed at transfer speed.

01

Translate stablecoin rails into bank operations

The core account view pairs stablecoin and cash balances with counterparties, transfer status, risk, date controls, and reporting so operators can understand the corridor without switching mental models.

A bank-facing corridor view for balances, transactions, risk, and reporting.

02

Design for exceptions and adoption

The concept treats failed payments as actionable operational states, then carries the same clarity into outward-facing bank onboarding and international positioning.

A failed payment stays connected to its review path and downstream impact.
The product promise translated into international bank onboarding.

03

Complete trial deck

The original eight-page presentation includes brand direction, core UX/UI states, alert behavior, onboarding language, typography, and research references.

Original Tesser design-trial presentation. Open PDF ↗

04

Concept and later production direction

A separate comparison preserves the distinction between my exploratory dashboard concept and the product interface visible a year later.

Production reference above; original concept below. Open PDF ↗

2026 CONNOR LEE

LOS ANGELES, CA