UzCard & Humo Online Payments: A Simple Explainer
How UzCard Humo online payments actually work for Uzbek websites and apps, what they cost, and how they fit alongside Payme and Click.

If you sell anything online in Uzbekistan, sooner or later a customer asks: “Can I just pay with my card?” Not Payme, not Click — the actual plastic card in their wallet. That card is almost always a UzCard Humo online payments setup under the hood, and understanding how it works is the difference between a checkout that converts and one that quietly loses sales.
This guide breaks down what UzCard and Humo actually are, how they connect to your site or app, what it costs, and where they fit next to Payme and Click — without the jargon.
What are UzCard and Humo, exactly?
UzCard and Humo are Uzbekistan’s two national payment card systems — the local equivalent of Visa or Mastercard, but built and cleared domestically. Almost every bank card issued in the country runs on one of these two rails. That means when you say “accept card payments in Uzbekistan,” you are really talking about accepting UzCard and Humo, not international cards.
This matters for two reasons. First, coverage: between them, UzCard and Humo sit behind the vast majority of local salary cards, so if your checkout can’t process them, you are turning away the default payment method most people already have. Second, cost and settlement: transactions clear in so’m, through local rails, which keeps fees and settlement times predictable compared to routing through international card networks.
How they differ from Payme, Click, and Uzum Bank
It helps to think of it as two layers. Payme, Click, and Uzum Bank are wallets and payment apps — consumer-facing products people already have on their phones, together covering the large majority of everyday digital payments in the country. UzCard and Humo are the card rails underneath — the infrastructure that banks, wallets, and payment gateways all plug into. In practice, a well-built checkout usually offers both: a wallet button (Payme, Click) for speed, and a card form (UzCard/Humo) for customers who prefer typing a card number, especially on desktop or for larger business purchases.
How does a UzCard/Humo online payment actually work?
A typical flow looks like this:
- The customer reaches checkout on your site or in your app and selects “pay by card.”
- They enter card details (or use a saved card token) on a secure payment page — usually hosted by a licensed processor, not your own server, for security and compliance reasons.
- A one-time SMS code confirms the transaction (3-D Secure style verification), which is standard for both UzCard and Humo.
- The processor confirms success or failure back to your system, and you fulfil the order.
- Funds settle into your business account, typically within a few business days depending on your bank agreement.
The important detail: you rarely integrate directly with UzCard or Humo as a merchant. Instead, you integrate with a licensed local processor or a bank’s merchant gateway that already has UzCard/Humo certification, and it exposes an API you call from your website or app.
Where does PayTechUZ and similar libraries fit in?
For developers, this is where open-source unification libraries like PayTechUZ are useful — they wrap several Uzbek payment providers (including card processing and wallets like Payme and Click) behind one consistent interface, so your backend team doesn’t have to hand-write separate integrations for every provider from scratch. It doesn’t replace the need for a merchant agreement with a bank or processor, but it meaningfully cuts development time.
What does it cost to accept UzCard and Humo payments?
Costs come in two parts: what your provider charges per transaction, and what it costs to build the integration.
| Component | Typical range | Notes |
|---|---|---|
| Processor/merchant fee | Percentage per transaction | Varies by bank/processor and your volume; negotiate as volume grows |
| Simple payment button integration | 1 500 000–5 000 000 so’m | Ordering + payment flow into an existing site or Telegram bot |
| Full checkout with card + wallets + CRM sync | 5 000 000+ so’m | Multiple payment methods, receipts, CRM/1C sync, admin dashboard |
| Ongoing support/maintenance | from ~$50/month | Monitoring, updates, provider changes |
These are ranges, not quotes — actual pricing depends on your product’s complexity and the processor you choose.
A practical decision checklist
Before you commit to a payments integration, walk through this:
- Do you already have a bank/processor relationship, or do you need to apply for merchant status first?
- Will customers pay mostly by card, by wallet (Payme/Click/Uzum), or both — and does your checkout reflect that?
- Do you need recurring/saved-card payments (subscriptions, repeat orders)?
- Does the payment flow need to sync with your CRM (amoCRM, Bitrix24) or accounting (1C, MoySklad)?
- Is your order flow inside a Telegram bot, a website, a mobile app, or all three?
- Who handles PCI/security compliance for card data — you, or the processor’s hosted page?
If most of your traffic already comes through a Telegram storefront or bot — which is where a large share of Tashkent retail and food-delivery order volume actually happens — plan the card payment step so it doesn’t force people out of the chat and into an unfamiliar browser page, since that’s a common place checkouts lose customers.
Card payments vs. wallets: which should you prioritise?
There’s no universal answer, but a reasonable default: if your customers skew younger and mobile-first, wallets like Payme and Click convert faster because people already have the apps installed. If you sell higher-ticket items, serve corporate or older customers, or operate in a sector like education or logistics where invoicing by card is expected, a solid UzCard/Humo card flow matters more. Most serious e-commerce and service businesses in Tashkent and Samarkand end up supporting both rather than picking one — for a deeper walkthrough of the wallet side, see this guide to accepting online payments in Uzbekistan with Payme, Click, and Uzum.
If you’re weighing wallets specifically, these two are worth reading side by side: Payme integration for your website and app, and Click integration, a practical guide for Uzbek businesses. If Uzum Bank is also on your shortlist, this piece on Uzum Bank payments integration covers what to check before signing up.
Frequently Asked Questions
Do I need separate integrations for UzCard and Humo? Usually no — a licensed processor or bank gateway typically supports both under one API, since almost every local card runs on one of the two systems anyway.
Can international customers pay with UzCard or Humo? No — these are domestic card systems tied to local bank accounts. For foreign cards, you’d need a separate Visa/Mastercard-capable gateway.
Is it safe to store card numbers on my own server? Generally you shouldn’t. Reputable integrations use a hosted payment page or tokenisation so sensitive card data never touches your servers, which also simplifies compliance.
How long does a basic integration take? A focused card-plus-wallet checkout for an existing site or bot is typically a matter of weeks, not months, assuming your merchant account is already approved.
Getting card payments right is mostly about picking the right processor and designing a checkout that doesn’t lose people at the last step — small details like SMS confirmation flow or Telegram-native checkout can swing conversion noticeably. If you want a second opinion on your setup or need it built, take a look at our services and recent work, then get in touch and we’ll walk through what fits your product.
Building something like this?
Fera Tech ships iOS & full-stack apps end-to-end. Tell us about your project.
Start a project