Recurring Subscription Payments in Uzbekistan: How To

If you run a SaaS product, a gym, an online school, or a media subscription in Tashkent, you already know the awkward part: your customer wants to pay once and forget about it, but Uzbekistan’s payment rails were not originally built with Western-style auto-billing in mind. Setting up recurring subscription payments Uzbekistan businesses can actually rely on takes a different approach than plugging in Stripe.

The good news is that it is solvable, and increasingly common. Payme, Click, and Uzum Bank all support card tokenization that lets you charge a saved card on a schedule, provided you build the flow correctly and are upfront with customers about it.

---

Why recurring billing is different here

Card-on-file billing works only if the customer’s bank and card scheme (UzCard or Humo) allow token-based charges without a fresh OTP every time. Payme and Click both offer a “binding card” mechanism: the customer enters card details once, confirms with an SMS code, and your backend receives a token to charge later. Uzum Bank has been building out similar merchant APIs as it grows quickly among younger, urban users.

This is different from Western recurring billing in one important way: local banks are more cautious about silent charges, so the first charge (the binding) almost always requires explicit customer confirmation, and subsequent charges should still notify the customer — ideally through Telegram, since roughly three out of four internet users in Uzbekistan are active there daily.

The typical recurring payment flow

1. Customer picks a subscription plan on your site or Telegram bot.
2. You redirect to Payme, Click, or Uzum Bank’s card-binding screen (or use their SDK inline).
3. Customer confirms with SMS OTP; the provider returns a card token to your backend.
4. Your system stores the token securely and schedules the next charge (monthly, weekly, etc.).
5. On the billing date, your backend calls the provider’s “charge by token” endpoint.
6. Success or failure is pushed back via webhook; you notify the customer, ideally via a Telegram bot message with the receipt.

A library like PayTechUZ is worth evaluating here — it wraps Payme, Click, and Uzum Bank into one interface, so you are not maintaining three separate integrations with three different quirks.

Handling failed charges

Card balances run low, banks flag suspicious activity, tokens expire. Build retry logic: attempt again after 24–48 hours, notify the customer through your Telegram bot, and pause access gracefully rather than cutting it off instantly — this protects retention far more than a hard cutoff.

What it costs to build

Scope	Typical price band (so’m)	Notes
Single-gateway recurring billing (Payme or Click only)	1 500 000 – 5 000 000	Card binding + scheduled charge + webhook handling
Multi-gateway (Payme + Click + Uzum Bank) with retry logic	5 000 000+	Closer to a CRM/AI-agent-level build in complexity
Ongoing support & monitoring	from ~$50/mo	Failed-charge alerts, dashboard, provider API changes

These are ranges, not quotes — the final number depends on how many plans, currencies, and edge cases (proration, upgrades/downgrades, trials) you need.

A checklist before you launch

• Customer sees a clear consent screen before the first charge, including amount and frequency
• Card tokens are stored encrypted, never raw card numbers, in line with PCI-adjacent practice
• Telegram (or SMS) notification fires before and after every recurring charge
• Failed-payment retry and grace period are defined, not improvised
• Customer can cancel the subscription in one click, from the same channel they subscribed in
• You reconcile provider settlement reports against your internal ledger weekly

Local context that shapes the decision

The government’s push behind the AI Strategy 2030 and IT Park’s tax incentives has accelerated fintech and e-commerce activity across Uzbekistan, which means more local SaaS, media, and marketplace businesses are asking this exact question. In practice, subscription businesses that pair recurring billing with a Telegram bot for reminders and support tend to see healthier retention than those relying on email alone — a pattern consistent with the broader trend that Telegram bots often drive a meaningful share of monthly transactions for Tashkent-based digital businesses.

If you already accept one-time payments, this build is an extension rather than a rebuild. Our guide on how to accept online payments in Uzbekistan with Payme, Click, and Uzum covers the base integration these recurring flows sit on top of.

Choosing the right provider mix

Payme has the largest user base by far, so it is the safest default for consumer subscriptions. Click is a strong second, especially with an older or more provincial customer base outside Tashkent and Samarkand. Uzum Bank is worth adding if your audience skews younger and mobile-first, since it has grown quickly through the Uzum super-app ecosystem.

For a deeper look at each integration path, see our practical breakdowns of Payme integration for your website and app, Click integration for Uzbek businesses, and what you need to know about Uzum Bank payments integration.

Trials, upgrades, and downgrades

Most subscription businesses eventually need more than “charge the same amount every month.” A free trial that converts to a paid plan needs a binding event on day one even if no money moves yet, so the token is ready when the trial ends. Upgrades mid-cycle usually mean a prorated charge for the remainder of the period; downgrades are simpler if you apply them at the next billing date rather than refunding mid-cycle. Building these rules in from the start avoids a painful rewrite later, and they add meaningfully to the cost band above — budget toward the higher end of the multi-gateway range if trials and plan changes are part of your product.

Reporting and reconciliation

Payme, Click, and Uzum Bank each provide settlement reports, but the formats differ and none of them map cleanly onto typical accounting software like 1C or MoySklad out of the box. A recurring-billing build should include a reconciliation view — even a simple weekly export comparing what your system expected to charge against what actually settled. This catches silent failures (a token quietly stops working, a charge is disputed) before they show up as a revenue gap at month end.

Frequently Asked Questions

Can I charge a customer’s card without them re-entering details every month? Yes, through card binding/tokenization with Payme, Click, or Uzum Bank. The first charge needs explicit SMS confirmation; subsequent charges use the stored token, though best practice is still to notify the customer each time.

Do I need a license to run subscription billing in Uzbekistan? You don’t need your own banking license — you work through licensed payment providers (Payme, Click, Uzum Bank) who handle the regulated parts. Your responsibility is correct integration, data handling, and clear customer consent.

What happens if a recurring charge fails? The provider returns a failure code via webhook. Good practice is an automatic retry after 24–48 hours, a Telegram notification to the customer, and a grace period before suspending access.

Should prices be in so’m or dollars? Always so’m for local customers. Even if your product has a USD list price internally, quote and charge in so’m to match how Payme, Click, and Uzum Bank settle locally.

---

Recurring billing is one of the higher-leverage builds we do because it directly protects monthly revenue rather than just capturing one-time sales. If you’re weighing which provider mix fits your product, take a look at our services or the products we’ve already shipped in our work. When you’re ready to talk through your specific plans, pricing tiers, and edge cases, get in touch.