Online payment on a website in Uzbekistan: Payme, Click, COD
Online payment on a website in Uzbekistan is not a checkbox in the technical brief but one of the main levers of conversion: if a customer cannot pay in a familiar way within a minute, they close the tab or switch to Telegram to ask for bank details. The payment mix here differs from the international one, so foreign guides fit poorly. Below: what to enable, what to prepare, how it works technically and what drives the price.
Online payment on a website in Uzbekistan: which methods you need
The baseline for a store selling to individuals is Payme and Click. These apps are already installed on most customers' phones, and payments in them are tied to Uzcard and Humo cards. If one of them is missing from your site, part of your orders disappears: people will not install a new app for a single purchase.
The second layer is card payment through a bank or gateway form, for those who do not use apps. The third is cash or card payment to the courier on delivery. The fourth is instalments for expensive goods: they are connected separately and not every store needs them.
Do not start with everything at once. Payme, Click and cash on delivery are enough for launch; add the rest when your orders show that customers are asking for it.
What to prepare before integration
A merchant account is opened for a business, so collect the company's registration documents, a bank account, the contact details of a responsible person and a description of what you sell in advance. The list of documents differs between providers and can change, so confirm it in the merchant dashboard or with the provider's manager.
Prepare the website itself too. Reviews usually check for product descriptions with prices, contact details, and delivery and return terms. Write those pages before applying, or the review will drag on. Receipts and tax accounting for online sales are a question for your accountant, since they depend on your tax regime.
How payment acceptance works technically
Payment is embedded in one of two ways. With a redirect, the customer clicks 'Pay', lands on a Payme or Click page, pays and returns to the site. It is simpler, and card data never touches your server. An embedded form or widget looks neater but needs more testing.
The key part of integration is not the button but the server side. Payme sends requests to your server: can the payment be accepted, create a transaction, confirm it, cancel it (CheckPerformTransaction, CreateTransaction, PerformTransaction, CancelTransaction). Click has a similar pair, Prepare and Complete. Payme passes amounts in tiyin and Click in soums, and mixing up the units is a common mistake: the payment goes through for a hundred times less or more than intended.
Order status must change only on confirmation from the payment provider, not when the customer returns to the 'Thank you' page, because they can close the tab right after paying. The handler must be idempotent: a repeated request for the same payment must not create a second order or deduct stock twice.
Cash on delivery and prepayment
Cash on delivery remains necessary, especially outside Tashkent, where people get used to prepayment more slowly. Removing it for the sake of a 'cleaner' flow makes sense only if you have checked your own orders and found no demand for it.
A practical scheme is to split by amount: cheap orders ship with cash on delivery, expensive or non-standard ones with full or partial prepayment. This lowers the risk of a courier refusal, which costs you delivery and time. Confirm such orders by phone or message before dispatch.
Timelines and what drives the cost
Merchant registration on the provider's side takes from a few days to a couple of weeks and depends on how complete your documents are. While the review runs, the developer works on the integration in a test environment. The integration itself on a ready site takes roughly 2–4 working days per provider, plus 1–2 days to check all scenarios.
The cost consists of the developer's work, the provider's fee on every transaction, time for documents and testing, and support when the API changes. Connecting one provider on the market costs roughly 1,000,000 to 4,000,000 soums depending on the site platform and the amount of logic. This is a guideline, not a price list. The fee is set by the contract and business category: find it out before launch and build it into product prices.
FAQ
Can I accept payments without a registered business? A merchant account usually requires a registered business, so confirm the terms with the provider before development starts. Until you have an account, work with cash on delivery.
Do I need both Payme and Click? Ideally yes: you do not lose customers used to a single app, and you get a fallback if one of the providers is temporarily unavailable.
What should I choose on a tight budget? Start with Payme, Click and cash on delivery, and add the rest on customer request.
How do I know payment works correctly? Run test payments, a cancellation and a repeated request, then make a real payment for a small amount and compare it in the provider's dashboard and in your orders database.
Pre-launch checklist
Typical mistakes: order status changes on the redirect rather than on server confirmation; soums and tiyin are mixed up; payment cancellation is not handled; secret keys sit in the page code; there is no clear page for a failed payment; the final total with delivery appears only after the customer reaches the payment step.
Before launch, check that: a test payment goes through and the order becomes 'paid'; a repeated request does not create a duplicate; a cancellation restores the status; payment works on a phone; a manager is notified about a new paid order; and a real small payment shows up in the dashboard.
If you need a website with payment designed from the start, 4 Digital builds turnkey websites from 1,399,000 soums. The checks above will be useful with any contractor, though.