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.
Corridor 05 · 11 screens
Everything else in this product pushes cedi out of Ghana. This corridor pulls yuan in — an exporter in Takoradi invoices a buyer in Ningbo, the buyer pays over CIPS from a Chinese bank that will never install anything, and the payment has to find its way back to the right invoice. The whole design rests on one reference printed on a pro forma, and on being honest about the payments that arrive without it.
Flow A
Kwaku Asare ships 18 tonnes of shea butter to a buyer in Ningbo. He never sees the buyer’s bank, and the buyer never sees this product. What joins the two is a reference he prints on his pro forma invoice.
An inbound payment is not a transaction the recipient starts, which inverts every assumption in the rest of the product. The exporter’s only act happens before any money exists — registering the invoice and getting the reference onto it — and everything after that is waiting, with the two states that decide whether he loads a container.
Registration happens before the money, which is the whole trick of this corridor: the reference cannot be attached to an incoming payment retrospectively, so the invoice has to exist in the system before it is sent to Ningbo. The expected-by date is what later separates “waiting” from “overdue”, and it is captured here because only the exporter knows it.
The buyer types it into the remittance information field at their bank.
The reference is rendered as the largest thing on the screen because it will be retyped by hand at a counter in China, where nobody can read English instructions. The Chinese-language instruction sheet and the WeChat route are the actual distribution mechanism — an English PDF emailed to a buyer is how a reference gets omitted, and an omitted reference is the unmatched queue.
¥186,000.00 from Ningbo Hengxin
This screen exists to be looked at repeatedly and to answer one question: has the money actually arrived. The note is the commercially important line in the entire corridor — buyers routinely send a screenshot of a payment instruction and ask for the container, and an exporter with no independent way to check will ship against it.
At Stanbic, 06 Oct 2026, 11:18 GMT
Rate held for 09:41. Declining holds the yuan and re-quotes tomorrow.
The exact net is shown before conversion happens rather than on the receipt afterwards, which is the only version of “transparent pricing” that is worth anything on the inbound leg: a fee disclosed after an irreversible conversion is a deduction, not a price. Naming the three things that matched also pre-empts the question the flagged case raises — why this one went through and another did not.
A payment of ¥186,000.00 arrived from Ningbo Hengxin with no reference on it. The amount and the payer match your invoice; the reference field was left empty.
The middle tier of matching is where inbound corridors actually live, and it is designed as its own state rather than left as “pending”. The exporter’s confirmation is collected but explicitly described as insufficient, because a screen that lets the recipient self-identify a payment is a fraud route — and saying so plainly is cheaper than a delay nobody can explain.
06 Oct 2026, 11:41 GMT · Stanbic ••••8820
The receipt restates the rate and the fee that were quoted before conversion, in the same words, so the two screens can be compared line by line. That repetition is the point: a pricing promise made at quote time and then summarised differently on the receipt is indistinguishable from a pricing promise that was not kept.
Overdue is a filter of its own because on this corridor lateness is the normal failure, and it is a commercial fact rather than a technical one. The note says so directly — an exporter looking at a red row needs to know whether to chase his buyer or chase us, and every ambiguous status here produces a support call that a sentence would have prevented.
Flow B
The exporter with the most to lose is the one with the weakest phone. *714*88*4# answers one question — has my buyer’s money arrived — on a handset with no data, at a port with no signal worth the name.
Inbound payments settle first and are notified by SMS; USSD is how they are checked afterwards, never how they are started. Every query is bound to the registered phone, so a stranger who guesses a reference is told nothing at all rather than being told they guessed wrong.
Only the four digits are typed, not the whole reference — the prefix and the exporter’s own initials are already known from the SIM, and every character removed from a USSD entry is a keypress that cannot be mistyped on a numeric keypad.
The warning against shipping on a payment slip survives the cut down to 182 characters, which is the test of whether a line belongs on a USSD screen at all. It is the only sentence here that changes what the exporter does next.
Rate, fee and net fit on the smallest screen in the product, because the disclosure rule does not get a channel exemption. “No markup” costs ten characters and is the one claim a feature-phone user has no other way to verify.
One message covers both a mistyped reference and a real reference belonging to someone else, and it deliberately does not distinguish them. Telling a caller that a reference exists but is not theirs confirms a stranger’s invoice number for them, which on a corridor where the reference is the key to a payment is the beginning of an interception.
Decisions
Reference plus amount plus payer clears automatically. Amount plus payer is flagged and confirmed by two people. Amount alone goes to a human queue in the console. Treating the last two as failures would return money that is genuinely owed.
The 0.5% comes off the cedi payout, so it is quoted before the exporter agrees to convert, not disclosed on the receipt afterwards. A fee shown after an irreversible conversion is not a price, it is a deduction.
The single largest loss on this corridor is a container released against a payment slip. Every inbound screen, including the USSD one, says whether money has actually arrived at Stanbic.