# Payments in Uzbekistan: UZS fees and settlement terms for your business

Customers need a convenient way to pay. Your team needs a clear cost, a confirmed transaction status and money that can be reconciled to an order. In Uzbekistan, local card acceptance, sum-denominated payouts and contractual settlement should be discussed together.

PayStar already connects a wide range of payment methods. Ask Anastasia to help request options for your product in Uzbekistan and compare gateway terms. The figures below are a historical starting point, followed by the questions that turn interest in a GEO into a useful commercial brief.

## 95 offers: where to start your comparison

The snapshot dated 14 September 2026 contains **95 Uzbekistan-only offer records: 47 for collections and 48 for payouts**. Duplicate offer IDs have been removed. Multi-country records are excluded from this sample.

These are catalogue offers, not counts of independent providers, connected methods or currently available routes. A method name and several currencies attached to one record do not confirm every possible combination.

Start with the customer journey. Order payments require commercial acceptance, refunds and order matching; payouts require the correct beneficiary, a permitted purpose and final confirmation. Include UZCARD and HUMO in your brief as local card systems. Their use in merchant acquiring is illustrated by a [local bank’s acquiring page](https://kdb.uz/ru/corporates/local-terminals); this does not establish support by any particular gateway.

A card-to-card transfer and a purchase payment are not the same product merely because they use the same card. Request the precise service, contracting entity and eligible business model.

## UZS fees: compare the full economics

The mean stated **percentage fee component** in eligible UZS records is **7.52% for collections (n=46)** and **1.87% for payouts (n=39)**. Every record carries equal weight; transaction volumes are not used.

The median is **5.00% for collections and 2.00% for payouts**. The observed percentage-component ranges are **2.50–16.80%** and **0.00–4.00%**, respectively. These are boundaries of the historical sample, not an available price range for a new customer.

The calculation includes only records with an explicit UZS fee currency, a percent sign in the original description and a numeric, non-negative percentage. Of 47 collection records, one lacks an explicit percentage component. Of 48 payout records, six use another fee currency and three more lack an explicit percentage.

These means are neither market pricing nor a PayStar quote. They exclude fixed charges, currency conversion, minimum fees, reserves, refund costs and other charges. Even a zero percentage component does not establish that a transaction is free.

**Illustrative arithmetic, not a gateway offer.** On a 200,000 UZS transaction, “2% + 3,000 UZS” costs 7,000 UZS; “3% with no fixed charge” costs 6,000 UZS. At 600,000 UZS, those costs become 15,000 and 18,000 UZS. The break-even amount is 300,000 UZS. Comparing percentages alone would miss this difference.

Request a calculation for your average transaction and distribution of amounts, separately addressing successful, declined and refunded operations. Confirm whether charges are deducted from settlement or billed separately.

## Settlement: distinguish payment from available funds

Among the 47 collection records, the plain **T+0 label appears in 15** and T+1 in 14. Another 10 state other conditions, including one “T+0 on request”; eight have no term or a dash.

These labels describe stated terms, not measured speed. Conditional T+0 on request is not grouped with plain T+0. Customer payment approval, credit to a gateway balance and receipt by the merchant are different events.

Agree what starts T, the cut-off, time zone, business-day calendar, minimum withdrawal, frequency and possible holds. Confirm settlement currency separately: UZS acceptance proves neither settlement in UZS nor permission to transfer funds abroad.

For payouts, request the status lifecycle, finalization window, return of unexecuted funds and retry rules. A retry after a timeout should first check the original transaction to avoid creating a duplicate payout.

## Conversion: ask for evidence for your use case

This snapshot contains no measured average conversion rate. Offer counts, card-system familiarity and promises of quick payouts do not supply that missing evidence.

For a pilot, agree the denominator: created orders, opened forms or attempts submitted for processing. Compare equivalent traffic, amounts and periods, distinguishing bank declines, invalid details, incomplete customer actions and technical failures.

**Hypothetical calculation:** 820 successful results from 1,000 submitted attempts equal 82% by attempt. Assume those attempts cover 900 unique orders and each of the 820 successes belongs to a different paid order. Then 820 paid orders equal 91.11% by order. These are different metrics, not competing estimates of one result. This example does not describe any provider’s performance.

A useful report includes statuses and decline reasons, repeat attempts, time to a final outcome and amount reconciliation. This is more useful for planning than an unexplained headline percentage.

## What to request from a gateway

A short brief makes responses comparable. Supply your legal entity, incorporation country, product, website, average transaction, monthly volume and required directions. Share sensitive documents only through an agreed secure channel.

| Area | What the response should specify |
| --- | --- |
| Acceptance | UZCARD/HUMO or another precise method; supported journey, confirmation and refunds |
| Payouts | Eligible recipients and purposes, beneficiary checks and final statuses |
| Pricing | Percentage, fixed component, minimums, FX, refunds and reserves |
| Limits | Per transaction, day and month; collections and payouts separately |
| Settlement | Currency, schedule, cut-off, working days, holds and statements |
| Onboarding | Licences, documents, contracting entity, acceptance criteria and testing |

Do not carry approval for one product over to another. A store, a digital platform and a regulated service may receive different terms from the same provider.

## Uzbekistan licensing and product requirements

**The payment service.** The Law on Payments and Payment Systems provides for Central Bank licensing and prohibits payment services without the relevant licence, with an exception for payment agents and subagents. Check the counterparty’s actual role, current status and authorized activity, not just its logo. [Law ZRU-578, Articles 15 and 24](https://lex.uz/ru/docs/4575788), [Central Bank register](https://cbu.uz/en/payment-systems/registers/payment-organizations/).

**The underlying product.** From 24 September 2026, NAPP states that operators of electronic trading platforms, order aggregators and digital streaming services must register through its system. This is a separate notification regime for the specified categories; it should not automatically be attributed to every seller. [NAPP’s 24 September notice](https://napp.uz/ru/news/23-va-24-sentabrdan-elektron-tijorat-operatorlari-uchun-yangi-normalar-kuchga-kirishi-haqida-axborot-xabari).

**Special categories.** Organizing internet risk-based games, lotteries and bookmaking is subject to separate NAPP licensing. A payment-services licence does not replace a product licence or establish that a particular transaction is permitted. [Regulation No. 3638](https://lex.uz/docs/7615198).

**Cryptoassets.** The current PP-3832 prohibits their use as a means of payment or acceptance of payment except in cases established by legislation. Special regimes cannot be extended to every token or merchant: the exact exception and participant status must be checked, while relevant service providers are subject to NAPP licensing. [PP-3832](https://lex.uz/ru/docs/3806048), [NAPP licensing](https://napp.uz/en/pages/service-providers).

Legal sources were reviewed on 30 September 2026. Before onboarding, check current licences and applicable requirements for identification, data, currency transactions and the product itself. This overview is not a legal determination for a particular business.

## PayStar’s role

PayStar provides information and separately agreed technical services. **PayStar does not act as a bank or payment service provider (PSP).** PayStar does not organise payment acceptance or settlement in its own name: it does not receive, hold or settle customer or business funds. Its API, routing and monitoring tools support the agreed technical scope.

PayStar works only with lawful products and licensed products wherever licensing is mandatory. A GEO article is not approval of an activity or confirmation that a provider will onboard it. You choose the provider and enter the agreement directly. The PSP remains responsible for approval, payment processing and settlement under that agreement.

## Get details on Uzbekistan gateways

Ask Anastasia for terms for your use case: methods, fees, limits, settlement and product requirements. This helps turn a headline rate into a specific option you can discuss with a provider.

[Get details on Telegram](https://t.me/anastasiapaystar) · [Email Anastasia](mailto:Anastasia@PayStar.uk).

Information is provided free of charge. Integration, technical work and processing are discussed separately; availability is confirmed after product and documentation review.

## About the data

Commercial data was supplied by payment gateways and **has not been independently verified by PayStar**. It uses the historical snapshot of 14 September 2026; terms change weekly or more frequently and may already be outdated when read. Counts and arithmetic were checked against that snapshot; this does not verify the truth of gateway statements. Aggregates are not an offer, a complete price, a market-wide estimate or a guarantee of onboarding, conversion or settlement. Calculation examples are hypothetical. Current terms and legal status require separate confirmation.