Can I take website payments without a legal entity in Uzbekistan?

Full Payme/Click/Uzum acquiring usually needs TIN and a bank account. Without a legal entity you keep one-off transfers and payment links — not a store integration, and they scale poorly.

How long to connect Payme and Click to an existing site?

Application review often 3–7 business days, API code 1–3 days. UZNEO guide for integration with tests is about 3–7 days, depending on site stack and number of systems.

What fees do Payme, Click and Uzum charge?

Soft guide: Payme ~1–1.5%, Click ~1–2%, Uzum ~0.8–1.5%. Exact tariff is in the merchant contract. Many tariffs pay out daily. Do not rely on chat rumors.

What does the site need technically?

HTTPS, callback backend, order and success pages, return policy, legal details, logs. A static landing can start with payment links, but a cart needs a server.

Why use two payment systems?

Some clients only use one app. Payme + Click or Payme + Uzum cover more familiar final-step scenarios and cut checkout drop-off.

How is a payment link different from API?

A link sends the customer to a ready URL; statuses are often checked manually. API lets the site create invoices and handle callbacks: statuses, anti-duplicates, notices. For order volume, API is more reliable.

Can I take payment only through a Telegram bot?

Yes — for a small catalog and prepaid services it is a solid start. For 100+ products, SEO and complex delivery, a site or Mini App with the same payment logic is usually better.

Web development22 minApril 1, 2026

Payme, Click, Uzum: how to add online payment to your website

Robert MirovUpdated Sep 5, 2026

Online payment in Uzbekistan is a customer expectation, not a “nice bonus”. Buyers are used to paying with UZCARD or HUMO via Payme, Click or Uzum Bank (formerly Apelsin) — apps they use every day. If your site or bot has no familiar button, some people say “I’ll pay later” and never return. Below is a calm owner-level guide: how the systems differ in plain words, which documents you need, how a payment link differs from full API integration (the programmatic link between your site and the payment provider), how to handle a callback (the “payment succeeded” notice), timing and budget ranges, Telegram bot payment, refunds and common mistakes. No hype and no “connect in an hour” promise. Logistics link — payments and delivery. Launching a store from scratch — online store guide.

01Why online payment matters — without scare tactics

Online payment is not for decoration. It closes the gap between “I want to buy” and money on your account. Typical scenarios in Tashkent and the regions: • online store with a cart: the customer places an order and pays at once; • prepaid services: booking, consult, flower delivery, courses; • Telegram bot: catalog → payment link → status to the manager; • service landing: a “Pay” button without a full store. Without card acceptance, many businesses keep a chain: lead → chat → transfer → screenshot → manual check. That works at low volume and breaks when one manager cannot verify every payment.

Before	After
“Send your card number” in DMs	Payme / Click / Uzum button on site or in bot
Receipt screenshot and manual check	Callback updates order status automatically
“I’ll pay tomorrow” and silence	Payment at checkout or right after
“I paid / I didn’t” disputes without logs	Callback log and status in the system
One awkward app button	Two systems — the customer’s familiar choice

Online payment does not replace service or delivery. It removes friction on the final step — where warm leads are most often lost.

02Payme, Click, Uzum — plain-language overview

Payme — one of the most recognizable payment methods in Uzbekistan. The customer pays in the app or via a widget: UZCARD and HUMO. Merchant fee often lands in the ~1–1.5% range (exact figure is in the contract). Many urban buyers trust the button: “Payme is there” means “I can pay calmly”. Click — broad audience and a convenient REST API (a standard way to exchange data over HTTPS). Local cards plus often Visa/Mastercard. Application approval often 3–5 business days. Fee guide ~1–2%. Useful when you need a fast technical link to a site or bot. Uzum Bank (formerly Apelsin) — growing with younger users and Uzum ecosystem customers. QR, installments, subscriptions depend on product and tariff. Fee guide ~0.8–1.5%. If your buyers already live in the Uzum ecosystem, an Uzum button lowers friction. All three work in two modes: • payment link — the customer opens a ready URL in the app / payment page; • full API integration — site or bot creates an invoice, handles redirect/iframe and processes callbacks. Fees and timings are soft guides. Live terms always come from merchant support. Do not rely on someone else’s tariff from a chat — conditions depend on niche, turnover and contract.

03Payment link or full API: what to choose

Owners often mix up “a button with a link” and “payment inside the store”. Those are different maturity levels. A payment link fits if: • order volume is small; • products/services are priced manually or via a chat price list; • a landing or bot without warehouse stock is enough; • development budget is limited and you need a start in days. Full API integration fits if: • you have a cart, stock and delivery statuses; • managers should not verify every payment by eye; • ads send people to a catalog, not to “message us”; • refunds, repeat callbacks and dispute logs matter.

Before (link / manual mode)	After (API + callback)
Manager creates the link by hand	Site/bot creates an invoice for the order amount
“Paid” status set by eye	Callback changes status in the system
Duplicate payments sorted in chat	Idempotency: repeat callback does not spawn orders
Ads lead into conversation	Customer pays at checkout without an extra step

UZNEO rule: start with the scenario that covers 80% of orders. A link can become full integration later — if from day one you plan HTTPS, clear statuses and a place for callbacks. A store with a cart is better built as an online store, not “business card site + links forever”.

04Documents and legal entity: what they usually ask

Full acquiring (accepting cards through a payment system on a site/bot) in Uzbekistan usually requires a legal entity: sole proprietor or LLC with a TIN and a Uzbekistan bank account. Individuals usually cannot connect full website acquiring — one-off transfers and simplified schemes remain, and they scale poorly. Typical document pack (confirm with the provider): • registration certificate / extract; • TIN and bank details; • product or service description (what you sell, how you deliver); • site or landing with contacts and offer / return policy; • license if the niche requires it (healthcare, education, finance, etc.). What moderators often check: • is it clear what you sell and at what price; • are legal contacts and details present; • does the site look like an empty shell for suspicious traffic; • are returns and service terms described. If you have no site yet, you can start with a landing and payment links while preparing the legal pack. For ads and buyer trust, close the minimum early: who the seller is, what you sell, how money is returned.

05Step-by-step connection

Step 1. Legal entity and account. Sole proprietor or LLC, TIN, bank account. Without this, full acquiring is usually unavailable. Step 2. Apply to the system. Cabinets: Payme Business / Click Business / Uzum Merchant. Fill the form, attach documents, provide site URL and business description. Step 3. Contract and keys. Review often takes 3–7 business days (Click is often faster; others may take ~10). After approval you receive a merchant ID (seller identifier) and API keys / access to sandbox (test) and production. Step 4. Integration. Developer work: create an invoice for the order amount, redirect or iframe to pay, handle callback, update status, success/error pages. Experienced teams often need 1–3 days of code per one–two systems — if the site already has a backend. Step 5. Test and go live. Small-amount payments, cancellations, repeat callback, manager notice, a trial refund (at least the process). Go live only after successful tests. UZNEO usually connects Payme/Click to an existing site in 3–7 days or builds a turnkey store in 20–30 days — guide, depends on stack, number of systems and refund scenario.

06System comparison and how to choose

Parameter	Payme	Click	Uzum
Fee (guide)	~1–1.5%	~1–2%	~0.8–1.5%
Cards	UZCARD, HUMO	UZCARD, HUMO, often Visa/MC	UZCARD, HUMO
Onboarding	~5–7 days	~3–5 days	~5–10 days
Payout	Often daily	Often daily	Often daily
Installments	Check tariff	Check tariff	Often available
QR	Yes	Yes	Yes
Strength	Recognition	API and onboarding speed	Ecosystem / younger audience

Practical recommendation: at least two systems at checkout — e.g. Payme + Click or Payme + Uzum. One button excludes people without that app or habit. How to pick a pair: • urban retail and services — often Payme + Click; • audience closer to Uzum / marketplace — Payme + Uzum; • foreign cards more often — confirm current Visa/MC terms with Click. Do not connect “all three at once” if the team cannot test and support three callbacks. Two stable buttons beat three half-finished ones.

07Timelines and budget range

Timeline has two parts: merchant approval (provider + document completeness) and technical integration (site stack). Soft timing guides: • application and contract — often 3–7 business days; • code on an existing site with backend — often 1–3 days per system; • ready integration with tests at UZNEO — about 3–7 days; • turnkey store with payment — about 20–30 days. Integration budget range (soft guide, not a price list): • payment link on a landing — from hundreds of thousands UZS / tens of $; • full integration on an existing site — often from ~2–5+ mln UZS for one–two systems (CMS, Next.js, custom — different complexity); • bot + payment — often from ~2.5 mln UZS, ~7–10 days by scenario; • turnkey store — payment is part of the online store development estimate. What raises cost: outdated site without HTTPS, no backend for callbacks, non-standard CMS, three systems at once, complex refunds and CRM accounting. What lowers cost: clean stack, one–two systems, clear order statuses, willingness to test. Site stack affects timing more than “which button looks nicer”. Platform comparison — WordPress, Tilda and Next.js.

08Technical requirements and callback checklist

What systems and common sense usually require: • HTTPS (SSL) — mandatory; Let’s Encrypt is enough; • backend for callbacks (“payment succeeded / failed”). A static site without a server — links only; • order page: items, amount in UZS, order ID; • success page and a clear error message; • public return policy; • legal contacts and details. Callback in plain words. After payment the provider calls your URL with the result. Your site must: verify signature/token (per docs), find the order, update status, reply with the correct code, write a log. Without this, money can be charged while the order stays “awaiting payment”. Pre-prod test checklist: 1. Successful test payment → order = “paid”. 2. Cancel / fail → status is not “paid”. 3. Repeat callback does not duplicate the order or ship stock twice. 4. Callback logs exist (for disputes). 5. Manager notification (email / Telegram). 6. Refund process (at least manual) is described and checked. 7. Invoice amount and currency match the order (no tiyin mismatches). Simple option: button → Payme/Click link → pay in the app. Fits one-off services. Full integration fits a store with cart and warehouse.

09Payment in a Telegram bot

Many Tashkent businesses take payment via a Telegram bot — faster than a full store and cheaper than a mobile app. Typical flow: • customer picks a product or service in the bot; • bot creates an invoice and sends a Payme/Click/Uzum link; • customer pays in the app; • callback updates status in the bot / CRM; • manager gets a Telegram notice. When a bot is enough: food and flower delivery, prepaid services, small catalogs, booking with a deposit. When a site or Mini App is better: 100+ SKUs, filters, complex delivery, account area, SEO and ads to landing pages.

Before	After
Price list in a channel + “message the manager”	Bot takes the order and issues payment
Transfer screenshot in DMs	“Paid” status after callback
Night leads wait until morning	Payment and order capture 24/7

Bot + payment guide: often from ~2.5 mln UZS, ~7–10 days — depends on catalog, languages and number of payment systems. A bot pairs well with ads and CRM if payment statuses land in one deal card.

10Refunds, trust and customer support

A payment button without clear return rules raises complaints and makes merchant life harder. The customer should know in advance: • within how many days an order can be cancelled; • whether a service prepayment is refundable; • who covers the fee on a refund (often a contract term with the provider); • where to write in a dispute. Practical site minimum: • “Payment and returns” page in plain language; • support contacts (Telegram / phone / email); • legal entity details; • refund processing time (e.g. “up to N business days after confirmation”). Technically a refund may go through the merchant cabinet manually or via API — depends on system and tariff. At the start a manual process is often enough if it is described and managers know the steps. The key is not leaving the customer without a reply after a charge. Trust is built not by a “secure payment” slogan, but by familiar buttons, HTTPS, a clear order status and live support. That is calmer than any banner.

11Common mistakes

1. One system — clients without that app leave on the final step. 2. No HTTPS — application rejected or audit fails. 3. Callback not handled — money charged, order stuck. Need server and logs. 4. No test payments — production surprises with statuses and duplicates. 5. Outdated stack without updates — security risk; modern option — Next.js vs WordPress/Tilda. 6. No return page — complaints get harder and reviews suffer. 7. Ads before payment is ready — you pay for traffic and lose conversion at checkout. 8. Three half-finished buttons at once — support and tests spread thin; bugs stay unnoticed.

Before	After
One button “like the competitor”	Two proven systems for your audience
Static site + “pay later”	Backend + callback + statuses
Launch ads on connection day	Test checklist first, then budget
Refunds “we’ll figure it out”	Public rules + clear process

Fixes are usually cheaper than reconnecting from scratch: close the callback checklist, add a second button and describe returns.

12Checklist before you launch ads

Before spending budget on Google Ads, Instagram or Telegram, walk a short list. It is cheaper than fixing payment under hot traffic. 1. Legal entity and merchant contract are active; keys are not from the test contour only. 2. HTTPS works on every checkout page. 3. Two payment buttons — or one on purpose, knowing whom you exclude. 4. Success / error / cancel change order status correctly. 5. Repeat callback is verified. 6. Manager gets a notice on a new payment. 7. Return policy is published. 8. You made 2–3 real small-amount payments “as a customer”. 9. Delivery handoff is clear — who picks the order after “paid” (see payments and delivery). 10. There is an owner: who fixes payment on weekends if the callback fails. If an item is “later” — wait before scaling ads. UZNEO usually closes payment and statuses first, then amplifies traffic.

Summary

Payme + Click (or Uzum) is a calm standard for sites and bots in Uzbekistan. Order: legal entity → application → choose link or API → callback checklist → test → only then ads. Do not overcomplicate: two working buttons, clear returns and dispute logs beat “every system at once”. UZNEO builds online stores with payment, connects payment to existing sites and ships Telegram bot flows. Message on Telegram — we’ll estimate timing, stack and budget range for a clear next step.