Localization of payment pages
1) Localization goals (which we consider a success)
AR↑/Abandonment↓ due to understandable fields, familiar methods, native language.
Transparency: amounts shown correctly, fees, rates, taxes, withdrawal dates.
Compliance: correct legal wording, self-exclusion/RG, same-method policy.
Inclusiveness: a11u, RTL, non-Latin names/addresses, local requirements for details.
2) Locale definition and enabling rules
Signals: 'Accept-Language' → UI language, KYC country → legal/methods/limits, IP/GPS/SIM → pre-settings and "soft" localization, wallet currency.
In case of conflict (e.g. KYC = BR, IP = PT):1. Law and methods - according to KYC.
2. Language - at the user's choice (the switch is always visible).
3. Currency by account currency; if not, by KYC country, showing the course.
Remember the user's choice (cookie/profile) and log 'evidence' (for audit).
3) Currency, prices, taxes
Show local currency and, if debiting to another - conversion and exchange rate source (date/time).
Formats: thousand/tenth delimiters, currency signs before/after: '1 234.56 €' vs' $1,234. 56`.