Click Integration Guide for Uzbek Businesses
A practical Click integration guide for Uzbekistan: how it works, costs in so'm, common pitfalls, and how it compares to Payme and Uzum Bank.
If you sell anything online in Uzbekistan — a Telegram-based shop, a mobile app, a booking website — customers will ask one question before they buy: “Can I pay with Click?” This Click integration guide for Uzbek businesses walks through exactly what that means technically, what it costs, and where founders usually get stuck.
Click is the second most-used payment system in the country, right behind Payme, and it’s often the first thing customers try on a checkout screen. Getting it wrong — a broken callback, a confusing error, a payment that “went through” but the order never confirmed — costs you sales and trust. Getting it right takes a focused sprint of engineering, not months.
What Click Integration Actually Involves
Click works through a merchant account (Click Merchant Cabinet) plus an API integration on your side. At a technical level, three pieces have to work together:
- Checkout initiation — your app or bot generates a payment link or invoice with an amount and order ID.
- Payment confirmation callback — Click sends a signed webhook to your server confirming (or reversing) the transaction.
- Order state update — your backend marks the order paid, notifies the customer (usually via Telegram), and triggers fulfilment.
The tricky part is rarely step one. It’s steps two and three — handling Click’s two-phase confirmation (Prepare and Complete requests), verifying signatures correctly, and making sure your database never ends up out of sync with what Click actually charged. A rushed integration often “works” in testing and then silently drops a percentage of real transactions under load or on network retries.
Where PayTechUZ Helps
Most Uzbek dev teams don’t hand-roll the Click protocol from scratch anymore. Libraries like PayTechUZ wrap Click, Payme, and other local providers behind a consistent interface, handling signature verification and the prepare/complete flow for you. This cuts integration time significantly and reduces the class of bugs that come from mis-reading provider-specific documentation. If you’re evaluating providers broadly, our guide to accepting online payments in Uzbekistan covers Payme, Click, and Uzum Bank side by side.
Click vs Payme vs Uzum Bank: A Quick Comparison
Businesses rarely integrate just one provider — most serious Uzbek stores support at least two, because customers have strong habits and won’t switch apps mid-checkout.
| Provider | Market position | Typical use case | Integration notes |
|---|---|---|---|
| Payme | Largest user base (10M+) | Default choice, e-commerce | Well-documented, widely supported by libraries like PayTechUZ |
| Click | Second largest | Retail, delivery, subscriptions | Two-phase confirmation, solid uptime |
| Uzum Bank | Fastest-growing | Younger, app-first audience | Newer API, growing adoption |
| UzCard/Humo | Card-rail coverage | Card-based checkout | Often bundled via a gateway rather than direct integration |
For a deeper look at each, see our explainers on Payme integration for your website and app, Uzum Bank payments integration, and UzCard and Humo online payments explained.
What Click Integration Typically Costs
Pricing depends heavily on scope — a single “pay for this order” button is a very different job from a full subscription-billing system with refunds, partial payments, and reconciliation reports.
- A basic Click checkout added to an existing website or Telegram bot: roughly 1 500 000–3 000 000 so’m.
- A fuller integration with order management, refund handling, and admin dashboard: 3 000 000–5 000 000+ so’m.
- If you’re building the whole ordering flow (cart, order tracking, payment, notifications) from scratch, that’s closer to the range for an ordering-and-payment bot generally: 1 500 000–5 000 000 so’m.
- Ongoing support and monitoring (webhook failures, provider API changes) typically runs from ~$50/month.
These are ranges, not quotes — the honest answer is always “it depends on your existing stack,” but these bands reflect what Uzbek businesses typically budget for.
Common Integration Mistakes
- Not handling the
Preparerequest separately fromComplete— treating Click’s callback as a single-step confirmation - Trusting the callback amount blindly instead of re-checking it against your own order record
- No idempotency — a retried webhook creates a duplicate “paid” order
- Forgetting to test the cancel/reverse flow, only the happy path
- No Telegram notification on payment failure, leaving customers unsure if they were charged
- Storing merchant secrets in client-side code instead of the backend
Each of these is a small fix on its own, but they’re exactly the kind of thing that surfaces only after real customers start paying — which is why testing with real (small) transactions before launch matters more than testing with sandbox mocks alone.
Why Telegram Matters Here
With roughly 27 million users and about 76% of Uzbekistan’s internet population on Telegram, most Click integrations we see aren’t for a standalone website at all — they’re for a Telegram bot that takes an order, shows a Click payment button inline, and confirms the order back in the same chat. That flow removes the friction of switching between an app and a browser, and it’s the pattern behind a large share of Tashkent food-delivery and retail bots, where Telegram-based ordering often accounts for a significant chunk of monthly turnover. If you haven’t yet mapped out what AI and automation could do beyond payments, our complete guide to AI agents for business in Uzbekistan is a good next read.
Frequently Asked Questions
Do I need a business bank account to open a Click merchant account? Yes — you’ll register as a legal entity or registered individual entrepreneur with Click and link a business account before you get API credentials.
Can I integrate both Click and Payme at the same time? Yes, and it’s common. Most checkout flows show both as options, since customer habits differ and offering only one leaves money on the table.
How long does a typical Click integration take? For a straightforward checkout added to an existing product, a focused build usually takes a few weeks, not months — assuming your merchant account is already approved.
What happens if a payment succeeds but my server misses the callback? This is exactly why idempotent, retry-safe webhook handling matters. Click will retry failed callbacks, but your system needs to reconcile state correctly rather than silently dropping the update.
Every business’s checkout is a little different — different order flow, different fulfilment logic, different existing stack. If you want a second pair of eyes on your Click integration or a full payments setup across Click, Payme, and Uzum Bank, take a look at our services and recent work, then get in touch and we’ll walk through what a focused build would look like for you.
Building something like this?
Fera Tech ships iOS & full-stack apps end-to-end. Tell us about your project.
Start a project