When you build checkout for a region where card penetration sits below 30 percent, the form has to start with mobile wallets and local bank transfers, not Visa/Mastercard tabs. Central Asia — Uzbekistan in particular — has its own mix of UZCARD, Humo, and phone-balance top-ups.

Field order matters

Western checkout forms put the card number first. For UZ users the card fields should sit below the wallet option, because most first-time deposits come from a mobile wallet. The heuristic: sort methods by historical conversion rate for the geo, not by global popularity.

const sortedMethods = methods .filter(m => m.supportedGeos.includes(geo)) .sort((a, b) => b.conversionRate[geo] - a.conversionRate[geo]); 

Handling sum validation

Minimum deposits vary per method and currency. A site like 888Starz publishes its method-specific limits openly, which lets you cross-check that your validator matches the operator's actual floor. Hard-coding limits leads to silent failures when the operator adjusts them server-side.

Currency display

UZS amounts run into the millions for modest sums. Use Intl.NumberFormat('uz-UZ', { style: 'currency', currency: 'UZS', maximumFractionDigits: 0 }) and always drop the decimals — no one pays 1.5 soum.

Takeaway

Localised payment UX is not about translating labels. It is about knowing which methods dominate, surfacing them first, and validating against the operator's real constraints rather than a static config file.