Six words for money, and never a seventh

In a product where money moves, an amount is always somewhere. The words you use for those places will end up in your database, your dashboard, your support scripts and your users' heads. Choose them once.

What goes wrong

The usual failure is not that the words are bad. It is that there are too many of them, arrived at separately.

The backend has an enum. The dashboard shows a slightly friendlier version. The mobile app shows a third phrasing because that screen was built by someone else in a different quarter. Support has its own vocabulary that grew out of phone calls.

Nobody decided this. It accumulated. And now a user says "it says processing" and the agent has to work out which processing they mean.

The rule

One word per state. The same word everywhere — user interface, admin dashboard, support conversation, database column.

If a state needs explaining, explain it in a definition the user can read, not by inventing a second word for the same thing.

Ours

Our own product uses six, and we treat adding a seventh as a schema change rather than a copy change:

• Pending — the code exists, nobody has scanned it
• Scanned — the code has been used, and by whom
• Credited — the reward is in the user's wallet
• Processing — a withdrawal has gone to the gateway, no answer yet
• Success — the money has reached the UPI ID
• Failed / Reversed — it did not arrive, and the amount is back in the wallet

Two of those pull double duty deliberately. Failed and Reversed mean different things internally — one never left, one came back — but from the user's position the outcome is identical, so they sit together in the interface and the money returns either way.

Why it is architecture, not copy

Because the alternative shows up in your data.

When each surface has its own vocabulary, you cannot query across them without a translation table. Your daily reconciliation has to know that four different strings mean the same thing. New engineers guess. Reports disagree with each other, and someone spends a week finding out why.

A fixed vocabulary is not about tone of voice. It is about being able to answer "how much is in flight right now" with one query and believe the answer.