Languages

How it works#

U.CASH Pay keeps two translation maps per language: a client map (everything your customers see - checkout screens, status pages, transactional email) and an admin map (the merchant console). Both are maintained by U.CASH; you never translate anything yourself.

• Checkout visitors get the language from their browser's Accept-Language header, falling back to English.
• Console users pick their language from the account menu; the choice is remembered per user.

Coverage#

68 languages including Arabic, Bengali, Chinese (simplified and traditional), Czech, Danish, Dutch, English, French, German, Greek, Hebrew, Hindi, Indonesian, Italian, Japanese, Korean, Malay, Persian, Polish, Portuguese (European and Brazilian), Romanian, Russian, Spanish, Swedish, Thai, Turkish, Ukrainian, Urdu, Vietnamese, and more - with full coverage of newer surfaces such as Bank Payments.

Right-to-left languages (Arabic, Hebrew, Persian, Urdu) render correctly in the checkout and console layouts.

Fixing the language of a checkout#

By default the checkout follows the visitor. If you embed a payment button on a page that is already in one language, you can pin it:

• Pass the language alongside the checkout parameters when you create it via the API or an SDK.
• A saved browser language choice wins over the automatic detection for returning customers.

Language never affects the payment itself: coins, amounts, and confirmation rules are identical in every language.