Money input must name the currency; do not let people assume the current one

What it is

A number in an amount field is meaningless without a unit: “100” may be yuan, dollars, or yen. People fill the blank with the currency in their own wallet; if the system books another, the gap is an exchange-rate multiple. Explicit currency denomination makes the currency visible and confirmable at input time, not only later on a statement. The issue is which currency this money is, not how thousands are grouped, and not a later mismatch between a number and a unit.

Why it happens

Number perception carries no dimension. Missing a currency, working memory fills in “of course local” or “of course USD”—two defaults that collide for cross-border, travel, and multi-currency accounts. The $ sign is used in several countries; seeing it may still be Australian or Canadian dollars. A label that says “Amount (USD)” once, with no currency in the slot, leaves the viewport on scroll or focus and the default assumption returns. A currency choice buried in account settings is invisible at fill time, which equals not choosing. The error detonates at booking, reconciliation, or refund, when nobody remembers which currency they thought they were in.

Studying it

Show multi-currency users amount slots with digits only, $ only, or an ISO currency code; have them enter “a hundred,” then ask which currency the system will take. Factors: region, account default, whether the slot can switch. Outcomes: currency-judgment accuracy, later reconciliation surprise. Do not sample only one region. Support tickets that say “I thought it was local currency” are ready-made error language.

Where it stops holding

A product that takes one currency, with users in the same region, makes repeated currency chrome noise; a page-level statement is enough. Crypto, points, and game coins are not ISO currencies, but they still need names that will not be taken as fiat. An FX preview (“about xx local”) can cut errors, but the preview must name both currencies or it is just another dimensionless number. On a read-only history, currency must travel with each line; do not guess last year’s money from the current account default.

Applying it

• Show a currency name or code in or next to the amount slot; never present the digits alone.
• When several currencies are legal, offer an in-moment switch; do not rely only on a default buried in the account.
• Do not let $ mean US dollars by itself; pair it with USD or “US dollar.”
• Verify by cropping the amount off the page and asking “how much, of what.” A miss or a wrong currency means denomination still rides on an assumption. Then have a cross-border user enter an amount and compare booked currency with what they believed.

Related

• Within the group: E2.19.2 Unit input must accept a familiar system and convert · E2.19.3 Grouping and decimal marks vary by locale and must adapt · E2.19.4 Number–unit coupling errors are hard to notice before submit
• Adjacent: E2.11 Numeric input and steppers · E2.07 Input masks
• Search terms: explicit currency denomination · currency code · ambiguous dollar