Skip to content
Ritesh FirodiyaGet in touch

Work / Aakalan / Wiki / Surfaces

settle-receive

Surfacecanonicalverified 2026-09-23

SURFACE.MOBILE.SETTLE.RECEIVE

Summary

They owe you. There is nothing to pay, only something to record.

Raw wireframe

  • .context/designs/mobile/settle/receive.html

Why it is drawn this way

Recording is final, in both directions. See settling-is-immediate. The old copy explained why THIS direction was the exception; there is no exception left to explain.

Receiving used to slip straight back to the list, and paying landed on a "waiting" screen whose balance deliberately had not moved. Neither read as success, and "I pressed it and nothing happened" is exactly how the flow was reported. Both finish now, and both say so, in place.

The primary action exists in both directions. It used to exist only when you owed AND had their UPI ID, so the commonest thing on this half of the screen — recording what arrived — was a row in the body with nothing marking it as the point of the visit.

Remind is a message, not a settlement, so it never competes for the same slot as the button that records one. See we-never-message-anyone.

The currency line appears only when there genuinely is a second balance. A payment happens in ONE currency: somebody you share a Goa group and a Tokyo group with can owe you rupees and be owed yen, and there is no single amount to settle. See money-in-minor-units.

The currency symbol follows the balance being settled. It was a hardcoded ₹ on a screen whose whole reason for those chips is that the two can differ, so settling the yen line put a rupee sign in front of a yen amount.

Related

Sources

  • src/app/settle/[id].tsx

Every project of mine is written down like this.

Read the résumé