Design demo. Every screen here is a static mockup — nothing is connected to a payment system, and no control does anything. Names, balances, account numbers and references are invented for review. The rate shown (¥1 ≈ ₵1.76) is illustrative, not quoted.

Interface design · MVP scope

A payments corridor between Ghana and China

Five settlement paths, two regulatory regimes and three surfaces — a smartphone wallet, a feature-phone USSD session and an operator console. One transparent price on every one of them: a 0.5% transfer fee and no margin on the exchange rate. This is the interface design for all of it, screen by screen.

eCedi · Bank of Ghana CIPS settlement Escrow MoMo & GhIPSS Ghana Card & passport KYC Visitor wallet 0.5% fee · zero FX markup

Open the prototype

Use it, don’t just look at it

These three are clickable. Buttons, rows, the tab bar and the sidebar all navigate, and on a phone the app fills the screen with no browser chrome in the way. Nothing moves money — but the shape of the product is real.

Prefer the annotated version? The pages below show every screen side by side with the reasoning behind it — that is the design review, this is the product.

141Screens designed
5Corridors
3Surfaces
0.5%Fee · no FX markup

Added in this revision

Six things the first draft did not cover

The corridor spec moved on after the first set of screens was drawn: money now has to come into Ghana as well as leave it, the people using it are not all Ghanaian — and not all of them live here, the price is fixed at 0.5% with nothing taken on the rate, and somebody has to be able to stop a payment that looks wrong. Each is linked below.

Kill switch · 5 + 3 screens

Freezing one account

A fraud queue that names the pattern rather than a rule number, and a freeze that states what it stops, what happens to money already in flight, and the words the customer will read — behind two signatures and an automatic review date. Plus the three screens the account holder sees.

Open the freeze design →
Kill switch · 4 screens

Stopping the whole corridor

Bank of Ghana gets a read-only window on the same ledger and one control nobody else has: a pause, scoped per direction, honest that what is already at CIPS cannot be recalled. Every pause and resume is signed and recorded.

Open the regulator view →
Onboarding · 10 screens

Opening an account without a Ghana Card

Much of this corridor is Chinese engineers, traders and students who cannot produce a Ghana Card on day one. Passport, immigration permit, optional non-citizen card — and the account’s own expiry tied to the permit’s, without ever holding the balance hostage.

Open the foreign route →
Visitors · 10 screens

Tourists and visitors paying in Ghana

A visitor wallet opened on a passport and entry stamp in ten minutes, loaded from a card or bank at home at a stated rate, spent on any shop QR or MoMo number — taxis and market stalls included — and emptied back home on departure. Plus the trader’s side: tourist money in cedis, with no card machine.

Open the visitor route →
New corridor · 11 screens

Money coming the other way

An exporter registers an invoice, prints the reference on the pro forma, and the buyer in Ningbo pays over CIPS quoting it. Matched at the bank, converted at a locked rate — and the payments that turn up with no reference at all get their own queue.

Open the inbound corridor →
Pricing & compliance · 6 screens

One fee, shown before you commit

School fees, a hospital bill or a supplier invoice: a purpose, the documents that match it, and a quote carrying the locked rate, the 0.5%, the exact yuan delivered and the 14:00 GMT cut-off. Every screen in the product now prices this way.

Open the payment flow →

The five corridors

Each one moves money a different way

They share a wallet and an identity, but almost nothing else. A trader settling a container of cocoa and a construction worker’s mother sending school fees need different screens, different devices and different guarantees.

01 · 64 screens

eCedi Wallet

The account everything else settles into. Three identity routes — Ghana Card, a passport and an immigration permit for the foreign nationals this corridor is largely built for, or a short-stay visitor wallet for tourists — a dual-balance dashboard, MoMo and bank rails, documented payments out of Ghana, an e-CNY travel wallet, and what a holder sees when a payment is stopped.

View the wallet design →
02 · 15 screens

Family Support over USSD

Ghana → China remittance on a feature phone. A 182-character session with no app, no data connection and one shot at getting the confirmation right.

View the USSD design →
03 · 22 screens

Admin Panel

Users, wallets and every transaction across the corridors in one console — plus the two controls that stop money rather than move it: an account freeze with two signatures behind it, and the Bank of Ghana’s corridor pause.

View the admin design →
04 · 11 screens

Money coming in

The China → Ghana leg. An exporter registers an invoice and gets a reference; the buyer pays over CIPS quoting it; the payment is matched at Stanbic and converted at a locked rate with the fee shown before the exporter agrees. Plus the payments that arrive with no reference at all.

View the inbound design →
05 · deferred

Self-service portals

Employer payroll and trade settlement are designed and monitored from the admin panel in this scope. Giving contractors and exporters their own portals is a later phase, once the corridor itself is proven.

Design language

Decisions that shaped every screen

Balance

Two figures, never one

Held and available diverge whenever escrow is live. A single balance would be wrong on any day a trade is in flight, so both appear everywhere a balance appears — including inside the USSD session.

Currency

Show the far side

A sender in Accra is thinking in what lands in Guangzhou. Every amount entry shows the converted figure and the rate before the amount is committed, not after.

Failure

Failure gets equal design

Every rejection names its cause, its remedy and whether money moved. On a remittance, a bare “transaction failed” is indistinguishable from a lost ₵858.

Batch

Nothing bulk is atomic

Thirty-eight salary credits succeed or fail independently, so progress is counted and failures retry individually. Retrying the whole batch to fix one is how duplicate salaries happen.

Reference

One reference per transfer

The same identifier appears in the USSD session, the SMS, the app and the receipt. Two channels producing different references for one transfer makes support impossible.

Price

One fee, and no spread

0.5% of the transfer, and the bank’s rate passed through untouched. Every quote, receipt and USSD summary states the rate, the fee and the exact net — and puts “no markup” beside the rate, because that is the one number a user cannot check for themselves.

Stop

Two switches, both witnessed

An operator can freeze one account when a pattern looks like fraud; Bank of Ghana can pause a whole direction of the corridor. Both state what happens to money already in flight, both need a signature, and both leave a record neither side can edit afterwards.

Locale

Built for the network, not the demo

Most users arrive on a mobile connection with variable bandwidth. Screens are typographic rather than image-heavy, and the USSD flow assumes the session may die at any point.

Scope

What this covers, and what it does not

In this demo

Interface design

All 141 screens across the five corridors, including empty, pending, partial, held and failed states. Layout, typography, colour, terminology and the copy on every control — including the exact wording shown to someone whose wallet has just been frozen.

Not yet

Anything that moves money

No integrations, no backend, no CIPS or MoMo connectivity, no accounts. Licensing, settlement agreements and compliance sign-off sit outside this design work entirely.

Next

On agreement

Clickable prototype, component library, and the technical architecture behind each corridor — built out once the direction here is signed off.