Payme and Click payment integration Payme, Click and Uzum integration

Payme, Click and Uzum payments on your website, Telegram bot, Mini App or mobile app — built so that money is never charged twice, every payment matches an order and the payment status reaches your CRM or 1C at once. You sign the contract with the payment provider, and the money goes to your account.

Price
from $2,500
Timeline
from 2 weeks

Price and deadline are fixed in the contract before work starts

What is included

  • 01Payme, Click and Uzum on your website, bot, Mini App or app
  • 02Handling of payment-provider callbacks with signature checks
  • 03Protection against double charges and repeated callbacks
  • 04Payment statuses in your CRM, 1C or MoySklad
  • 05Cancellations and refunds reflected in your accounting
  • 06Fiscal receipts through an online cash register
  • 07An exchange log: every payment and response is visible
  • 08A Telegram alert if the exchange stops

Who it is for

  • Stores and services that take card transfers and reconcile payments by hand
  • Telegram bots and Mini Apps where the customer has to pay without leaving the chat
  • Companies that accept payments but whose statuses never reach the CRM and 1C
  • Businesses that need Uzum Nasiya instalments or Uzcard and Humo acquiring

Three levels and prices

Pick the level that fits the task and budget. The exact scope is assembled in the configurator and fixed in the contract.

Link

Two systems, one-way exchange

$2,500–6,000

≈ UZS 30M · from 2 weeks

Data bus

Up to 6 systems, two-way exchange, queue and retries

$10,000–25,000

≈ UZS 120M · from 6 weeks

API platform

Public API, partner keys, documentation, webhooks

$30,000–70,000

≈ UZS 360M · from 12 weeks

UZS amounts are indicative, at the Central Bank of Uzbekistan rate on 14.11.2026. Contracts are in USD, or in UZS at the rate on the invoice date.

In detail

What drives the price

The price is not about a “Pay” button; it is about where money and statuses have to go. The Link tier connects two systems one way — say, Payme and your website — with an exchange log where every payment is visible. The Data bus tier connects several systems both ways: payment providers, the bank, 1C, the CRM and the website, with a queue, retries and failure alerts. The API platform tier is for when partners connect to you: a public API, keys, documentation and webhooks. If we are already building your store, bot or app, Payme, Click, Uzum, card acquiring and the online cash register are added to that project as separate lines in the configurator.

How the integration runs, week by week

On day one you apply to Payme, Click or Uzum: your company signs the contract with the provider, and we tell you which documents and website pages the application needs. While the provider reviews it, we build the integration in the provider’s test environment and run every scenario, not just a successful payment: cancellation, a repeated callback, a dropped connection, insufficient funds, a refund. Then we connect statuses to your CRM or 1C and set up fiscal receipts. We switch to live keys once the provider approves the application, and the first real payments run under our watch. Review times depend on the provider, so apply on day one.

Local specifics: Payme, Click, Uzum and the receipt

Each provider has its own logic. Payme calls your server itself: it asks whether an order can be paid, creates a transaction, confirms or cancels it, and the server must answer correctly even when the same request arrives several times. Click runs a payment in two steps, with every request signed. Uzum adds Uzum Nasiya instalments, while Uzcard and Humo cards connect directly through your bank’s acquiring. Fiscal receipts are a topic of their own: they must carry the product and service classification codes (IKPU), or the online cash register rejects them. Amounts in UZS, cancellations, partial refunds and reconciliation against the bank statement are all tested before launch, not discovered through customer complaints.

Risks and common mistakes

The first typical mistake is confirming an order when the customer returns to the “thank you” page instead of on the provider’s server callback. The customer closes the tab: money taken, order lost. The second is no protection against repeats: the provider resends a callback and a second order or a second credit appears. The third is no reconciliation: money arrives, the order sits unpaid, and nobody notices until month end. The fourth is a secret key in the page code, or test keys on the live server. The fifth is testing only the happy path. We close all of this with an exchange log, a retry queue and a Telegram alert when the exchange stops.

What the contract says

2%

for every day we are late

If we are late, your invoice drops by 2% a day, up to 10% of the contract. So we only name deadlines we can keep.

1

company per niche per city

For a year we do not take on your competitor in your city. What we build for you does not end up next door.

10%

refund after an outside review

Bring your own engineer. They check the code against the contract. If a contracted item is missing, we refund 10%.

Questions

How much does a Payme and Click integration cost?

Connecting a payment provider to your website, bot or accounting system starts at $2,500, with a timeline from 2 weeks: that is the Link tier, with an exchange log. If we are already building your store, bot or app, Payme, Click and Uzum are added to it as separate lines in the configurator. The exact amount is fixed in the contract.

How long does the integration take?

Our part takes from 2 weeks, including every scenario tested in the test environment. Add the provider’s own application review: that depends on Payme, Click or Uzum, so it is best to apply on day one. If our part is late, the invoice drops by 2% for every day, up to 10% of the contract.

Who signs the contract with Payme and Click?

You do. Your company signs with the payment provider, the money goes to your bank account, and we are not part of the payment chain. We tell you which documents and website pages the application needs and handle the technical side.

Can customers pay inside a Telegram bot?

Yes. The bot issues an invoice, the customer pays with Payme, Click or Uzum without leaving Telegram, and the bot confirms the order and sends a receipt. The payment status reaches your CRM or admin panel at the same time.

Can you connect Uzum Nasiya instalments and Uzcard and Humo cards?

Yes. Uzum Nasiya handles payment in instalments; Uzcard and Humo acquiring is connected through your bank. These are separate lines in the configurator, and we choose the payment methods you actually need during discovery, based on your customers and average order value.

What if a payment went through but there is no order?

The integration is designed to prevent it: the order is confirmed by the provider’s server callback, a repeated callback does not create a second order, and the exchange log and reconciliation surface every mismatch. If this already happens in your current integration, we start with an audit and find where payments get lost.

Other solutions

Practice: Fintech & Banking