Telegram bot payments in Uzbekistan: Payme and Click setup
Telegram bot payments close the biggest gap in the funnel: the moment a customer leaves to 'pay later' and never comes back. This guide covers connecting Payme and Click, how the payment flow works, what to check before launch and what drives the price.
Two ways to take payment in a bot
The first option is Telegram's built-in payments. The bot sends an invoice, the customer pays inside the Telegram window, and the payment provider is connected through BotFather. The second option is a button linking to a Payme or Click page or app: the bot creates an order, the customer goes to pay, and the provider notifies your server of the result.
The choice depends on the task. A built-in invoice shortens the customer's path. A payment link gives more flexibility: your own order statuses, one mechanism shared by the bot and the website, and non-standard scenarios such as prepayment. Ask your provider which options your contract actually covers.
What to prepare before integrating
You need a registered company or sole trader, a bank account and a contract with Payme, Click or both. Many businesses connect both: users have firm habits, and an extra method removes some refusals at the last step.
A pre-launch checklist: merchant dashboard access and test credentials; a server with HTTPS to receive notifications; a database with products, prices and order statuses; message texts for success, failure and waiting; and a named person responsible for daily reconciliation. Connect live keys last, once test payments run without errors.
How Telegram bot payments work step by step
The typical flow looks like this. The bot builds an order with a unique number and amount. It then creates an invoice and shows a payment button. The customer pays in the provider's app or page. The provider calls your handler: for Payme this is a set of methods to check, create and perform a transaction, for Click it is two stages, prepare and complete. Your server updates the order status, and only then does the bot send a confirmation.
The key principle: an order counts as paid only after server-side confirmation from the provider. Never confirm payment just because the user returned to the chat. Coming back to the bot does not mean the money was charged.
Check the amount format separately, because providers differ; Payme, for example, works in tiyin. A wrong multiplier is the most common reason test payments come out a hundred times too large or small. Also make the handler idempotent: the same notification can arrive twice, and an order must never be fulfilled twice.
What to do when payment fails
The customer closed the payment page, the transaction hangs, the card has insufficient funds, the invoice expired. Each case should lead to a clear message and a 'Pay again' button, not silence. The order stays in the cart so the person does not start over.
Expire unpaid invoices on a timeout, usually after 15–30 minutes, and release reserved goods or booking slots. Otherwise abandoned carts will block your stock and schedule. For hanging payments, add a repeat status request to the provider: if no answer arrives within a few minutes, the bot checks the state itself and tells the customer the outcome.
Refunds, reconciliation and security
Decide refund mechanics before launch: who initiates, within what window, and how it appears in the bot. A refund made in the provider dashboard must also change the order status in your database, or your records drift and customers get messages that are no longer true.
Once a day, reconcile payments in the provider dashboard against orders in your database. Gaps come from lost notifications and network failures, and it is better to find them yourself than through a customer complaint.
Keep provider keys on the server only, never in Mini App code or a public repository. Verify the signature or authorization of incoming requests, otherwise anyone can confirm someone else's order with a plain request to your handler. On the payment screen show the final amount, the order contents and a company name that matches what the customer will see on their statement.
Cost and timeline
The price consists of several parts: the bot itself with a catalogue and orders, connecting each provider, error and refund handling, a panel or alerts for the manager, and testing. The provider's commission is not part of development cost and is set by your contract. As a market guideline, connecting one provider to an existing bot costs roughly 2,000,000–5,000,000 UZS, and two providers with error handling and reconciliation roughly 5,000,000–10,000,000 UZS. This is not a quote; the exact price depends on the task.
On timing: the integration itself usually takes one to three weeks including testing, but signing the contract with a provider can take longer, so start there. The 4 Digital studio builds Telegram bots with payment acceptance; bot pricing starts from 999,000 UZS.
FAQ
Can I connect Payme and Click at the same time? Yes, it is a common practice: the customer picks the familiar method, and your server handles both types of notification in a single orders table.
Do I need a registered company? A provider contract usually requires a company or sole trader and a bank account. Ask the provider for the exact list of documents.
How do I test payments before launch? Walk the whole path in the test environment: successful payment, refusal, repeated notification, expired invoice and refund. Only then connect live keys.
What if the provider's notification never arrives? The bot should request the payment status itself after a few minutes, and the daily reconciliation against the dashboard will catch whatever remains.