Product Design · April 2026

TransferNetDesigning a Remittance App That Answers “Where Is My Money?”

  • TransferNetClient
  • Product DesignDiscipline
  • Sign-up to deliveryScope
  • MobilePlatform
TransferNet app screens arranged across a blue field, from onboarding through to transfer tracking.

Tl;DR

Money from Australia to Nepal, and never out of sight.

Sign-up, identity checks, a four-step send and a five-stage tracker. One phone, one corridor, no dead ends.

Problem

But.. what is the rate, and where did it go?

Remittance apps ask for a passport before they will quote you, then hide the fee until checkout. After you send, the money is simply gone for a while.

Home screen leading with the exchange rate, a trend line, transfer-type tabs and the fee shown before any tap.

the rate, first

the number that decides the transfer is the first thing on screen

Getting in

Two doors, then one field at a time.

The welcome screen routes rather than sells — new sender or returning, nothing else. Sign-up asks for an email and a password, password recovery states its rules inline instead of rejecting you afterwards, and verification ends on a screen that says so.

Welcome screen with two routes: get started, or already have an account.

route, don’t pitch

Create account form with email, password and confirm password fields.

one short form

Create new password screen with the character requirements stated inline beneath the field.

rules before the error

My role

Gate the button, don’t scold the user.

Identity is the step people abandon, so nothing turns red mid-typing. The form stays quiet and the button stays unavailable — completion is the only signal.

Identity form partly filled with the continue button held disabled.

not yet

The same identity form complete, with the continue button now active.

now

The send

A fee you meet at checkout is a fee you hid.

So rate, delivery method, fee and subtotal each get their own row on step one, where they can be read rather than discovered. Step two puts repeat recipients a tap away and gives a first-time sender something to do instead of an empty list.

Step one of the send flow with dual currency inputs, the rate card, delivery method, fee and subtotal.

cost, up front

Step two of the send flow with frequent recipients as avatar pills, a search field and an illustrated empty state.

or add a new one

The decision I’d defend

Payment happens outside the app. So prove it inside.

This corridor settles by manual bank transfer, which means the sender leaves, pays, and comes back. So the account details are copyable, the receipt upload is marked required, and Continue stays dead until the evidence is attached.

Payment step with copyable bank account details, an instruction callout and a required receipt upload zone.

upload payment

the hand-off is copyable and the requirement is not optional

Committing

Show the receipt back before you take the money.

The review screen repeats the amount, the recipient bank, the rate and the uploaded receipt as a thumbnail, so confirming is a check rather than a leap. The screen after it hands over a transfer number and a route straight into tracking.

Verification complete screen with a green check and a single call to action.

verified, once

Confirm transfer screen summarising amount, recipient bank, fee, rate and the uploaded receipt thumbnail.

the whole transfer, restated

Success screen carrying the transfer number and delivery method above back home and track transfer actions.

a number to quote

Coming back

The second transfer should be shorter than the first.

Saved recipients carry a send action on the row, so a repeat transfer skips the home screen entirely. The account screen keeps settings shallow and puts what the sender has saved in front of what the app wants to tell them.

Recipients list with frequent contacts as pills above a searchable list, each row carrying a send shortcut.

send from the row

Profile screen with a verified badge, three personal stats, quick action tiles and a settings list.

shallow settings

Impact

“Processing” had to mean something.

So the tracker names five stages, the pill always agrees with the timeline, and the history filters on the same words. Sender and recipient sit side by side, because the person asking is usually neither of them alone.

Transfer detail with a status pill above a five-stage vertical timeline showing completed, active and pending states.

five stages, three states

Transaction history grouped by date with a daily total, status filter chips and a track shortcut on every row.

the same words, as filters

What this taught me

When a product moves someone’s wages, ambiguity is the whole risk.

A missing status is not a small gap in a remittance app. It is somebody phoning home to ask whether the rent arrived.