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
Four settlement paths, two regulatory regimes and three surfaces — a smartphone wallet, a feature-phone USSD session and an operator console. This is the interface design for all of it, screen by screen.
Open the prototype
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.
Start at the splash and walk the whole thing: sign in, Ghana Card verification, top up from MoMo, withdraw, and the transfer history.
Open the app → Feature phone · 10 screensThe *714*88# family support flow as a caller in Accra actually experiences it — a text terminal, no app, no data.
Dial the session → Desktop · 13 screensThe operator’s side: users and wallets, every transaction across the corridors, trade settlements awaiting review, and reports.
Open the console →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.
The four corridors
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.
The account everything else settles into. Onboarding and Ghana Card KYC, a dual-balance dashboard, and top-up and withdrawal across MoMo and bank rails.
View the wallet design → 02 · 13 screensGhana → 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 · operator consoleUsers, wallets and every transaction across all four corridors in one console. Trade settlements awaiting review, salary batches, USSD remittances, and reporting.
View the admin design →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
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.
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.
Every rejection names its cause, its remedy and whether money moved. On a remittance, a bare “transaction failed” is indistinguishable from a lost ₵858.
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.
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.
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
All 63 screens across the four corridors, including empty, pending, partial and failed states. Layout, typography, colour, terminology and the copy on every control.
No integrations, no backend, no CIPS or MoMo connectivity, no accounts. Licensing, settlement agreements and compliance sign-off sit outside this design work entirely.
Clickable prototype, component library, and the technical architecture behind each corridor — built out once the direction here is signed off.