Finding payment providers in Uzbekistan starts with a practical question: which combination of payment method, transaction direction and customer experience does your business need?
UZCARD and HUMO are useful starting points. A shortlist becomes actionable when it explains how customers can pay, where business payouts can go, and what happens to the money after a transaction succeeds.
We reviewed 95 unique offer records linked exclusively to Uzbekistan in the PayStar export dated 14 September 2026. The sample contains 47 incoming-payment records and 48 outgoing-payment records. These observations describe recorded proposals; each provider still needs to qualify the proposed activity for your business.
What the Uzbekistan sample tells us
The currency split matters: 89 records list UZS and six list USD. All 47 incoming records list UZS; the outgoing records comprise 42 in UZS and six in USD. A search for Uzbekistan payment solutions therefore needs an explicit currency requirement.
Local method labels also overlap. HUMO appears on 42 records and UZCARD on 33, with 32 records carrying both labels. Together, they identify 43 distinct offers in this sample.
These figures help organise the search. They do not measure market share, count separate providers, or establish that every labelled offer supports merchant acquiring.
| Requirement | What to establish with the provider |
|---|---|
| UZCARD payment acceptance | Supported sales channel, customer flow and permitted business activity |
| HUMO payments | Exact operation offered, customer authentication and transaction confirmation |
| UZS payouts | Eligible recipient destination, required details, funding and limits |
| Settlement to your business | Receiving account, currency, timetable and charges |
The useful comparison is a set of confirmed capabilities for your intended operation.
Separate the card network from the customer experience
HUMO describes itself as a payment system based on bank cards and part of Uzbekistan’s payment infrastructure. Its business materials also describe terminal and contactless acceptance. This establishes the system’s role; the actual checkout offered to your customers requires a separate explanation from the PSP. HUMO system overview and business terminals.
A concrete example comes from UZCARD’s announcement of 29 June 2026. In the described TEZ QR flow, a customer scans a QR code displayed on a UZCARD terminal using the Uzum Bank app. The payment can use a linked UZCARD, Visa or HUMO card. UZCARD’s TEZ QR announcement.
That example combines three different elements: the terminal interaction, the mobile application and the funding card. It illustrates why “supports UZCARD and HUMO” needs more detail.
For your own checkout, request a demonstration covering the devices and channels your customers use. Establish whether the offer provides a hosted online payment page, an app-based flow, a terminal transaction or another arrangement. For any QR proposal, ask where the code appears, which apps can complete the payment and how your system receives confirmation.
The published terminal example is evidence of that particular flow. An online business needs confirmation of its own integration and acceptance scenario.
Treat UZS payouts as a separate requirement
The sample’s near-even split between incoming and outgoing records makes direction a useful first filter. Within the method-labelled records, HUMO appears on 19 incoming and 23 outgoing offers; UZCARD appears on 14 incoming and 19 outgoing offers.
A method can therefore appear on both sides of the search while describing different operations. Begin a payout discussion with the purpose of the payment and the intended recipient, then establish the supported destination.
Ask the provider to confirm:
- Whether the proposed payout reaches a card, bank account or another destination.
- Which recipient details and checks are required.
- Minimum and maximum transaction amounts, plus any cumulative limits.
- How the payout balance is funded and which currency is debited.
- What happens when a transfer remains pending, fails or is returned.
Keep refunds and new outgoing payments separate in the comparison. Request confirmation of the process available for each, including how it links to the original purchase where relevant.
Follow the money through to settlement
A customer-facing payment confirmation answers one operational question. Your finance team also needs a clear account of when proceeds become available to the business.
HUMO identifies the Central Bank’s Clearing Centre as performing national-currency settlement within its system. That description concerns the payment infrastructure. Your PSP agreement must specify the subsequent obligations owed to your business. HUMO’s settlement overview.
Compare the collection currency, payout funding currency and merchant settlement currency separately. Ask for the conversion point and exchange-rate basis wherever they differ. Confirm the receiving account, settlement cut-offs, minimum amounts, separate charges and treatment of non-working days.
Then evaluate the quote against your actual activity: small, typical and large transactions, expected transaction count and the balance required to keep payouts operating. This turns a list of fees into a usable operating comparison.
Build a focused Uzbekistan PSP shortlist
A useful brief includes your business activity, company registration country, sales channel, required methods, payment directions, transaction sizes, monthly volume and preferred settlement arrangements.
PayStar Discovery helps turn those requirements into a focused PSP shortlist with the commercial, technical and operating context needed to assess the next step.
You choose the provider and enter the agreement directly. The PSP remains responsible for approval, payment processing and settlement under that agreement.
Looking for payment providers in Uzbekistan? Share your requirements through PayStar Discovery so the comparison can focus on the UZCARD, HUMO and UZS operations your business actually needs.
Research basis: PayStar offer export dated 14 September 2026; public sources checked on 15 September 2026. The sample is an internal research dataset, not a live availability list.