Skip to contentMasha Sidorova

Tether Payments

One wallet for crypto holders and the unbanked, with an Arabic version people stayed for

Tether bridges the gap between investment and utility for 500M+ users: a high-trust ecosystem for storing and spending funds across a global network of online and in-person merchants.

Unlock screen, dark theme: Hey, Tom!

Problems

The app had to serve people already holding crypto and the billions still outside the banking system, at the same time.

Tether's brief asked for payments in dollars "as easy as paying with a Visa or Mastercard", with as few steps and clicks as possible. Stakeholders measured success by one thing first: the time from opening the app to having funds in the wallet. The problems they named were:

  1. KYC friction, for people who arrive mid-checkout and want to pay now.
  2. Funding the wallet, which they expected to be the hardest step.
  3. Distrust of crypto and low financial literacy.
  4. Different languages and currencies, with early adopters in countries such as Turkey, Argentina and Mexico.
On this pageSolution

Solution and impact

  1. Fast-funnel onboarding that runs from sign-up to the first deposit, with wallet setup as a natural step, not a gate.
  2. A dashboard built around the balance and Deposit, with Scan QR, Send and Deposit one tap away.
  3. Plain language, a clear detail page for every payment, and recovery flows that reassure instead of alarm.
  4. A currency picker and RTL rules for Arabic, with the numeral format left in the user's hands.
10%
Arabic-language users kept the app because it finally felt built for them.
500M+
Users already rely on the experience built to support their needs at scale.
Summarize with AI

2 audiences, one app:
Tether holders first, the unbanked next

Tether Payments Group is the payments arm of Tether. Its mission is to bring the billions of unbanked people into the dollar economy with payments that are safe, simple and cheap. The first users would be people who already hold Tether; the long-term audience is anyone, including people who have never used a crypto wallet.

  • As few steps as possible. The brief set the bar at paying with a Visa or Mastercard in the US.
  • No crypto talk. "Positioning us as a crypto company is going to do us a disservice."
  • Volatile currencies in the first markets, and Arabic speakers whose habits differ by region.
  • iOS in light and dark from day one, handed off to engineering with written rules.

Decision 1

In a financial app, trust is won or lost in the first session

People leave a wallet that feels like an obstacle before they ever fund it. So the core experience runs in one line from the first screen to money in the wallet: sign up, protect the account, back up the key, deposit. Each step asks for one thing and says why. When something goes wrong, a forgotten password or a lost phone, recovery is just as calm: 2 clear ways back, by email or with the private key.

Start and onboarding: gateway to the global economy
Sign up: let's get started
Sign up: personal info
Sign up: phone number
2-factor authentication: enter the 6-digit code
Create a password
Create a PIN
Confirm your PIN
Back up your wallet: your private key
Back up your wallet: copied to clipboard
Dashboard, first time: how much to deposit?
Deposit: enter an amount or pick 100, 500 or 1,000
Deposit filled: send 500.00 USDT from Apple Pay to the wallet

Forgot the password

2 ways back are offered at once. By email, the link opens the mail app and a new password is set in 2 steps.

Log in: incorrect password, with Forgot your password? under the field
Reset password: use email or phone, or a private key
Reset password by email: Send link
We've sent a link to your email: Check my inbox
Open mail app: Mail, Gmail or Outlook
Set a new password, with the rules checked as you type
You changed your password: Log in with password

Lost the phone

The other way back is the private key saved at sign-up: paste it, import, and the wallet returns with its balance.

Log in: incorrect password, with Forgot your password? under the field
Reset password: use email or phone, or a private key
Restore wallet with a private key: the 64-character code from the previous wallet
Paste from Notes: the system asks for permission
The private key is pasted: Import wallet
Dashboard: wallet restored, with the balance back

Decision 2

Paying should take a scan, an amount and one confirmation

"Open the app, scan a QR code… confirm your payment, and off you go." Scan QR stays one tap away on the home screen. The amount, the recipient and the fee sit on one confirmation screen, the code check comes only at the end, and every payment gets a clean detail page afterwards.

Scan QR: the merchant's code is in the frame
Send USDT by QR: enter amount
Send USDT by QR: 213.90 USDT typed
Confirm payment
Verify transaction: choose a method
Verify transaction: enter the 6-digit code
Transaction in progress
Success: you sent 213.90 USDT
Transaction details

Decision 3

Mirroring is not RTL: I reengineered the architecture, not flipped it

Arabic speakers don't share one set of habits. Which numerals people read money in varies across countries, regions and even within one country: some users in the Gulf prefer Eastern Arabic numerals, ١٢٣٤, others Western ones, 1234. For an app this large, one mirrored layout would fail someone.

I synthesized the existing RTL rules into one Arabic version guide for the hand-off, so every screen solves the same cases the same way:

  • Layout and navigation. The whole screen mirrors, including navigation bars, tab bars and sliders; Back flips, and transitions slide right to left. Icons that show direction, such as Send, flip too; carousels run the other way.
  • Text direction. Alignment follows the language, not the mirror: an amount right-aligned in English stays right-aligned in Arabic, and Latin brand names don't break the right alignment.
  • Numerals are the user's choice. People pick Eastern Arabic or Latin digits when they pick the language.
  • Latin inside RTL. Email and password fields keep the RTL layout. Verification codes, the hardest case, render LTR within the RTL flow, aligned to the layout: filling the width or centered.
  • Typography. Noto Sans Arabic, line height 10–40% above the English default, slightly negative letter spacing, and weights matched by eye across scripts.

Numeral format: Western vs. Eastern Arabic

Which numerals people expect varies by country, region and even within one country. So the choice comes with the language: Eastern Arabic or Western digits. Each screen has its own slider.

Settings in Arabic, right to left, with Eastern Arabic numerals
Settings in English, left to right

Settings

Dashboard in Arabic, the balance in Eastern Arabic numerals
Dashboard in English: 12,345.67 USDT

Dashboard

Preferred language: Arabic with Eastern Arabic numerals selected
Preferred language: Arabic with Western numerals selected

Numerals

Unlock screen in Arabic
Unlock screen in English: Hey, Tom!

Unlock

Eastern Arabic numerals
Confirm payment, RTL

Arabic, RTL and numerals.

Decision 4

A variable color system that made dark theme a mode, not a redesign

Every component is documented for LTR and RTL, light and dark: a single source of truth for a dual-language, dual-theme product. Each screen below has its own slider: drag it to see the same screen in the other theme.

Unlock screen: Hey, Tom!, dark theme
Unlock screen: Hey, Tom!, light theme

Unlock

Dashboard, first time: how much to deposit?, dark theme
Dashboard, first time: how much to deposit?, light theme

Dashboard

Success: you sent 213.90 USDT, dark theme
Success: you sent 213.90 USDT, light theme

Success

Transactions history by month, dark theme
Transactions history by month, light theme

History

Process

From 5 stakeholder interviews to a design brief the team could build against

I prepared the research: the interview plan with the Clay research team, and a competitor review of PayPal, Venmo, Nubank, Alipay, PayTM and Trust Wallet across onboarding, dashboard, deposit and withdrawal, and wallet security. After 5 30–40 minute interviews I synthesized the takeaways and took them straight into the designs, updating the screens as the picture got clearer.

TakeawayWhat it changed in the design
Users arrive mid-checkout and want to pay nowFast-funnel onboarding: wallet setup reads as a natural step, not an obstacle
Funding the wallet is the biggest challengeThe dashboard puts the balance and Deposit first, with security and KYC as short next steps
"Open the app, scan a QR code… confirm your payment, and off you go"Scan QR, Send and Deposit stay one tap away on the home screen
Distrust of crypto, low financial literacyPlain language, a clear detail page for every dollar-backed payment, recovery flows that reassure
Language and currency vary by marketA currency picker, and the RTL rules for Arabic

Impact and reflection

10% of Arabic-language users stayed because the app finally felt built for them

They could set the app up the way they read, numerals included, and every screen behaved the same way. The experience now serves 500M+ users.

What I take forward: when one audience has split habits, the answer is a choice and a rule, not a guess. Writing the rules down as a hand-off guide turns one designer's decisions into something the whole team and engineering can apply.

See other cases