Aglet

How to prioritize checkout currency mismatch risks

Prioritize currency work by the difference between a readable display problem and an amount or currency mismatch at payment or order persistence. A clear ISO code can resolve symbol confusion, while a charged amount that differs from review needs faster attention. Use tested currencies and locales only.

Decide where the work belongs

  1. Separate formatting from amount

    Elevate a saved order or payment amount that disagrees with the review above a misplaced decimal separator that leaves the numeric value intact. Treat an unclear symbol as risky when multiple currencies use it and no code is shown.

  2. Describe supported scope

    List currencies, locales, payment states, and fixed amounts tested. Include observed support cases only when order and payment records can be compared. Mark untested precision or conversion paths unknown rather than claiming every currency is affected.

  3. Choose a safe fallback

    Decide whether to display an ISO currency code, freeze conversion before payment, or stop when the amount cannot be reconciled. Do not silently switch currency or round a value without showing the resulting total. Assign an owner for any temporary wording.

What to carry forward

Prioritize a payment or order currency disagreement highest, then an ambiguous amount that could change a decision. Queue formatting-only work with tested locale scope, an explicit fallback, and the evidence needed to reassess unsupported currencies.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow