Uzbekistan Payments Guide

Payments in Uzbekistan: Uzcard, Humo, and App-Led Domestic Commerce An Uzbek customer can choose to pay by card without thinking about a card network. The customer may open a bank or fintech application, select a saved Uzcard or Humo credential, approve a payment request, scan a QR code or send funds through a familiar transfer flow. The application—not the logo printed on the card—may be the part of the experience the customer recognizes and trusts. An international merchant can therefore be technically ready for card payments and commercially absent from everyday Uzbek commerce. A checkout that accepts Visa and Mastercard may work for tourists, internationally enabled customers and some co-badged cards. It does not necessarily reach the domestic credentials and application-mediated payment experiences that shape much of the local market. The scale of that domestic system is substantial. Uzbekistan had 74.6 million bank cards in circulation, approximately 448,000 POS terminals and 46,678 ATMs and self-service kiosks on 1 July 2026. These are payment instruments and acceptance points, not unique customers. The country’s population is approximately 38.9 million. (CBU)

The applications surrounding those cards are equally important. The Central Bank reported more than 74 million remote-banking registrations by October 2025, while mobile-application transactions reached approximately UZS646 trillion during 2025. Registrations may include the same person at multiple institutions, and the transaction figure includes transfers and other financial activities beyond ecommerce. (CBU) The invisible infrastructure beneath a payment button includes: 1. The customer’s bank or payment application. 2. The card credential or account selected inside it. 3. Uzcard, Humo or an international scheme. 4. A bank, processor, payment organization or aggregator. 5. The merchant’s order and confirmation system. 6. Settlement, reconciliation and refund processes. 7. Any international-card or cross-border overlay. Each layer can change eligibility, customer trust, authentication, payment confirmation, refund behavior and merchant access to funds. The strategic conclusion is: Uzbekistan requires a domestic-card-first payment strategy with app-aware checkout design. Visa and Mastercard are important additions, but they are not substitutes for reliable Uzcard and Humo ecommerce support.

Uzbekistan payment snapshot Category Uzbekistan market position Region Central Asia Population Approximately 38.94 million in the IMF’s 2026 country dataset Currency Uzbek soum, UZS Nominal GDP Approximately US$147.0 billion in 2025; IMF projection of US$181.5 billion for 2026 Global nominal-GDP rank 63rd in the current IMF-based 2025 comparison, rather than the 50th-place premise in the original brief GDP growth 7.7% in 2025; IMF projection of 6.5% for 2026 GDP per capita Approximately US$3,968 in the World Bank’s 2025 data Digital-economy indicator Information economy and ecommerce contributed 4.08% of GDP in 2024 under the official statistical definition Ecommerce indicator Official ecommerce trade volume reached UZS15.21 trillion in 2024 Cards in circulation 74.6 million on 1 July 2026; not unique cardholders Important domestic networks Uzcard and Humo Current Uzcard scale More than 24.7 million cards, 265,000 terminals, 16,000 ATMs, 36 partner banks and 33 payment aggregators Current Humo scale More than 35 million cards, 184,000 terminals and 6,400 ATMs Mobile and app relevance Very high; bank and fintech applications mediate cards, transfers, bills and QR payments Emerging national QR layer UzQR entered into force on 1 July 2026 International-card relevance Essential for travel, cross-border customers and selected online buyers, but supplementary for broad domestic reach Recurring readiness

Strongest through explicitly supported stored-card or automatic-debit products; ordinary P2P and QR payments are primarily one-time Local-acquiring relevance High for domestic cards, UZS settlement, app integrations, refunds and reconciliation Strongest merchant opportunities Retail ecommerce, travel, education, gaming, SaaS, digital content and marketplaces Primary merchant takeaway Validate the complete domestic card stack—not merely whether the checkout has a generic card form Uzbekistan’s 2025 economy grew 7.7%, while the IMF projects 6.5% real growth and approximately 7% average consumer inflation in 2026. The economy’s current-dollar scale and per-capita income should be kept distinct: fast growth supports demand, but product pricing and likely transaction value still need to reflect local purchasing power. (IMF) The official information-economy-and-ecommerce measure rose from 3.56% of GDP in 2023 to 4.08% in 2024. It includes the information and communications technology economy, content and media activity, and ecommerce as defined by the National Statistics Committee; it is not a measure of all economic activity that happens to use digital technology. (Siat) Uzcard and Humo’s published totals should not be added together and treated as unique customers. Individuals can hold several cards, co-badged products can involve more than one network, and the Central Bank’s aggregate card total covers the wider banking market. (UZCARD)

The anatomy of an Uzbek online payment A generic card diagram normally shows three visible participants: Customer → card network → merchant That diagram is too simple for Uzbekistan. A more useful model has seven layers. Layer 1: the customer’s bank or payment application The application may control: * Login and device authentication. * The list of saved cards. * Card-to-card transfers. * QR scanning. * Utility and government payments. * Merchant-payment initiation. * Transaction notifications. * Virtual-card issuance. * Account balances. * Customer support. The customer may think, “I paid through my bank app” or “I paid through my payment app,” even when the underlying instrument is an Uzcard or Humo card. This changes merchant localization. Showing a recognized bank, app or domestic-network path can communicate more than a card-number field headed simply Credit or debit card. Layer 2: the credential The customer might select: * A physical Uzcard credential. * A virtual Uzcard card. * A Humo card. * A domestic card stored inside a payment application. * A co-badged Uzcard–Mastercard card. * A Humo–UnionPay product when issued and eligible. * A standalone Visa, Mastercard or UnionPay credential. * A bank account rather than a card. * An electronic-money balance. The credential determines where the payment can be processed and what authentication, refund or recurring functionality may be available. A card that works for local transfers is not automatically enabled for: * Ecommerce. * International purchases.

* Card-on-file. * Merchant-initiated transactions. * Recurring billing. * Foreign-currency processing. Layer 3: the domestic network Uzcard and Humo provide the local network and processing context for a large share of domestically issued cards. They are not user-interface applications. They sit below the customer-facing app and help determine how a credential is routed, authenticated and accepted. The merchant must therefore distinguish: * Uzcard acceptance * Humo acceptance * Visa or Mastercard acceptance * A co-badged card’s domestic side * The same card’s international side A merchant that supports the Mastercard side of a co-badged card has not necessarily integrated the Uzcard side for local ecommerce. Layer 4: the acquirer, processor or payment organization This participant can control: * Merchant onboarding. * Merchant-category eligibility. * Connection to Uzcard or Humo. * Gateway or API access. * Authentication. * Payment status. * Refund tools. * Settlement. * Reporting. * Technical support. The Central Bank’s register of payment organizations was updated in June 2026. A merchant should verify the entity performing each regulated payment function instead of assuming that the checkout brand, bank, processor and acquirer are the same company. (CBU) Layer 5: the merchant transaction The merchant must create a commercial payment, not merely observe money movement. A merchant-ready transaction should contain: * Order ID. * Exact UZS amount. * Product or service. * Customer reference.

* Method and network. * Provider transaction ID. * Authentication result. * Payment status. * Expiration. * Refund status. * Settlement reference. This is what separates a purchase from an informal card-to-card transfer. Layer 6: settlement and refund A customer can receive a successful payment message while the merchant still has to wait for: * Provider settlement. * Fee deductions. * Reserve deductions. * Currency conversion. * Merchant payout. * Bank availability. * Reconciliation. Refunds may follow a different technical route from payment initiation. A card payment may support an original-transaction refund through the provider; a transfer may require a separate outbound transaction. Layer 7: the international overlay Visa, Mastercard, UnionPay and other international systems matter for: * Tourists. * Foreign-issued cards. * Cross-border ecommerce. * International travel by Uzbek customers. * Co-badged credentials. * Foreign-currency purchases. * Global subscription services. The international overlay expands the market. It does not replace the domestic stack.

Economic position and merchant relevance Uzbekistan’s 2025 nominal GDP was approximately US$147 billion, placing it 63rd in the current IMF-based global table. The IMF projects current-price GDP of about US$181.5 billion in 2026, but that is a forecast for a different year and should not be substituted into a 2025 ranking. (IMF) The market’s commercial case rests on four factors: * Nearly 39 million residents. * Rapid economic growth. * Expanding formal retail and services. * Increasingly dense digital-payment infrastructure. Retail trade turnover reached UZS210.2 trillion during January–May 2026, 20.7% higher in nominal terms than in the corresponding period of 2025. Because the figure is nominal, part of the increase reflects price changes rather than only increased physical consumption. (Stat.uz) For merchants, Uzbekistan is not yet a mass market with Western-European transaction values. It is a fast-expanding consumer and services economy where local pricing, small-screen performance and method access can determine whether digital demand becomes paid demand. What the economic ranking means The rank should influence market prioritization, but not dominate it. A merchant should consider: * Total obtainable customers in the target vertical. * Average order value in UZS. * Payment-method eligibility. * Digital fulfilment versus physical logistics. * Refund and support cost. * Local-acquiring requirements. * Cross-border settlement. * Reusability across Central Asia.

Uzbekistan may be more attractive to a mobile gaming company, education platform or regional B2B service than to a high-priced subscription brand that requires internationally enabled recurring cards. Consumer-spending implications The World Bank’s 2025 GDP-per-capita figure was approximately US$3,968. That does not establish household disposable income, but it indicates why merchants should test several price points rather than import prices unchanged from richer markets. (Worldometer) Recommended pricing experiments include: * Lower one-time entry products. * Monthly rather than annual commitments. * Local bundles. * Student or education tiers. * Family plans. * Prepaid digital credit. * Smaller gaming packages. * Clearly disclosed instalments where offered by a regulated provider. The payment method and price should be designed together. A local card does not help if the product is still priced beyond the target customer’s usable balance.

Digital-economy maturity Uzbekistan’s official digital-economy indicator is narrower and more useful than a generic claim that the country is “digitalizing rapidly.” The National Statistics Committee reports that information-economy and ecommerce activities generated 4.08% of GDP in 2024, up from 3.56% in 2023 and 3.06% in 2022. The series is based on reporting and administrative data and follows the committee’s classification of ICT, content and media, and ecommerce activity. (Siat) Official ecommerce trade volume reached UZS15.21 trillion in 2024, compared with UZS13.26 trillion in 2023 and UZS10.89 trillion in 2022. The statistic is based on reporting forms and business surveys, so it should not be treated as a direct measurement of all consumer card spending or every informal social-commerce transaction. (Siat) A separate 2025 market guide citing Uzbek government data estimated 2024 ecommerce at about US$1.2 billion, or 3.8% of retail, and referenced a private forecast that ecommerce could reach 9%–11% of retail by 2027. The forecast is not an official outcome and is subject to economic, regulatory, platform and measurement uncertainty. (Trade.gov) A maturity profile is more informative than one percentage Uzbekistan’s payment maturity is visible in: * 74.6 million cards in circulation by July 2026. * Approximately 448,000 POS terminals. * More than 74 million remote-banking registrations by October 2025. * UZS646 trillion in 2025 mobile-application transaction value.

* Approximately 25 million electronic wallets at the end of 2025. * 139,000 registered QR codes in the 2025 payment ecosystem. * The national UzQR framework entering into force in July 2026. (CBU) None of these indicators is a unique-customer measure. One person can have: * Several cards. * Several bank applications. * Several app registrations. * A card on both domestic and co-badged networks. * One or more electronic wallets. The totals show infrastructure density, not the exact number of addressable ecommerce buyers. Mobile commerce is an architectural assumption Merchants should assume that many local customers will: * Discover the product on a phone. * begin checkout on a phone. * receive an OTP on the same device. * switch into a bank or payment app. * return to the merchant after authorization. A mobile checkout must preserve: * The basket. * Selected language. * Customer session. * Payment attempt. * Order state. * Return path. Desktop-compatible card acceptance is not enough.

Commercial growth prospects Retail ecommerce: strong immediate fit Retail ecommerce is the clearest broad consumer opportunity. The official ecommerce series has increased each year since 2020, while retail turnover continued expanding rapidly during the first five months of 2026. (Siat) Promising categories include: * Consumer electronics. * Fashion. * Beauty and personal care. * Household goods. * Children’s products. * Digital vouchers. * Cross-border retail. * Marketplace goods. Relevant payment methods: * Uzcard. * Humo. * International cards. * App-mediated domestic payment. * UzQR. * Bank transfer for selected orders. * Cash on delivery where commercially justified. * Instalment products offered through eligible providers. Operational priorities: * UZS pricing. * local-card support. * mobile checkout. * delivery verification. * exchanges and partial refunds. * promotion and price-expiration rules. * seller and product trust. Classification: Strong immediate fit. Travel and ticketing: high-growth opportunity Uzbekistan received 6.57 million foreign tourist visits during the first half of 2026, 24.9% more than during the corresponding period of 2025. Official reporting also recorded more than 5.35 million visits during the first five months and US$2.24 billion in tourism-service exports over that period. (O‘zbekiston Respublikasi Hukumat portali) Travel merchants need two payment configurations. Domestic traveller Prioritize: * Uzcard. * Humo. * local bank and fintech apps. * UzQR. * domestic transfers. * UZS.

* instalments where appropriate. International visitor Prioritize: * Visa and Mastercard. * UnionPay where supported. * global mobile wallets where available. * transparent UZS pricing. * foreign-card authentication. * multilingual support. * cash fallback where operationally relevant. Travel payment operations must support: * Deposits. * delayed capture where provider-supported. * partial refunds. * itinerary changes. * cancellation. * no-show evidence. * refund after the traveller leaves the country. Classification: Strong opportunity with significant cross-border and refund complexity. Education and testing: strong fit Uzbekistan’s expanding population, government digital services and demand for skills development support opportunities in: * Online courses. * language instruction. * examination preparation. * professional certification. * coding and technology education. * university-related services. * tutoring. * employer training. Payment characteristics: * Parent and student may be different parties. * Values range from small course purchases to substantial tuition. * Some products are one-time; others are monthly. * Instalments may matter. * Access may begin before the course finishes. * Refund rules can depend on attendance or content consumption. Recommended methods: * Uzcard and Humo. * UzQR. * app-mediated payment. * transfer or invoice for larger fees. * stored cards or specifically supported recurring products. Classification: Strong immediate fit. Gaming and digital goods: strong payment fit

Gaming and digital content align with the domestic payment environment because they can use: * Low-value UZS pricing. * domestic debit cards. * app-based payments. * QR. * instant fulfilment. * repeat transactions. * virtual cards. The payment risks are: * Account takeover. * card testing. * minor or family disputes. * immediate consumption. * virtual-item resale. * repeated low-value fraud. No sufficiently authoritative current national forecast was found for the complete Uzbek gaming market. The commercial recommendation is therefore based on payment and distribution fit rather than a precise market-size forecast. Classification: Strong payment fit; demand should be validated by game, audience and price point. SaaS and business services: high-value segment opportunity Uzbekistan reported US$940 million in IT-service exports in 2025, reflecting the expansion of its technology and outsourcing economy. The government’s Digital Uzbekistan 2030 strategy targets considerably larger IT-service exports, but that target should not be treated as a guaranteed forecast. (O‘zbekiston Respublikasi Hukumat portali) SaaS merchants should distinguish: * Consumer and freelancer plans. * SME subscriptions. * Annual domestic contracts. * Enterprise invoicing. * Export-oriented businesses. * Local UZS contracts. * USD or other foreign-currency contracts. Recommended methods: * Stored cards for self-service. * Uzcard and Humo for domestic one-time purchases. * provider-supported recurring products.

* bank transfer and invoice for enterprise contracts. * international cards for cross-border customers. Classification: Attractive for well-defined business segments. Marketplaces: high opportunity, higher regulatory burden Marketplaces can connect local buyers, small businesses and service providers, but the payment problem is larger than checkout. A marketplace must design: * Buyer acceptance. * Seller onboarding. * Payment allocation. * Refund ownership. * Seller reserves. * Payout timing. * Chargeback allocation. * Tax and receipt handling. * Fraud controls. * Prohibited-product controls. A platform that merely introduces buyers and sellers has a different regulatory and payment role from one that receives funds, holds balances and controls seller payouts. Classification: High opportunity, operationally complex.

How customers pay in Uzbekistan The relevant categories are: * Uzcard cards. * Humo cards. * Co-badged domestic and international cards. * Standalone Visa, Mastercard and UnionPay cards. * Bank and fintech applications. * UzQR and other QR experiences. * Card-to-card transfers. * Bank-account transfers. * Electronic-money wallets. * Cash and cash-on-delivery. * Provider-specific instalment or financing products. The merchant should not display all of these as if they were equivalent buttons. A customer may begin with the same Uzcard credential but complete through: * Direct card entry. * A saved-card application. * A QR request. * A card-to-card transfer. * A payment aggregator. * A co-badged international route. Each flow creates different merchant data and operating consequences.

Payment-method priority matrix Payment method General priority Best fit Principal limitation Uzcard ecommerce acceptance Launch essential for broad domestic commerce Retail, gaming, education, marketplaces, digital media and services Support depends on issuer, card product, acquirer, gateway and merchant category Humo ecommerce acceptance Launch essential for broad domestic commerce Same major domestic consumer verticals Online capabilities, authentication and refunds must be verified through the selected provider UzQR Early high-value addition; potentially essential as adoption develops Mobile retail, services, education, in-person and app-led commerce Newly implemented in July 2026; provider coverage, customer adoption and refunds require live testing Payment-app flow using domestic cards Launch essential or high-value Mobile commerce, repeat users and app-familiar customers App, card and provider eligibility vary Visa and Mastercard Essential supplement Tourism, international customers, travel, SaaS and co-badged credentials Does not replace Uzcard and Humo coverage UnionPay High-value or segment-specific Visitors, travel and co-badged products Customer and merchant coverage is provider-specific Co-badged cards Useful overlay Customers needing domestic and international capability Domestic and international sides can have different rules Structured bank transfer High-value addition B2B, tuition, annual SaaS and larger purchases Matching, fulfilment timing and refunds Card-to-card transfer

Usually unsuitable as the primary merchant flow Exceptional manual or informal collection Lacks normal merchant-acquiring data, order controls and structured refunds Electronic-money wallet Segment-specific Gaming, digital content, smaller purchases and selected apps Wallet count, active use, refunds and recurring support vary Cash on delivery Segment-specific Physical retail and trust-sensitive buyers Refusal, courier collection, settlement delay and return cost Instalment or financing product Segment-specific Electronics, travel, education and higher-value retail Underwriting, fee, regulation and refund complexity Provider-supported automatic debit High-value for subscriptions where available SaaS, education, memberships and media Must be confirmed at provider, issuer and card-product level Carrier billing Niche Selected low-value digital content Limits, revenue share and operator coverage Cryptocurrency Usually unnecessary for mainstream launch Specialist regulated use cases Regulation, volatility, accounting and refund complexity

Uzcard: the domestic network merchants cannot treat as optional Uzcard currently reports more than 24.7 million cards, 265,000 terminals, 16,000 ATMs, 36 partner banks and 33 payment aggregators. These are first-party network statistics and should be checked immediately before publication because they change as banks issue cards and deploy acceptance devices. (UZCARD) What Uzcard is Uzcard is a domestic payment system connecting issuing banks, processing infrastructure, acquirers, payment aggregators and merchants. Its capabilities have expanded over time to include: * Card payments. * ecommerce. * person-to-person transfers. * virtual cards. * NFC products. * co-badged international cards. * selected recurring or automatic debit services. * international-card acquiring through participating partners. (UZCARD) This does not mean every Uzcard credential supports every capability. A typical Uzcard ecommerce flow A structured flow may operate as follows: 1. The merchant creates an order in UZS. 2. The customer selects Uzcard or a local-card option. 3. The gateway collects or tokenizes the necessary credential. 4. The issuer or application authenticates the customer. 5. The domestic processing system routes the transaction. 6. The provider returns a verified status. 7. The merchant fulfils the order. 8. The acquirer or provider settles the transaction. 9. Any refund is connected to the original order. The merchant should confirm whether the flow is: * Direct card entry. * Hosted payment page.

* App-to-app authorization. * QR. * Tokenized repeat payment. * Merchant-initiated debit. * Card-to-card transfer. These are not interchangeable. Uzcard–Mastercard co-badging Uzcard–Mastercard products combine domestic and international functionality in one credential. Uzcard states that these cards can receive and transfer soum domestically while using Mastercard capabilities for international travel and online purchases. The Mastercard side may use 3-D Secure. (UZCARD) The operational distinction is crucial: * A domestic Uzbek merchant may route the card through Uzcard. * A foreign merchant may see a Mastercard credential. * Currency conversion and authentication can differ. * Refund routing can depend on the processed side. * Recurring capability must be confirmed for the route actually used. International-card acquiring through Uzcard Uzcard states that it works with international systems on co-badging and acquiring, allowing eligible global cards to be accepted through connected terminal and ATM infrastructure. This confirms physical infrastructure partnerships, not universal online-card gateway support for every merchant. (UZCARD) A merchant must separately verify: * Ecommerce acquiring. * Card-not-present support. * Merchant category. * currency. * authentication. * refunds. * recurring transactions. * settlement. Recurring-payment caution

Uzcard’s history identifies an Autopayment service launched in 2021 for recurring debits. That does not establish universal recurring support across every issuer, gateway, merchant category or card product. (Uzcard) Subscription merchants must test: * Initial consent. * token creation. * subsequent debit. * insufficient funds. * expired or replaced card. * cancellation. * full and partial refunds. * customer notifications.

Humo: a second domestic rail with its own ecosystem Humo describes itself as Uzbekistan’s national interbank card payment system. As of August 2026, its website reported more than 35 million issued cards, more than 184,000 terminals and over 6,400 ATMs. It also identified broad participation by Uzbek banks and promoted HumoPay and contactless functionality. (HUMO Payment System) Humo’s network totals overlap with customers who may also own Uzcard or international cards. They are not a separate population of 35 million unique buyers. What merchants must verify For Humo ecommerce acceptance, confirm: * Which Humo card products are supported. * participating issuers. * gateway or aggregator. * direct card entry versus app authorization. * UZS processing. * tokenization. * OTP or other authentication. * status callbacks. * partial refunds. * recurring support. * settlement. * reconciliation. Physical Humo acceptance does not automatically establish online Humo acceptance. HumoPay and app-mediated use Humo promotes mobile and contactless payment functionality, while the Central Bank reported that HumoPay had been integrated into the mobile applications of 20 banks by the end of 2025. This shows the importance of the application layer around the credential rather than merely the plastic card. (CBU) The merchant experience can still differ by: * Bank application. * customer device. * card product. * token. * provider. * authentication path. Humo’s international overlay

Humo announced a co-badged UnionPay–Humo product with Agrobank in July 2026. Customer issuance was planned for mid-August 2026, after the research cutoff for this guide, so the product should be described as announced rather than broadly available. The proposed product combines domestic Humo functionality with UnionPay use abroad and online. (HUMO Payment System) This illustrates a broader market trend: domestic credentials are acquiring international overlays while retaining their role inside Uzbekistan. International expansion of the card does not eliminate the need for merchants to support Humo domestically.

The payment application may matter more than the card logo Uzbekistan’s remote-banking statistics recorded more than 74 million registrations by October 2025. The table includes registrations across banks and does not deduplicate people who use several institutions. (CBU) The Central Bank reported UZS646 trillion of transactions through mobile applications in 2025, approximately 1.6 times the preceding year’s level. That total includes a broad range of financial activity, such as transfers, deposits, currency operations, repayments and payments; it is not merchant-checkout volume. (CBU) Why the application controls trust The application can show the customer: * Their available balance. * A familiar merchant name. * A saved card. * A payment request. * An OTP or biometric prompt. * A transaction receipt. * Support and dispute options. This creates a trust advantage that a foreign-hosted card form may lack. App-aware checkout design The merchant should determine: * Which applications support the selected method. * Whether a deep link is available. * whether a QR can be scanned from the same device. * whether the customer must copy a card number. * what happens when the app opens. * how the customer returns. * whether the merchant receives a callback. * whether the transaction can remain pending. * how the customer retries. A method shown to an ineligible customer creates abandonment rather than localization. Saved card does not always mean tokenized merchant card

A saved domestic card inside a payment app may be stored by the application, not the merchant. The app can initiate a new customer-authorized transaction without giving the merchant a reusable token. This distinction affects: * Subscriptions. * one-click repeat purchases. * merchant-initiated transactions. * account updating. * portability to another provider.

A purchase is not the same as a card-to-card transfer Card-to-card transfers are familiar in Uzbekistan and are often embedded in bank and payment applications. They can feel like payments because a customer sends money using: * Card number. * telephone number. * saved beneficiary. * application contact. * QR-like instruction. But a P2P transfer is not automatically merchant acquiring. A merchant payment normally provides * Merchant identity. * order amount. * order reference. * authorization result. * processor confirmation. * merchant statement. * refund linkage. * commercial transaction classification. A P2P transfer may provide only * Sender. * recipient card or account. * amount. * transfer reference. * timestamp. * brief purpose. In 2026, the Central Bank issued guidance on adding transfer-purpose information to P2P flows in mobile applications. Even with a purpose field, the transfer remains different from a structured merchant transaction. (CBU) Risks of accepting informal transfers * Incorrect amount. * missing order reference. * payment after order expiry. * fake screenshot. * payment from a third party. * duplicate payment. * fulfilment before confirmation. * refund request to another card. * manual reconciliation. * unclear commercial classification. A merchant using transfer-based collection should build: 1. A unique order reference. 2. Exact UZS amount. 3. Payment deadline. 4. Server or bank confirmation. 5. Matching rules. 6. Duplicate handling. 7. Beneficiary-verification controls for refunds.

8. Finance reconciliation.

UzQR and QR payments Uzbekistan introduced the unified UzQR payment-acceptance framework on 1 July 2026. The Central Bank said the system allows commerce and service businesses to register QR stickers remotely and view real-time transaction information and reports through a merchant account. (CBU) UzQR is a significant development because it can standardize a customer experience that had previously depended more heavily on provider- or bank-specific QR implementations. The 2025 QR base Before UzQR’s launch, the Central Bank reported approximately 139,000 QR codes in the payment ecosystem at the end of 2025. That figure should not be interpreted as UzQR adoption because the unified national framework entered into force later. (CBU) A merchant-ready UzQR flow A good implementation should include: 1. Merchant creates an order. 2. Provider produces an order-linked QR. 3. Customer scans through an eligible application. 4. Customer verifies merchant and amount. 5. Customer authenticates. 6. Payment is processed. 7. Provider sends verified confirmation. 8. Merchant changes order status. 9. Settlement and reconciliation records are created. 10. Refund connects back to the transaction. Static versus dynamic QR A static sticker can be appropriate for: * Physical stores. * fixed merchant identity. * customer-entered amounts. A dynamic QR is normally better for ecommerce or order-based services because it can contain: * Exact amount. * order ID. * expiry. * merchant reference. What remains unproven

Because UzQR is new, merchants should not assume: * Every relevant customer app supports it. * all gateways expose an API. * dynamic ecommerce QR is available from every provider. * refunds work consistently. * partial refunds are supported. * transaction reporting is standardized across providers. * recurring payments are possible. These capabilities require production testing. Fee structure The Central Bank published a fee structure for the national QR system that includes a domestic-system component when payment uses Uzcard or Humo. Because tariffs and commercial acquiring terms can change, merchants should confirm the total merchant fee with their bank or payment provider rather than relying only on the system-level component. (CBU)

Instant, clearing and interbank payment infrastructure Uzbekistan operates Central Bank interbank, instant-payment and clearing systems supporting transfers among financial institutions and payment services. In May 2026, the Central Bank’s clearing-settlement system processed approximately 15 million transactions worth UZS10.26 trillion. The measure covers broad clearing activity and is not a merchant-ecommerce share. (CBU) These systems matter to merchants because they support: * Transfers. * bill payment. * clearing between domestic systems. * card settlement. * payment-organization services. * increasingly interoperable QR acceptance. The merchant generally does not integrate directly with the central infrastructure. It contracts with a bank, acquirer, processor or registered payment organization that exposes an acceptance product.

International cards and co-badging Visa, Mastercard, UnionPay and other international cards are commercially important in Uzbekistan. They support: * International visitors. * Uzbek customers holding foreign-currency cards. * travel reservations. * foreign SaaS and digital services. * cross-border ecommerce. * global wallet credentials. * co-badged domestic cards. The Central Bank’s 2025 card-market review found growing product diversity, including virtual and co-badged cards. Its annual report said the number of co-badged cards reached 6.5 million at the end of 2025, approximately 1.4 times the previous year’s level. (CBU) Co-badging does not collapse two networks into one A co-badged card can contain: * A domestic-network function in UZS. * An international-network function for foreign or global acceptance. * different authentication systems. * different currency treatment. * different dispute rules. * different recurring capability. The processed side matters. International-card acceptance is not domestic-card acceptance A merchant supporting Visa and Mastercard may still miss: * Standalone Uzcard cards. * Standalone Humo cards. * local app flows using those credentials. * domestic QR. * domestic recurring products. * local refunds and settlement. Domestic acceptance is not international-card acceptance The reverse is also true. A local gateway advertising Uzcard and Humo does not automatically support: * Foreign Visa and Mastercard cards. * foreign-issued UnionPay. * 3-D Secure for all issuers.

* international currencies. * global refunds. * foreign-card recurring payments. Both layers must be validated.

Currency and pricing Uzbekistan’s official currency is the Uzbek soum, coded UZS. Common formats include: * 125 000 so‘m * 125,000 UZS * 125 000 сум For domestic consumer commerce, UZS pricing should be the default. Why UZS presentment matters Local pricing gives the customer: * A recognizable amount. * direct comparison with local alternatives. * clearer available-balance requirements. * fewer conversion surprises. * simpler refund expectations. * greater trust. A USD-only checkout can still work for international services or enterprise contracts, but it can narrow the reachable consumer segment. Separate the currency layers Merchants should define: * Presentment currency: what the customer sees. * Processing currency: what the provider receives. * Settlement currency: what the acquirer calculates. * Payout currency: what enters the merchant bank. * Reporting currency: what the merchant uses internally. * Conversion currency: what is exchanged. * Refund currency: what is returned. * Reserve currency: what the provider withholds. Accepting UZS does not prove that the merchant can receive USD, EUR or another payout currency. Exchange-rate context The Central Bank reported that the soum appreciated approximately 6.9% against the US dollar in 2025. The authorities continue moving toward a more flexible exchange-rate framework, so merchants should not assume that a recent direction of movement will persist. (CBU)

The provider’s commercial exchange rate can differ from the Central Bank reference rate because of: * Spread. * timing. * settlement cycle. * bank charge. * payout currency. * reserve conversion. Repatriation Official investment guidance describes legal guarantees for transferring and repatriating qualifying foreign-currency funds, subject to tax obligations, legal claims, insolvency and other restrictions. That is not a promise that every PSP will settle every foreign merchant offshore. (API Portal) Merchants must confirm: * Contracting entity. * local bank-account requirement. * UZS settlement. * conversion provider. * payout currency. * documentation. * tax clearance. * reserve treatment. * refund funding. * timing.

Local acquiring versus cross-border processing Cross-border processing can support a limited test A merchant may begin through an international PSP when: * Uzbekistan volume is small. * The target customers hold international cards. * Travel or foreign customers dominate. * UZS presentment is supported. * refunds work. * offshore settlement is acceptable. * domestic methods are not yet required. This is a market test, not a complete domestic strategy. Local processing becomes more relevant when * Uzbek residents provide most of the volume. * Uzcard and Humo are necessary. * UzQR is important. * app-mediated checkout is needed. * UZS settlement improves economics. * local refunds matter. * local customer support is required. * cross-border card cost is material. Capabilities that must be separated A provider may offer one without the others: * Local legal entity. * Uzbek bank account. * local acquirer. * domestic processing. * Uzcard. * Humo. * UzQR. * app integration. * international cards. * UZS settlement. * foreign-currency payout. * recurring payments. * marketplace payouts. A country-coverage page does not prove merchant eligibility or production access. Authorization-performance language Local acquiring may improve performance for some local-card and issuer combinations. It should not be presented as a guaranteed authorization uplift. Merchants should compare: * Issuer. * Uzcard versus Humo. * domestic versus international route. * direct card versus app. * authentication outcome. * new versus returning customer.

* order value. * merchant category. * provider. * currency.

Checkout localization Uzbek is the state language. Russian remains widely used in business and consumer communication. English is relevant for travel, technology, international education and B2B services. A broad domestic checkout should generally support: * Uzbek in Latin script. * Russian. * UZS. * Uzcard. * Humo. * mobile-app continuity. * local telephone formats. * clear local support. Language continuity Localization should continue through: * Product page. * basket. * card-entry page. * QR instructions. * bank or payment-app handoff. * authentication. * payment status. * receipt. * refund. * customer support. A translated checkout that redirects into an unexplained payment flow is not fully localized. Payment-method naming Avoid displaying only: Credit or debit card A clearer structure may be: * Uzcard * Humo * International card * UzQR * Bank or payment app * Bank transfer The exact labels should match provider functionality. Card-entry design Validate whether domestic cards require: * 16-digit PAN or another accepted format. * Expiry date. * CVV or no CVV. * telephone number. * SMS OTP. * application approval. * additional identity fields. Do not copy an international-card form and assume it works for every domestic product. Name fields Support: * Uzbek Latin-script names. * Cyrillic names. * long multi-part names. * optional patronymics. * business names. * foreign traveller names. Addresses Physical-goods merchants should support: * Region or viloyat. * district. * city or settlement. * street. * building. * apartment.

* delivery landmark. * postal code where used. Avoid blocking checkout because a customer does not conform to a Western address template. Telephone numbers Support: * Uzbek +998 numbers. * local formatting. * foreign numbers for tourists and international customers where relevant. Identity fields Banks and payment organizations may perform their own KYC. The merchant should not collect a passport number or personal identification number merely because the provider already knows it. Collect identity information only when required for: * Legal compliance. * high-risk fulfilment. * travel. * invoicing. * regulated products. * fraud investigation.

Authentication Uzbek customers may encounter: * SMS OTP. * 3-D Secure. * bank-application approval. * Face ID. * device binding. * payment-app PIN. * QR approval. * issuer fraud checks. The Central Bank required biometric identification in bank and payment-organization applications for new registration, password recovery and login from another device as an anti-fraud measure. (CBU) Who controls the experience Merchant controls * Amount. * currency. * merchant name. * order reference. * payment page. * return URL. * timeout. * error message. * retry offer. Provider or issuer controls * Customer authentication. * OTP delivery. * biometric verification. * available funds. * account risk decision. * final authorization. What merchants can improve * Pass accurate order and customer data. * preserve mobile sessions. * explain the next step. * keep the payment amount visible. * use verified callbacks. * poll pending transactions. * prevent duplicate orders. * provide a relevant fallback. What merchants cannot guarantee * OTP delivery. * issuer approval. * application availability. * customer balance. * international capability. * recurring enablement.

Recurring payments and subscriptions Uzbekistan’s card and app environment supports repeat digital commerce, but repeat use should not be confused with automatic recurring collection. Method Automatic recurring suitability Main limitation Tokenized international card Strong where issuer and provider support it Expiry, replacement, balance or credit, and issuer decline Tokenized Uzcard Provider- and issuer-dependent Must be validated for actual off-session merchant charging Tokenized Humo Provider- and issuer-dependent Cannot be assumed from one-time ecommerce support Uzcard Autopayment or supported debit product Potentially strong Availability differs by bank, provider and merchant category Payment-app saved card Not automatically recurring App may initiate only customer-approved transactions UzQR Generally one-time Customer ordinarily approves each payment Card-to-card transfer Not automatic Customer initiates each transfer Manual bank transfer Not automatic Matching and customer action every period Electronic wallet Provider-specific Stored balance does not imply merchant-initiated access Cash collection Not automatic Offline action for each billing cycle Subscription requirements Merchants should validate: * Initial customer consent. * token creation. * merchant-initiated transaction support. * recurring indicators. * notification. * account updater. * insufficient-balance behavior. * retry limits. * cancellation. * full and partial refund. * price changes. * UZS billing consistency. Suitable subscription verticals

* SaaS. * streaming. * gaming memberships. * education. * professional memberships. * subscription retail. Manual renewal as a fallback A merchant can send a monthly payment request through: * App. * QR. * invoice. * message. * transfer instruction. That can be useful, but it is a manual renewal, not automatic billing. The customer must understand whether the service renews automatically or requires action.

Refunds, reversals and disputes A payment method should not be classified as launch-ready until the merchant can refund it. Domestic cards For Uzcard and Humo, validate: * Authorization reversal. * full refund. * partial refund. * refund period. * original-card return. * replaced-card behavior. * closed-account behavior. * transaction reference. * merchant approval. * settlement adjustment. Do not assume that all domestic gateways expose the same refund API. International cards Visa, Mastercard and UnionPay may provide: * Reversal. * full refund. * partial refund. * network dispute. * chargeback. The actual process depends on the acquirer and processed network. Co-badged cards The merchant should determine which side processed the payment. A refund should follow the original route wherever possible. A payment processed through Mastercard should not be treated as if it were a domestic Uzcard transaction merely because both functions were printed on one card. QR and app payments A QR refund may be: * Provider-linked to the original transaction. * a separate transfer. * a return to a card. * a return to an account or wallet. Validate: * Destination. * partial refund. * limits. * timing. * merchant reference. * customer notification. P2P and bank transfers A refund is commonly a new outgoing transaction. Controls should include: * Verification of original payer. * destination matching. * refund approval. * high-value dual authorization. * fraud checks. * original-order link. * outgoing transfer reference.

Never redirect a refund to a new beneficiary solely because the customer asks through email or chat. Dispute models differ Domestic card schemes, international card networks, transfers and QR payments do not offer identical customer-claim rights. The merchant should separate: * Financial reversal. * scheme dispute. * consumer complaint. * merchant refund. * fraud report. * bank investigation.

Settlement and treasury Payment success is not the same as usable merchant funds. A transaction can pass through: 1. Customer approval. 2. Issuer or app confirmation. 3. Network processing. 4. Acquirer settlement. 5. PSP payout. 6. FX conversion. 7. Merchant bank availability. Settlement questions Before launch, document: * UZS settlement. * payout currency. * payout bank. * local-account requirements. * payout frequency. * cut-off time. * weekends and holidays. * minimum payout. * reserve. * refund funding. * chargeback deductions. * provider commission. * FX spread. * gross versus net reporting. Domestic-network economics The merchant should obtain separate pricing for: * Uzcard. * Humo. * UzQR. * international cards. * app-based payment. * bank transfer. * instalment products. A low headline fee may be offset by: * Settlement delay. * manual reconciliation. * refund cost. * reserve requirements. * currency conversion. * support burden. Reconciliation Each successful order should map to: * Merchant order ID. * provider transaction ID. * domestic or international network. * issuer or app where available. * gross amount. * fee. * refund. * net settlement. * payout batch. * accounting entry. This becomes especially important when the same card is accepted through direct entry, an app and a co-badged international route.

Payment regulation and licensing Uzbekistan’s Law No. LRU-578 on Payments and Payment Systems took effect in February 2020 and provides the central legal framework for payment systems, operators and payment organizations. (LEX.UZ) The Central Bank maintains current registers of payment-system operators, payment organizations and electronic-money systems. Merchants should verify the regulatory status of every partner performing acquiring, processing, payment initiation, wallet or money-movement functions. (CBU) Ordinary merchant versus payment provider A merchant selling its own products does not automatically become a payment organization. The analysis changes when a company: * Holds customer balances. * Issues electronic money. * Operates a wallet. * receives payment for third-party sellers. * controls seller payouts. * facilitates transfers. * performs acquiring. * converts or remits customer funds. Marketplace responsibilities A marketplace should map: 1. Who sells to the buyer? 2. Who appears on the receipt? 3. Who accepts payment? 4. Who holds funds? 5. When does the seller become entitled to payment? 6. Who approves refunds? 7. Who bears chargebacks? 8. Which regulated provider moves the money? 9. Who performs seller KYC? 10. Who reports the transaction for tax purposes? KYC and AML Banks, payment organizations and other regulated institutions have KYC, transaction-monitoring and anti-money-laundering duties. A merchant may also need verification for: * High-value goods. * travel.

* regulated services. * marketplace sellers. * suspicious refunds. * business-account transactions. The merchant should avoid duplicating provider KYC unless it has a separate reason to collect the information. E-commerce regulation Uzbekistan’s Law on Electronic Commerce regulates relevant online commercial activity. Additional notification and operating requirements have evolved for ecommerce operators, and 2026 amendments should receive current local legal review. (LEX.UZ) This article provides general information and does not constitute legal, regulatory, tax or accounting advice. Merchants should confirm applicable obligations and operating requirements with qualified advisers and relevant payment partners.

Personal data and localization requirements Uzbekistan’s Personal Data Law includes a localization provision requiring personal data of Uzbek citizens processed through information technologies, including the internet, to be collected, systematized and stored using technical means physically located in Uzbekistan. (LEX.UZ) The law was amended in March 2026. The exact effect of the amendments and their interaction with payment processing, fraud tools, cloud hosting and multinational group access should be reviewed before launch. (LEX.UZ) Payment teams should document: * Fields collected. * purpose. * consent or legal basis. * local storage. * overseas processors. * PSP access. * issuer access. * fraud-provider access. * retention. * deletion. * encryption. * incident response. * customer rights. Data minimization Do not collect: * Full identity documents. * personal identification numbers. * unnecessary address fields. * bank data not required for payment. The merchant should let the regulated payment provider authenticate the customer where possible.

Tax and invoicing context Uzbekistan’s standard VAT rate is 12%. Category-specific exemptions, zero-rating and special treatment can apply, so merchants should not automatically add 12% to every order without tax analysis. (Invest Uzbekistan) Foreign electronic services Foreign suppliers and foreign intermediaries providing electronic services to customers in Uzbekistan can have VAT-registration and remittance responsibilities under the Tax Code. Official guidance states that when electronic services are supplied through a foreign intermediary, the intermediary can become responsible for VAT calculation and payment and may need to register with the Uzbek tax authorities. (API Portal) This can affect: * SaaS. * streaming. * gaming. * digital media. * online advertising. * cloud services. * automated education. * electronic marketplaces. Receipts and electronic invoices Uzbekistan uses electronic invoices, online cash-register systems and virtual cash-register infrastructure. Payment and accounting systems may need to connect: * Merchant. * customer where required. * product. * UZS amount. * VAT. * discount. * payment method. * transaction reference. * refund. * credit adjustment. * settlement. Exact invoice and fiscal-receipt requirements depend on the merchant’s entity, tax status, product and customer. Merchant of Record A Merchant of Record structure changes: * Seller identity. * card descriptor. * payment acceptance. * tax registration. * invoice. * refund. * dispute ownership. * settlement.

The arrangement should be reviewed specifically for Uzbekistan.

Fraud and payment risk Uzbekistan should not be characterized as inherently high risk. The relevant risks arise from: * App use. * account takeover. * card-not-present transactions. * informal transfers. * marketplaces. * immediate digital fulfilment. * refund processes. The Central Bank introduced Face ID for sensitive application events such as new registration, password recovery and login from another device to reduce card-related fraud. It also reported a substantial increase in appeals concerning unauthorized credit and theft involving bank cards, which are complaints rather than a national merchant-loss rate. (CBU) Domestic-card risk Monitor: * Stolen card data. * OTP interception. * card testing. * app-account takeover. * family disputes. * unrecognized subscription. * refund abuse. Transfer risk Monitor: * Edited screenshots. * wrong amount. * wrong recipient. * third-party payer. * transfer after expiry. * refund-redirection request. * invoice manipulation. * account takeover. QR risk Monitor: * Replaced QR stickers. * malicious QR destinations. * incorrect merchant name. * duplicate callbacks. * payment-status spoofing. * fulfilment before confirmation. Marketplace risk Monitor: * Fake sellers. * counterfeit goods. * prohibited products. * off-platform payment. * seller takeover. * mule payout accounts. * buyer-seller collusion. * refund manipulation. Gaming and digital-content risk Monitor: * Low-value velocity. * credential testing. * account takeover. * consumed content. * virtual-item resale. * household disputes.

Operating controls Recommended controls include: * Server-confirmed payment status. * idempotency. * amount matching. * expiry. * device and account history. * velocity limits. * refund-destination controls. * seller verification. * delivery evidence. * transaction alerts. * method-specific risk rules.

Provider landscape and operating models Model Strongest use case Main trade-off Global PSP International cards, fast market test and regional reuse Uzcard, Humo, UzQR and UZS settlement may be limited Local bank or acquirer Domestic cards, UZS settlement and local support Local contracting, integration and bank requirements Registered payment organization or aggregator Multi-bank, app, card and payment-service access Coverage and capability differ by organization Uzcard-connected processor Domestic Uzcard acceptance Humo and international layers require separate confirmation Humo-connected processor Domestic Humo acceptance Uzcard and international layers require separate confirmation UzQR provider Unified QR acceptance New service; ecommerce APIs and refunds must be tested Payment-app integration Familiar mobile customer experience Provider dependency and limited token portability Payment facilitator Marketplace and sub-merchant acceptance Seller KYC, reserves, fund control and payouts Merchant of Record Another entity manages the customer sale and selected payment or tax duties Less merchant control and different margins Payment orchestration Several domestic and international providers Added technical and reconciliation complexity Direct scheme integration Very large merchant requiring deep control Highest certification, maintenance and operating burden Provider due diligence Confirm: * Merchant-category eligibility. * Contracting entity. * Uzcard ecommerce. * Humo ecommerce. * UzQR. * app-to-app payment.

* international cards. * co-badged routing. * tokenization. * recurring support. * full and partial refunds. * UZS settlement. * payout currencies. * local bank account. * reserve terms. * marketplace seller payouts. * reporting. * data localization. * technical support. * current Central Bank registration.

Payment strategy by vertical Vertical Launch payment foundation Uzbekistan-specific configuration Main operating risk Retail ecommerce Uzcard, Humo and international cards App flow, UzQR, UZS, COD and exchanges Delivery refusal, return fraud and refund complexity Travel Domestic and international cards Local apps for residents, foreign cards for visitors Cancellation, FX, foreign issuers and delayed refunds Education Uzcard, Humo, UzQR and transfer Parent/student payer, invoices and instalments Access before payment, partial refunds and recurrence Gaming Domestic cards, app payment and QR Small UZS packages and instant confirmation Account takeover and consumed digital goods Digital media Stored cards and app payment Manual local-card renewal where recurring is unavailable Renewal failures and subscription disputes SaaS Cards, transfer and invoice UZS self-service, foreign-currency enterprise plans Recurring support, FX and tax allocation Marketplaces Domestic cards, QR and transfer Seller KYC, reserves, payout and refunds Fund control and seller fraud B2B services Bank transfer, invoice and corporate card UZS references and foreign-currency contracts Matching, documentation and settlement

Payment-performance measurement Uzbekistan requires merchants to measure the stack, not only the country average. Metric Recommended definition Checkout conversion Completed orders ÷ checkout sessions Domestic-card visibility rate Eligible sessions showing Uzcard or Humo ÷ eligible sessions Method selection rate Method selections ÷ sessions displaying that method Method completion rate Successful payments ÷ attempts initiated with the method Uzcard success rate Confirmed Uzcard payments ÷ Uzcard attempts Humo success rate Confirmed Humo payments ÷ Humo attempts International-card authorization rate Approved authorizations ÷ international-card authorization requests App handoff completion Successful payments ÷ bank or payment-app handoffs App return rate Successful returns to merchant ÷ app handoffs QR completion rate Confirmed QR payments ÷ QR attempts Transfer match rate Automatically matched transfers ÷ transfers received Authentication success Completed authentication events ÷ authentication events started Recurring success rate Successful scheduled charges ÷ scheduled charges attempted Completed-order rate Paid, accepted orders ÷ customers entering checkout Technical-error rate Technical failures ÷ payment attempts Refund rate Refunded orders or value ÷ completed orders or captured value Refund completion time Time from merchant approval to customer-accessible funds Chargeback or dispute rate Disputes ÷ relevant card transactions or value Fraud-loss rate Confirmed fraud loss ÷ processed value

Cost per successful payment Payment cost ÷ successful payments Cost per retained order Payment, fraud, refund and dispute cost ÷ retained orders Settlement delay Time from customer confirmation to usable merchant funds Reconciliation exception rate Unmatched settlement entries ÷ settlement entries Support-contact rate Payment-related contacts ÷ attempts or completed orders Retained revenue Revenue after fees, fraud, refunds, tax and FX costs Segment by: * Uzcard. * Humo. * UzQR. * international card. * co-badged route. * payment application. * issuer. * provider. * local versus cross-border processing. * direct card versus app-mediated payment. * mobile versus desktop. * Uzbek versus Russian. * domestic versus foreign customer. * one-time versus recurring. * new versus returning customer. * order value. * vertical. * checkout version. Do not combine Uzcard and Humo into one “local card” rate if the purpose is to diagnose performance.

Launch recommendations by merchant stage Merchant testing demand Launch: * UZS pricing. * Uzbek and Russian mobile checkout. * Visa and Mastercard if already available. * At least one provider capable of genuine Uzcard and Humo ecommerce. * Reliable refunds. * Clear settlement. * Country-specific success criteria. The test is incomplete if only internationally enabled customers can pay. Merchant launching Uzbekistan Add: * Full Uzcard coverage. * Full Humo coverage. * app-aware checkout. * UzQR where provider readiness is demonstrated. * local customer support. * domestic method-specific refunds. * UZS reconciliation. * tax and receipt readiness. Merchant scaling volume Evaluate: * Local acquiring. * Multiple payment organizations. * Additional app integrations. * payment orchestration. * provider redundancy. * local tokenization. * settlement optimization. * marketplace or seller-payout infrastructure. Merchant optimizing performance Investigate: * Uzcard versus Humo. * issuer. * app. * direct entry versus app. * OTP and biometric failure. * UzQR completion. * mobile return. * refund time. * domestic versus international route. * provider fees. * retained revenue. Merchant introducing subscriptions Prioritize: * Tokenized credentials. * explicit recurring support. * correct consent. * provider-supported automatic debit. * failed-payment recovery. * price-change notification. * easy cancellation. * manual app or QR renewal only as a fallback. Merchant expanding across Central Asia Reuse: * Order architecture. * card vault.

* fraud engine. * refund service. * payment-status model. * provider abstraction. * finance reporting. Configure separately for each country: * Domestic networks. * currency. * QR. * bank apps. * tax. * data rules. * settlement. * language. Uzcard and Humo integration creates Uzbekistan coverage, not automatic Central Asian coverage.

Uzbekistan launch checklist * Confirm the current nominal-GDP rank and economic year. * Define the target customer and likely UZS order value. * Confirm merchant-category eligibility. * Present domestic prices in UZS. * Support Uzbek and Russian checkout. * Validate Uzcard ecommerce—not merely Uzcard P2P. * Validate Humo ecommerce—not merely Humo terminal acceptance. * Confirm which issuers and card products are supported. * Distinguish domestic cards from international cards. * Distinguish co-badged domestic and international routing. * Add Visa and Mastercard for visitors and internationally enabled customers. * Evaluate UnionPay for relevant visitor and co-badged use cases. * Test bank and fintech application handoffs. * Preserve the session during app switching. * Verify whether a saved app card creates a merchant token. * Evaluate UzQR with live provider capabilities. * Use dynamic, order-linked QR where possible. * Do not fulfil from a screenshot. * Distinguish merchant payment from card-to-card transfer. * Use unique references for transfers. * Test OTP, 3-D Secure and biometric flows. * Test pending and timeout behavior. * Test authorization reversals. * Test full and partial Uzcard refunds. * Test full and partial Humo refunds. * Test international-card refunds. * Test QR refunds. * Verify beneficiary controls for transfer refunds. * Confirm recurring support separately for each method. * Do not describe repeat app payment as automatic billing. * Compare local and cross-border processing.

* Confirm UZS settlement. * Confirm foreign-currency payout. * Confirm local bank-account and entity requirements. * Confirm reserves, fees and payout schedule. * Reconcile the network, provider, order, refund and payout IDs. * Review the Payments and Payment Systems Law. * Verify every provider in the current Central Bank register. * Review marketplace fund flows. * Review KYC and AML allocation. * Review ecommerce-operator requirements. * Review VAT and foreign electronic-service obligations. * Review electronic invoice and receipt requirements. * Review personal-data localization. * Minimize unnecessary identity collection. * Prepare card, app, transfer, QR and marketplace fraud controls. * Define metric denominators. * Segment Uzcard, Humo and international-card performance. * Assign payment, product, finance, tax, legal, data, fraud and support owners. * Establish a formal post-launch review date.

Frequently asked questions Are Visa and Mastercard enough for Uzbekistan? No, not for a broad domestic strategy. They can serve foreign visitors, international-card holders and the international side of co-badged products. Many customers rely on standalone Uzcard and Humo credentials or local application flows, so international-card support should supplement—not replace—domestic acceptance. Is Uzcard a bank card or a payment network? Uzcard is a domestic payment system. Banks issue Uzcard credentials, while processors, aggregators and acquirers connect them to merchants. Is Humo the same as Uzcard? No. Humo is a separate domestic payment system with its own cards, processing arrangements, participating banks and merchant infrastructure. A merchant should test both independently. Can a co-badged card be processed as either a domestic or international card? Potentially, depending on the product and merchant route. A co-badged Uzcard–Mastercard card can function domestically through Uzcard and internationally through Mastercard. The merchant should identify which side was processed because currency, authentication, refund and dispute rules can differ. (UzCard API) Is a card-to-card transfer a valid ecommerce payment? It can move money, but it lacks many features of structured merchant acquiring. A merchant relying on transfers needs its own order matching, confirmation, expiration, refund and reconciliation controls. What is UzQR?

UzQR is Uzbekistan’s unified national QR payment-acceptance system, whose operating framework entered into force on 1 July 2026. Merchants can register QR stickers and access transaction reports through its system. Its actual consumer-app coverage and merchant APIs should be verified with the selected provider. (CBU) Can Uzcard and Humo support subscriptions? Some card and provider combinations may support tokenized or automatic debit, and Uzcard has developed an Autopayment service. Ordinary card entry, app payment, QR and P2P transfer should not be assumed to support off-session recurring billing. Test the exact issuer, processor, product and merchant category. Does a foreign merchant need an Uzbek entity? Not under every model. Entity, bank-account, local-acquiring, domestic-network, UZS settlement, tax and data requirements are separate. The answer depends on the provider, merchant category and flow of funds. Can a foreign merchant receive settlement outside Uzbekistan? Some providers or operating models may support foreign-currency or offshore payout. UZS acceptance alone does not prove that capability. Contracting, conversion, documentation, tax and repatriation should be confirmed in writing. Which language should checkout use? Uzbek in Latin script and Russian provide the strongest broad domestic baseline. English should be added where travel, international education, SaaS or foreign customers justify it.

Final merchant recommendation Uzbekistan should be prioritized by: * Retail ecommerce merchants. * Travel and ticketing companies. * Education and testing platforms. * Gaming and digital-goods businesses. * SaaS and professional-service providers. * Marketplaces. The first launch layer should include: 1. UZS pricing. 2. Uzbek and Russian mobile checkout. 3. Genuine Uzcard ecommerce acceptance. 4. Genuine Humo ecommerce acceptance. 5. International cards as a supplementary layer. 6. App-aware authentication and return flows. 7. Provider-confirmed payment status. 8. Full and partial refund operations. 9. UZS settlement and transaction-level reconciliation. The second layer should follow the merchant model: * UzQR for mobile and physical acceptance as provider and customer coverage matures. * Stored cards or automatic-debit products for subscriptions. * Structured bank transfers for tuition, SaaS and B2B. * Instalment products for appropriate higher-value retail or education. * International cards and currencies for travel and cross-border customers. * Seller onboarding, reserves and payouts for marketplaces. * Payment orchestration as domestic and international integrations multiply. Before committing significant resources, merchants must validate: * Uzcard issuer and product coverage. * Humo issuer and product coverage. * app eligibility. * authentication. * UzQR production readiness. * domestic versus international routing. * full and partial refunds. * recurring functionality. * local acquiring.

* UZS settlement. * foreign-currency payout. * personal-data localization. * VAT and invoicing. * fraud-adjusted retained revenue. Uzbekistan’s defining payment fact is not simply that local cards are popular. It is that the card credential sits inside a wider system of banks, applications, domestic networks, processors, QR infrastructure and customer habits. A merchant sees a payment button. The customer sees the application and financial institution they already trust. Launch for the complete domestic card stack. Add international cards around it—not instead of it.

Editorial basis: the uploaded Uzbekistan country brief. The brief listed Uzbekistan as the world’s 50th-largest economy. The current IMF-based 2025 comparison places it 63rd, with nominal GDP of about US$147.1 billion, so this guide uses the updated rank. Economic data, UzQR implementation, provider coverage, tax rules and settlement capabilities should be checked again immediately before publication. (Worldometer) Editorial recommendations package SEO title options 1. Uzbekistan Payment Methods: Uzcard, Humo and Merchant Guide 2. Payments in Uzbekistan: Uzcard, Humo, Apps and UzQR 3. Accepting Payments in Uzbekistan: A Guide for International Merchants 4. How Customers Pay in Uzbekistan: Uzcard, Humo and Bank Apps 5. Uzbekistan Ecommerce Payments: Domestic Cards, Apps and UZS Recommended SEO title Uzbekistan Payment Methods: Uzcard, Humo and Merchant Guide Recommended H1 Payments in Uzbekistan: Uzcard, Humo, and App-Led Domestic Commerce Meta description Understand Uzbekistan payment methods, Uzcard, Humo, UzQR, bank apps, international cards, UZS settlement, refunds, recurring payments and regulation. URL slug /payments/uzbekistan Alternative: /global-payments-atlas/uzbekistan Primary keyword Uzbekistan payment methods Secondary keywords * Payment methods in Uzbekistan * Accept payments in Uzbekistan * Uzbekistan ecommerce payments * Uzcard payments * Humo payments * UzQR payments * Uzbekistan online card payments * Uzbekistan payment apps * UZS payment processing * Uzbekistan local acquiring

* Uzbekistan recurring payments * Uzbekistan bank transfers * Uzbekistan payment gateway * Central Asia payment processing Related entities * Uzbek soum * Central Bank of Uzbekistan * Uzcard * Humo * UzQR * Common Republican Processing Centre * National Interbank Processing Centre * payment organizations * remote banking * co-badged cards * Mastercard * Visa * UnionPay * electronic money * ecommerce law * personal-data localization * value-added tax Search intent The primary intent is informational and commercial investigation. The reader is likely evaluating: * Which payment methods Uzbek customers use. * Whether Visa and Mastercard are sufficient. * How Uzcard and Humo differ. * Whether both domestic networks are necessary. * How payment applications change checkout. * Whether card-to-card transfers count as merchant payments. * How UzQR works. * Which methods support subscriptions. * Whether local acquiring is required. * How UZS settlement and foreign-currency payout work. * Which tax, data and licensing requirements apply. Article excerpt Uzbekistan’s familiar “card payment” label hides a domestic stack of Uzcard, Humo, bank applications, processors, QR infrastructure and transfer behavior. International merchants need domestic-card coverage and app-aware checkout—not merely Visa and Mastercard. Social description A merchant can accept global cards and still miss everyday Uzbek commerce. This guide explains Uzcard, Humo, payment apps, UzQR, UZS settlement and the full domestic card stack.

Internal-link recommendations

* How to expand payments into a new country. * International payment-expansion checklist. * Global payment gateway versus local PSP. * One global PSP versus multiple local PSPs. * How to select a PSP. * Payment orchestration for international expansion. * Local acquiring versus cross-border processing. * How to improve authorization rates. * Authorization rate versus payment conversion. * Why customer payments are declined. * QR payment integration. * Account-to-account payment flows. * Recurring-payment recovery. * Marketplace payment and payout operations. * Settlement and reconciliation. * Gaming payments. * Education payments. * Kazakhstan and other Central Asian payment guides. Suggested internal anchors include: * “accept Uzcard and Humo” * “compare local and cross-border processing” * “optimize domestic-card authorization” * “integrate QR payments” * “manage recurring-payment recovery” * “reconcile local payment settlements” * “build a Central Asian payment strategy” Authoritative external-source recommendations Maintain and refresh references from: * Central Bank of Uzbekistan for cards, terminals, remote banking, UzQR, payment organizations, mobile transactions, FX and regulatory updates. (CBU) * National Statistics Committee for GDP, ecommerce, population, retail and digital-economy indicators. (Siat) * IMF and World Bank for international economic comparison, forecasts and per-capita data. (IMF)

* Uzcard first-party documentation for network, card-product, ecommerce and co-badging functionality. (UZCARD) * Humo first-party documentation for network scale, HumoPay and co-badged developments. (HUMO Payment System) * LexUZ for payment and personal-data legislation. (LEX.UZ) * Tax and government authorities for VAT, foreign electronic services and fiscal-receipt requirements. (API Portal) Structured-data recommendation Use: * Article * BreadcrumbList * Organization * ImageObject * FAQPage for the visible FAQ section Recommended article properties include: * Headline. * description. * author. * reviewer. * publication date. * modified date. * publisher. * main image. * geographic focus. * citations. * breadcrumb position.

Original asset recommendations 1. Anatomy of an Uzbek Online Payment Purpose: Explain why a visible card button is only the top layer of the transaction. Intended reader: Product, payments, finance and expansion teams. Data required: * Customer application. * issuing bank. * credential. * Uzcard or Humo. * international overlay. * processor or payment organization. * merchant order. * settlement. * refund. Recommended format: Seven-layer flow diagram. Suggested flow: Customer → bank/payment app → card credential → Uzcard/Humo → processor/acquirer → merchant order → settlement/refund Add a parallel branch for: Co-badged card → Visa/Mastercard/UnionPay international route Placement: Immediately after the payment snapshot. Core message: A card payment in Uzbekistan is a stack, not a single integration. 2. Is This a Purchase or a Transfer? Purpose: Help operations teams distinguish merchant acquiring from P2P or account transfer. Intended reader: Product, support, fraud and reconciliation teams. Data required: * Merchant identity. * order reference. * payment confirmation. * transaction type. * refund function. * settlement record. * dispute model. Recommended format: Decision tree. Questions: 1. Was an order created? 2. Did the provider identify a merchant transaction? 3. Is the amount tied to the order? 4. Is confirmation server-side? 5. Can the original transaction be refunded? 6. Does it appear in merchant settlement reporting? Placement: Within the app and transfer section. Core message:

Money received is not automatically a merchant-ready payment. 3. Domestic Stack Versus International Overlay Purpose: Compare Uzcard, Humo, co-badged cards and international cards. Intended reader: Payments, travel, SaaS and cross-border teams. Data required: * Network. * domestic acceptance. * international acceptance. * ecommerce. * 3-D Secure. * recurring capability. * currency. * refunds. * acquiring. * customer segment. Recommended format: Capability matrix. Placement: Before the international-card section. Core message: International acceptance expands the domestic stack; it does not replace it.

Visual recommendations Hero image concept Show a clean international card form in the foreground. Behind it, reveal the infrastructure the form hides: * Uzbek bank application. * Uzcard. * Humo. * UzQR. * payment processor. * merchant order. * settlement ledger. Two arrows should show: * A domestic Uzbek customer entering through an app. * An international customer entering through Visa or Mastercard. Suggested headline: One Card Button Can Hide Two Different Payment Worlds Suggested caption: Uzbekistan’s domestic card networks and payment applications determine whether a globally standardized checkout reaches everyday customers. Alt text: “Uzbekistan payment stack showing Uzcard, Humo, payment apps, UzQR and international cards connecting to merchant checkout and settlement.” Avoid a generic Tashkent skyline, national flag or Silk Road image as the main visual. Diagram concept Title: From Uzbek Bank App to Merchant Funds Show: 1. Customer app. 2. saved Uzcard or Humo credential. 3. authentication. 4. domestic network. 5. processor. 6. merchant payment confirmation. 7. settlement. 8. refund. Include a warning: A customer screenshot is not the merchant’s source of truth. Chart concept Title: Uzbekistan’s Payment Infrastructure Is Larger Than Its Population Show separate, non-additive panels: * Population: 38.9 million. * Cards in circulation: 74.6 million. * Remote-banking registrations: more than 74 million by October 2025. * Uzcard cards: more than 24.7 million. * Humo cards: more than 35 million.

* Electronic wallets: approximately 25 million at end-2025. * QR codes in the 2025 ecosystem: 139,000. The caption must say: Cards, registrations and wallets are not unique-person measures and overlap substantially. Map concept Create a Central Asian systems map showing: * Uzbekistan: Uzcard, Humo, UzQR and UZS. * Kazakhstan: its card, banking-app and QR environment. * Other Central Asian markets as separate payment configurations. * A reusable merchant core across the region. Suggested caption: Central Asian expansion can reuse merchant infrastructure, but domestic card networks, currencies and settlement remain country-specific. Alt text: “Central Asia payment map showing Uzbekistan’s Uzcard, Humo and UzQR infrastructure connected to a reusable regional merchant payment core.”

Human review and contribution recommendations Required before publication Uzbekistan payments specialist Verify Uzcard, Humo, UzQR, card products, app flows, authentication, refunds and settlement. Uzbekistan legal or compliance reviewer Verify payment licensing, marketplace fund flows, KYC, AML, consumer rules and ecommerce-operator requirements. Uzbekistan tax reviewer Verify VAT, foreign electronic services, fiscal receipts, electronic invoices and Merchant of Record treatment.

Strongly recommended Local acquiring and processing specialist Review domestic routing, gateway coverage, issuer support and UZS settlement. Uzbek and Russian localization specialist Review payment terminology, checkout instructions, error messages and support language. Data-protection specialist Review personal-data localization, processor access and cross-border storage. Fraud specialist Review OTP fraud, app takeover, P2P screenshots, QR substitution, marketplace fraud and refund redirection. Operations and reconciliation specialist Validate status callbacks, transfer matching, refunds, settlement and provider reporting. Treasury specialist Review UZS conversion, payout currency, reserves and repatriation. Optional enhancement Uzbek retail, travel, education, gaming or SaaS merchant contributor Provide an approved first-hand observation about domestic-card completion, app handoff, refunds or UZS settlement. Recommended first-hand contribution Compare the same merchant offer through: * Direct Uzcard checkout. * Direct Humo checkout. * App-mediated domestic-card payment. * UzQR. * International card. Measure: * Eligibility. * selection. * completion. * authentication. * technical error. * refund time. * settlement time. * payment cost. * support contacts. * retained revenue. The contribution should be anonymized and should not imply that one merchant’s results represent the entire country.

Final fact-check list Reconfirm immediately before publication: 1. Uzbekistan’s current nominal-GDP rank. 2. 2025 nominal GDP. 3. 2026 projected nominal GDP. 4. Real-growth forecast. 5. Inflation forecast and latest observed inflation. 6. Population. 7. GDP per capita. 8. Information-economy and ecommerce share of GDP. 9. Official ecommerce trade volume. 10. Ecommerce share of retail. 11. Retail-growth figures. 12. Total cards in circulation. 13. Total POS terminals. 14. Total ATMs and self-service kiosks. 15. Uzcard card count. 16. Uzcard terminal and ATM count. 17. Uzcard partner-bank and aggregator count. 18. Humo card count. 19. Humo terminal and ATM count. 20. Remote-banking registrations. 21. Mobile-application transaction value. 22. Electronic-wallet count. 23. QR-code count and its definition. 24. UzQR participating institutions. 25. UzQR ecommerce and dynamic-QR support. 26. UzQR fee structure. 27. UzQR full and partial refunds. 28. Uzcard ecommerce issuer coverage. 29. Humo ecommerce issuer coverage. 30. Uzcard authentication. 31. Humo authentication. 32. Domestic-card tokenization. 33. Autopayment and recurring capability. 34. Co-badged-card count. 35. Uzcard–Mastercard routing. 36. Humo–UnionPay issuance status. 37. International-card ecommerce support. 38. Local-acquiring requirements. 39. Uzbek-entity requirements. 40. Local bank-account requirements. 41. UZS settlement. 42. Foreign-currency payout. 43. Conversion and repatriation. 44. Provider reserves and payout timing.

45. Payment-organization registration. 46. Marketplace fund-flow obligations. 47. KYC and AML allocation. 48. Personal-data localization. 49. Effect of the 2026 personal-data amendments. 50. Standard VAT. 51. Foreign electronic-service VAT. 52. Electronic invoice and fiscal-receipt obligations. 53. Tourism growth. 54. IT-service export claims. 55. Gaming and education opportunity claims.

Differentiation note This guide is commercially distinct because Uzbekistan’s payment challenge is not a shortage of cards. It is the difference between seeing a card and understanding the domestic card stack. The customer may recognize: * The bank. * payment application. * saved credential. * transfer experience. * QR scanner. The merchant must understand: * Uzcard or Humo. * issuer eligibility. * processor. * authentication. * order confirmation. * settlement. * refund. * international overlay. The central editorial recommendation is: Build for Uzcard and Humo first, design for the applications through which customers use them, and treat international cards as an additional access layer rather than the definition of card acceptance.