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.