Online payments on your website: connecting Payme, Click and Uzum

Without online payments, an online store is just a catalog with a phone number. In Uzbekistan most shoppers pay with Uzcard and Humo cards via Payme, Click or Uzum — so connecting these systems should be planned from day one. Here’s what you need to prepare, how the integration works and where delays usually happen.

Which payment systems to connect

• Payme — one of the most popular systems, with convenient payment by card number or via the app.
• Click — widely used, with a large mobile app audience.
• Uzum — a growing ecosystem with a bank and a marketplace, familiar to younger shoppers.
• Visa and Mastercard — needed if you sell to foreign customers. Connected through an acquiring bank; check the terms with the bank in advance.

We recommend connecting at least two systems: some shoppers are used to one app and will leave if they don’t see it on the payment page.

What the business needs

1. A legal entity or sole proprietorship with a bank account.
2. An agreement with the payment system — signed on application; the system issues test and production access keys.
3. A finished website with product descriptions and prices, a public offer, delivery and return terms, and company contacts and details. Payment systems review the site before connecting it, and missing pages are a common reason for rejection.
4. IKPU (MXIK) codes for products and services — required for fiscal receipts. Choose them in advance with your accountant.

Apply to payment systems in parallel with development, not after it. Review and contract signing can take anywhere from a few days to a couple of weeks.

How the integration works

The flow is similar for all systems:

1. The customer places an order and chooses a payment method.
2. The site creates a payment and redirects the customer to the payment system’s secure page.
3. The customer confirms the payment — usually with an SMS code or in the app.
4. The payment system notifies the site of the status. The site verifies the notification and marks the order as paid.
5. The customer receives a fiscal receipt, and the manager is notified of a new paid order.

Step 4 is the most critical. The site must correctly handle repeated notifications, cancellations and refunds so that an order isn’t paid twice and money isn’t lost. This is exactly where cutting development corners costs the most.

Fiscal receipts

Every online sale must generate a fiscal receipt for the customer. Payment systems offer built-in solutions: the site sends the order contents with IKPU codes, and the system issues the receipt. Names, quantities and prices on the receipt must match the order — this is checked during integration.

Personal data

A store collects customers’ names, phone numbers and addresses. Uzbekistan’s personal data law requires such data about citizens to be stored on servers located in Uzbekistan. Keep this in mind when choosing hosting: a foreign cloud server may not be suitable for your main customer database.

The site also needs a personal data policy and consent checkboxes in order forms.

Pre-launch checklist

• The offer, delivery and return terms, and contacts are published on the site.
• Agreements with payment systems are signed and keys received.
• All products have IKPU codes.
• Test payments, cancellations and refunds have been run in test mode.
• Order notifications reach managers — via Telegram, email or CRM.
• The site runs on HTTPS, and the payment page works properly on mobile.

Cost and timing

Connecting one payment system to an existing store usually takes from a few days to a week of development, plus the payment system’s review time. In our online store projects, integration with Payme, Click and Uzum is already included in the price.

Already have a site and need to add payments? Get in touch — we’ll check what your case requires.