Uzum Bank Payments Integration: What You Need to Know
A practical guide to Uzum Bank payments integration for Uzbek websites and apps — costs, timeline, docs, and how it compares to Payme and Click.
If you run a store, restaurant, or service business in Tashkent and your customers keep asking “do you take Uzum?”, you already know the answer matters more than it used to. Uzum Bank payments integration has become one of the fastest-growing requests we get from Uzbek businesses, right alongside Payme and Click support.
Uzum Bank has grown quickly on the back of the Uzum super-app ecosystem, and a growing share of shoppers — especially younger, mobile-first customers — expect to pay with it at checkout. This guide walks through what integration actually involves, what it costs, and how to decide if you need it now or can wait.
Why Uzum Bank matters alongside Payme and Click
Payme remains the market leader with 10M+ users, and Click holds a strong second place. Together with card rails like UzCard and Humo, these three cover the overwhelming majority of digital payments in Uzbekistan. Uzum Bank is the fast-growing challenger — pulled forward by the popularity of the Uzum marketplace and Uzum Bank’s own super-app push. For an online store or Telegram-based ordering bot, missing Uzum increasingly means losing a visible slice of checkout attempts, particularly from customers who already have the Uzum app installed for shopping or transfers.
The practical takeaway: if you already accept Payme and Click, adding Uzum Bank is usually the next logical step rather than a nice-to-have you can defer indefinitely.
What Uzum Bank integration actually involves
At a technical level, integrating Uzum Bank payments follows a pattern similar to Payme and Click: a merchant account and API credentials from Uzum, a server-side endpoint that creates and verifies transactions, and webhook handling for payment confirmation. If your team has already built a Payme or Click integration, adding Uzum is incremental work rather than starting from zero — much of the checkout UI, order state machine, and reconciliation logic can be reused.
The typical steps
- Register as a merchant with Uzum Bank and get sandbox/test credentials.
- Build (or extend) a backend payment service with endpoints for creating, checking, and cancelling transactions.
- Implement the webhook/callback handler that updates order status on payment success or failure.
- Add the checkout option in your website, mobile app, or Telegram bot flow.
- Test in sandbox, then apply for production credentials and go live.
- Reconcile transactions against Uzum’s reporting so accounting matches actual payouts.
A lean team can usually get a first working integration through sandbox testing within a couple of weeks; production approval timelines depend on Uzum’s own merchant onboarding process, which is outside a developer’s control.
Libraries that unify multiple providers
Rather than writing separate integrations for Payme, Click, and Uzum Bank from scratch, many Uzbek dev teams use unifying libraries such as PayTechUZ, which wrap the quirks of each provider’s API behind a common interface. This is often the fastest path if you expect to support more than one payment provider — which, in practice, most serious online businesses in Uzbekistan eventually do.
Payme vs Click vs Uzum Bank: a quick comparison
| Provider | Market position | Typical use case | Integration effort |
|---|---|---|---|
| Payme | Largest, 10M+ users | Default choice for most stores | Well-documented, many existing libraries |
| Click | Strong #2 | Common secondary option | Similar effort to Payme |
| Uzum Bank | Fast-growing challenger | Increasingly expected by younger/mobile shoppers | Comparable effort; smaller ecosystem of ready-made libraries |
| UzCard/Humo | Card rails, near-universal | Card checkout | Often bundled via a gateway or the above providers |
If you’re starting from zero, our guide to accepting online payments in Uzbekistan across Payme, Click, and Uzum walks through the bigger picture of choosing providers before you integrate any single one.
What it costs and how long it takes
Pricing for a payments integration project depends heavily on what you’re building it into — a plain website checkout, a full e-commerce backend, or a Telegram ordering bot. As a rough guide for the Uzbek market:
- A simple Telegram ordering bot without payments typically runs 500,000–1,500,000 so’m.
- Adding ordering plus one or more payment providers (Payme, Click, or Uzum Bank) typically moves that to 1,500,000–5,000,000 so’m.
- A CRM-connected bot or AI-agent-driven sales flow with payments is usually 5,000,000 so’m and up.
These are ranges, not quotes — the right number depends on your existing systems, how many providers you need, and whether you already have a backend to plug into. A focused payments integration MVP is realistically weeks of work, not months, when scoped tightly.
Checklist before you start
- Confirm your business is eligible to register as an Uzum Bank merchant
- Decide whether you need Uzum Bank alone or alongside Payme/Click
- Identify where checkout happens: website, mobile app, or Telegram bot
- Confirm who owns the backend that will hold API credentials securely
- Plan for webhook handling and order-status reconciliation, not just the “pay” button
- Budget for sandbox testing time before requesting production access
Where this fits into a broader automation strategy
For many Tashkent and Samarqand retailers, a payment integration isn’t the whole project — it’s one piece of a Telegram-based ordering and CRM system. Telegram itself reaches roughly 95% of Uzbek internet users, so a bot that lets customers browse, order, and pay with Uzum Bank in one flow tends to convert far better than sending them to a separate website. If you’re weighing whether a Telegram bot with built-in payments makes sense for your business, our guide to Payme integration for websites and apps and our Click integration guide for Uzbek businesses cover the adjacent providers in more depth, while our explainer on UzCard and Humo online payments covers the card side.
Businesses that go further often connect payments to an AI-driven sales or support layer — for example, an AI agent that answers product questions in Uzbek or Russian and hands off to checkout automatically. Our complete guide to AI agents for business in Uzbekistan is a good next read if you’re thinking about that layer.
Frequently Asked Questions
Do I need Uzum Bank if I already accept Payme and Click? Not always immediately, but it’s increasingly common. If a meaningful share of your customers use the Uzum app, missing that option at checkout costs you conversions you can’t easily measure until you add it.
Can one developer team integrate all three — Payme, Click, and Uzum Bank? Yes. Most Uzbek payment integrations reuse the same backend structure across providers, especially with a unifying library like PayTechUZ. It’s normal to launch with one provider and add the others incrementally.
How long does a production Uzum Bank integration take? Development typically takes one to a few weeks depending on scope. The merchant approval process on Uzum’s side can add time and is outside a development team’s control, so it’s worth starting that application early.
What ongoing costs should I expect after launch? Beyond Uzum’s own transaction fees, budget for ongoing technical support — typically from around $50/month — to handle API changes, monitoring, and reconciliation issues as they come up.
If you’re planning a Uzum Bank payments integration — on its own or as part of a bigger Telegram ordering and CRM setup — we’d be glad to scope it with you. Check our services and recent work, or get in touch to talk through your specific setup.
Building something like this?
Fera Tech ships iOS & full-stack apps end-to-end. Tell us about your project.
Start a project