CRYPTO WALLET & PAYMENT CARDSBrand · Product · Handoff

From your wallet.
To your everyday.

A crypto wallet paired with payment cards.
Designed to connect digital assets with everyday purchases.

Explore the challenge ↓
ONE WALLET. MULTIPLE CARDS.

The Future of
Your Wallet.

WALLET → CARD → EVERYDAY SPENDING
MY ROLE

Sole designer

Brand, UX & UI
TIMELINE

Jun–Sep 2025 · 3 months

Outside my day job
PRODUCT

Crypto wallet & payment cards

Mobile experience
PROJECT STATUS

Design delivered

Client & engineering handoff
PROJECT BACKGROUND

I designed 28Pay from June to September 2025, over three months outside my day job. As the sole designer, I owned the brand and logo, UX and UI, marketing materials, App Store screenshots, and the app-download landing page.

The central design challenge was defining the relationship between receiving crypto, getting a card, and making money available to spend. I worked through that question with the stakeholder, then delivered the designs to the client and engineering team. My engagement ended at handoff.

WHAT IS 28PAY?

Crypto comes into the wallet.
A funded card takes it into everyday spending.

The product brings a crypto wallet and payment cards into one app. The wallet receives and manages crypto assets; the card provides a way to pay for meals, shopping, and online services. The original application designs offer Visa and Mastercard choices.

  1. 01 / RECEIVEDeposit crypto

    Choose an asset and network to receive funds into the wallet.

  2. 02 / APPLYGet a card

    Choose a card and complete the application and identity checks.

  3. 03 / FUNDFund that card

    Move funds from the wallet to the selected card. Its balance is shown in USD.

  4. 04 / SPENDPay with the card

    Use the card’s available balance for everyday and online purchases.

Getting a card and funding it are separate steps. Money received in the wallet is not automatically available on a card.

01 / THE AMBIGUITYDEFINING THE PRODUCT TOGETHER

One product idea.
A funding model still to define.

The stakeholder wanted people to bring crypto into 28Pay and use a card for everyday purchases. The ambiguity was in the requirements: where should incoming funds sit, what does opening a card actually enable, and which balance does a payment use? We needed to agree on these rules before the screens could give a clear answer.

THE MODEL WE AGREED ON

One wallet receives the crypto.
Each card is funded separately.

Separate balances, connected by explicit transfers.
  1. Give incoming crypto one home

    External crypto deposits needed to enter through the wallet, not directly into a card. We made the wallet the common place to receive and manage assets, so adding another card would not require a separate deposit destination.

  2. Separate getting a card from funding it

    Choosing Visa or Mastercard and completing the application gives the user a card. It does not move money onto it. I separated application completion from funding so “card issued” would not be mistaken for “money ready to spend.”

  3. Make allocation a deliberate choice

    With several cards, the destination matters as much as the amount. A manual top-up lets the user choose which card receives funds and review the amount before confirming. The return flow lets card funds move back to the shared wallet.

THE TRADE-OFF

A separate card balance adds a funding step and another balance to understand. My design response was to keep the selected card, source balance, and amount visible together, rather than imply that all wallet funds were ready to spend.

MY UX CONTRIBUTION

Clarify the rule with the stakeholder.
Carry it through every money journey.

The decision is visible in the delivered screens: asset details within the wallet, a named destination card, and separate funding and return flows.

Where this fits among crypto-card products Retrospective context ↗

Official documentation reviewed in October 2026 provides context for this case study. It is a retrospective comparison, not research conducted during the 2025 project.

PREFUND A CARD BALANCE

Crypto.com Prepaid Visa · US

The US funding guide describes adding funds to the card from crypto or cash. An optional Auto Top-up also exists: a separate balance does not have to mean manual funding.

CRYPTO FOR EVERYDAY PAYMENTS

RedotPay

Its official card guide describes a stablecoin-based card for spending crypto at online and in-store merchants. It is a real-world example of the product category, not evidence that its funding model matches 28Pay’s.

For 28Pay, separate balances and manual funding were the agreed product model. These examples help explain that choice; they do not establish 28Pay’s conversion, custody, or settlement rules.

02 / THE MONEY MODELFROM PRODUCT RULE TO USER UNDERSTANDING

One wallet.
Multiple cards to fund.

The wallet contains assets such as BTC, ETH, and USDT. Each payment card has a separate balance shown in USD. Users manually fund a selected card from the wallet and can transfer card funds back. The wallet shows what you hold; the card shows what you have set aside to spend.

FUNDING IS AN EXPLICIT STEP Money movement
Fund card
Return funds
Manual transfers
+
Get a card

Choose a card, complete the application and identity checks.
Then fund the card separately.

Card state
Shown: money moving between the wallet and one selected card. *Card status and transaction rules also affect spending.
Deposit

Add money to the wallet.

External funds → Wallet
Get a card

Choose a card and complete the application.

Card status changes
Fund card

Move money onto a selected card.

Wallet → Card
Return funds

Move card funds back to the wallet.

Card → Wallet

Keep the selected card identifiable

The card picker uses names and last four digits. Funding is tied to a specific card, even when several cards share the same wallet as their source.

Make both directions clear

Funding a card and returning its funds connect the same two balances. The transfer view identifies which account the money leaves and which receives it.

03 / THE EXPERIENCEPUTTING THE MODEL INTO PRACTICE

Receive it. Use it.
Know where it goes.

The flows cover receiving crypto in the wallet, funding a selected card, and withdrawing wallet assets to an external address. Each step makes the destination and the next action visible.

01 / RECEIVE CRYPTO

The right asset.
On the right network.

I separated asset, method, and network selection before showing the receiving address. The address screen keeps the chosen asset and network visible while the user copies or shares it.

28Pay is the receiving side. The user takes these details to the platform or wallet they are sending from.

Swipe to explore · Click to enlarge ↗
01–02 / 06
AT THE POINT OF CHOICE

Network requirements appear where the network is selected, then remain visible beside the receiving address.

FROM MY DESIGN NOTES

“Select the network, copy it to the sending side; this is the receiver.” This note guided the deposit sequence.

Original designs with sample addresses and network requirements.

02 / FUND A CARD

From the homepage
to a funded card.

Choose the destination card, review the top-up amount in USD, and confirm the funds received.

Swipe to explore · Click to enlarge ↗
01–02 / 04
MULTIPLE ASSETS IN THE WALLET

Wallet deposit starts with an asset and network. BTC, ETH, and USDT have their own balances; a USD equivalent expresses their value without implying a currency exchange.

A USD AMOUNT FOR THE CARD

The form labels its source “USD 錢包餘額” and shows the top-up amount in USD. This step focuses on the selected card and amount; it does not repeat the asset selector from wallet deposits.

The designs establish the user-facing funding flow and USD display. The timing of crypto conversion and the issuer’s custody and settlement arrangements were not confirmed within my scope. Sample amounts and card details vary across screens.

Different starting points. A clear next action.

This reading guide separates having funds, having a card, and being ready to spend.

STATE 01 / 03

Money is in the wallet.
No card has been issued yet.

This scenario starts with wallet funds and no card. Show card application as the next step, without implying that the wallet balance is already available for card spending.

SUGGESTED NEXT ACTIONGet a card ↗
Case-study explainer · guidance for further validation
Questions for a future iteration Beyond the shown flows
Pending or unsuccessful funding

Make the location of the funds and the next action clear.

A frozen card with remaining funds

Clarify whether and how funds can be returned while the card is frozen.

Further design work, subject to product and operational requirements.

KEY PAGES / CARD APPLICATION

Opening a card,
step by step.

Application establishes access to a card. The completion screen then points toward funding it.

Swipe to explore · Click to enlarge ↗
01–02 / 06

Original designs with sample data. Application payment and card top-up are separate steps.

03 / SEND & TRACK

Review before sending.
Know what happens next.

Choose an asset and network, enter or scan the destination, and review the amount and cost. Then verify with Face ID and check the transfer status and result details.

Swipe to explore · Click to enlarge ↗
01–02 / 08
BEFORE SUBMISSION

The form keeps the destination, sent amount, fee and received amount in view before verification.

AFTER SUBMISSION

Processing and result views make the status and transaction details available to review.

Original design states with varying assets, networks and amounts; not one completed transaction.

What I would refine next

Use one consistent transaction example, clarify the processing-stage labels, and design failure and timeout recovery. The screens show status feedback; they do not establish those recovery rules.

THE DETAILS THAT SUPPORT THE FLOWS

Make the money model
visible in the interface.

The same relationship carries through balance labels, transfers, and card activity.

01
BALANCE CLARITY

Name the balance.
Name the destination.

Tap USDT to view its details · Swipe to explore

A Wallet overview

Select USDT

B USDT details

One asset within the wallet

C Card overview

A separate card balance

DESIGN DECISION

The wallet overview leads into individual assets: selecting USDT reveals its balance, funding-account distribution, and history. The card has a separate balance shown in USD, with “充值卡片” keeping funding in the card context.

WHAT I WOULD REFINE

The card screen’s “帳戶餘額” could be more explicit. I would test “Card balance” to check whether people identify the spendable amount.

02
MOVING MONEY

Fund a card.
Move money back.

Wallet Card

Fund the selected card for spending.

Card Wallet

Return card funds to the wallet.

From the card homepage, open management and choose “劃轉.” The transfer view connects the selected card and wallet in either direction. Below is the card-to-wallet path.

Swipe to explore · Click to enlarge ↗
01–02 / 06

Original connected Figma screens; card details, amounts, and exchange terminology are sample design content.

03
EVERYDAY TRANSACTIONS

From a balance
to a record of activity.

Original 28Pay card overview with card balance, funding action and dated transaction history
Fixed bottom menu: 28Pay selected, Wallet, More
Scroll the screen ↓
CARD OVERVIEW & TRANSACTION HISTORY

I kept the selected card, its balance, and activity together.

See the card and its balance

The card above the amount identifies which balance is shown.

Keep funding within reach

“充值卡片” gives the balance a next action.

Review what happened

Dated transactions connect the balance to amounts, currencies, and activity.

Original interface · sample transaction data

04
CARD PERSONALITY

A card that feels
like your own.

Color choices bring the brand into card selection while preserving a consistent layout.

Electric blue
Bright orange
Vivid pink
04 / HANDOFF & REFLECTIONWHAT I DELIVERED AND LEARNED

A defined experience,
handed over for development.

I delivered the brand, product designs, and supporting marketing materials to the client and engineering team. Our collaboration ended at handoff, so I cannot confirm the subsequent launch status or business outcomes.

01

Make the trade-off explainable

Separate balances made funding a specific card explicit, but added a step. The design work was making that step understandable across deposits, funding, returns, and withdrawals.

02

Carry clarity through the journey

Network and address identify a deposit destination. Card identity anchors funding. Progress and transaction details explain what happens after a withdrawal is submitted.

03

Explore purpose-based cards

One wallet and multiple identifiable cards could support organizing spending by purpose, such as subscriptions or daily purchases. This remains a future direction, not a delivered feature.

A reference for that future direction: RedotPay describes using card themes to distinguish work and personal cards. Visual organization is different from enforcing spending rules. Reviewed October 2026.

What I would validate next Proposed follow-up
Understanding the balances

Can someone explain why a funded wallet does not automatically mean a funded card?

Funding the intended card

Can they select the right card, identify the wallet source, and explain the received amount?

Making a deposit

Can someone choose the matching asset and network, then locate the receiving address?

Following a withdrawal

Can they explain the fee and received amount before submitting, then find the status and transaction details afterward?

Reading activity

Can they connect a transaction’s amount and currency to the selected card?

These are proposed checks, not completed research or measured results.

A clearer path from
holding to spending.

UX & UI by Tori TaoBack to top ↑