How to Set Up Online Payments for a Website in Uzbekistan
The most valuable visitor to a website is someone who is ready to pay right now. But if instead of a "Pay" button, they're met with a message saying "our manager will send payment details during business hours," some of these customers will simply leave—for a competitor where online payments take a minute, not half a day of back-and-forth correspondence.
Connecting online payments to a website in Uzbekistan has become much easier today thanks to modern payment services. Once integrated, a customer can pay for a product or service with a bank card, through a payment service, or via their banking app, and the order automatically gets the status "Paid." Businesses no longer need to manually send payment details, check for incoming funds, and update order statuses—all these processes are handled automatically.
However, "connecting payments" is more than just adding a button. Behind it lies an entire payment acceptance system: an agreement with a payment organization or bank, integration, status updates, receipts, refunds, and security. In this article, we will walk you through the entire journey—from choosing a payment service to your first successful transaction.
What Are Online Payments and How Do They Work?
Online payment refers to electronic payments where a customer remotely pays for a product or service through a payment form on a website or in an app, using a bank card, a payment service, or their bank's application.
After the transaction is confirmed, the website receives a notification from the payment service about its outcome. Based on this notification, the system can automatically:
- change the order status and send a confirmation to the customer;
- generate a receipt;
- transfer data to the CRM and update the product stock;
- initiate delivery or grant access to the service.
From the customer's perspective, it all looks simple, but between clicking the button and the payment confirmation, several parties are involved: the merchant, the customer's bank, the acquiring bank, the payment system, and the payment organization that connects them all. A typical scenario looks like this:
- The customer places an order and clicks "Pay."
- The website transmits the payment parameters to the payment service.
- The customer selects a payment method and confirms the transaction—with a code from an SMS or within their banking app.
- The bank and the payment system verify the transaction and debit the funds.
- The website receives the payment status: the order is marked as paid, a receipt is generated, delivery is initiated, or access to the service is granted.
It is at this stage that payment acceptance becomes fully automated: the system independently links the payment to the order, receipt, CRM, and other business processes, without any employee involvement.
Payment System, Acquiring, and Aggregator: What's the Difference?
In everyday conversation, anything that allows you to accept money on a website is called a "payment system"—be it bank cards or mobile payment apps. In practice, this term covers various participants in the process, and understanding the difference determines which contract you sign and what you will pay a commission for.
Concept | What it does |
Payment System | Establishes the rules for settlements and provides the infrastructure for bank card transactions. Examples include the national card systems Uzcard and Humo, and the international systems Visa and Mastercard for cards issued in Uzbekistan. |
Online Acquiring | A service that allows businesses to accept bank card payments via a website or app. |
Payment Service | An app or digital wallet that allows a user to pay for purchases without entering their card details. A separate case is making a payment through your bank's mobile app. |
Payment Organization (Aggregator) | A company that provides payment services and facilitates payment transactions. Depending on its business model, it may offer acquiring, payment processing, fund collection and distribution, and other payment-related services. |
Payment Gateway | The technological infrastructure that transmits payment data between a website, banks, and payment processing centers |
Online Cash Register (Fiscalization) | Generates fiscal receipts when required by law |
For most companies, the practical choice is to partner with a payment organization that consolidates card acquiring and payments via payment services into a single interface. This allows a business to have one integration and one contract instead of managing multiple separate connections.
Which Payment Methods to Set Up for a Business in Uzbekistan
Before setting up payment acquiring, you should understand your audience's preferred payment methods. If customers can't find their usual way to pay, the likelihood they'll abandon their purchase increases significantly. Therefore, a modern website or app must offer the widest possible selection of payment options. A basic set includes the following:
Bank Cards
The primary method of payment is via cards from the national payment systems, Uzcard and Humo. If your customers include tourists, expats, or users of foreign banks, it is essential to also enable acceptance of international Visa and Mastercard cards. Additionally, you should verify the card-linking feature: a saved card turns a repeat purchase into a one-click payment and significantly increases conversion rates.
Payment Services and Banking Apps
A significant portion of users in Uzbekistan is accustomed to paying for purchases not directly with a card, but through mobile apps: payment services, e-wallets, and their own banking apps. Payment takes just a few taps, and there's no need to enter card details—which for a business means more completed orders.
The problem is that connecting each service individually is time-consuming and expensive: every integration requires development, a separate contract, maintenance, and support. The solution is payment aggregation: a payment organization combines cards and payment services into a single interface, while the business gets one API, one contract, and one personal account. New payment methods are then enabled on the provider's side, with no additional development on your end.
Autopay and Recurring Payments
For subscriptions, online schools, streaming services, and any monthly online payments, recurring payments are the solution. The user gives their consent once and links a card, and subsequent charges are made automatically on a schedule. The card details are not stored on the website; instead, a token issued by the payment service is used. To prevent autopayments from becoming a source of complaints, the service must provide:
- explicit user consent to the amount and frequency of charges;
- the ability to disable autopay in a couple of clicks;
- notifications about upcoming and completed charges;
- a retry attempt in case of insufficient funds and the ability to change cards without losing the subscription.
Installment and Split Payments
BNPL (Buy Now, Pay Later) services and split payments help sell items with a high average order value. The customer can pay for the purchase in installments, while the seller receives the funds according to the terms of their agreement with the financial partner. A split payment, on the other hand, is when a single customer payment is divided among several merchants (settlement accounts). Before integrating, be sure to clarify: what product categories are eligible for installment plans, who approves the customer's application, when the seller receives the money, and how returns are processed.
Payment Links
If you don't have a full shopping cart on your website, you can accept payments via a payment link. Within the ATMOS system, a payment link can be generated via an integration and sent to the client for payment. This is a convenient option for individual orders and situations where a full-fledged shopping cart or online store is not necessary.
Who Can Accept Online Payments
Online payments can be accepted by legal entities and individual entrepreneurs, and in certain scenarios, by self-employed individuals, if permitted by the payment service's rules and the legislation of the Republic of Uzbekistan. Regular commercial activity requires a legal status and tax regime appropriate for the nature of the business: even if a service technically allows an individual to create a payment link, this is insufficient for the systematic sale of goods and services. Any ambiguous cases should be clarified in advance with the payment organization and a tax specialist.
How to Prepare for Setting Up Acquiring Services
The payment service evaluates not only the applicant's documents but also the website itself: the customer needs to understand who the seller is, what they are buying, and under what terms. Here's what you need to get in order before submitting your application.
1. Business documents
Typically, you'll need to provide registration details, a tax number, bank details, information about the company director, a description of your business activities, and data on your projected turnover. For regulated industries, licenses and permits are also required. Important: the description of business activities in the application must match the actual content of your website. A mismatch is a common reason for additional checks and rejections.
2. Settlement account
Funds from customers are credited to the seller's bank account. Check with the payment service provider in advance about the payout schedule and frequency, the minimum transfer amount, and the refund procedure.
3. A functioning website with complete content
The catalog must be populated, prices must be displayed and be consistent on the product page, in the cart, and on the payment form, and all buttons and forms must be functional. The payment service will likely reject an application for a site with an empty catalog, placeholder text, and "under construction" pages.
4. Seller information
In the website's footer or on a separate page, provide the company's official name, address, phone number, email, and customer support contact methods. The customer needs to see who they are entering into a transaction with.
5. Payment, delivery, and return policies
Describe the available payment methods, when an order is considered paid, where you deliver to and for how much, how to cancel an order, and in which cases and within what timeframe money is refunded. These terms must reflect your actual business processes—it's not a good idea to copy the policies of another online store without adapting them.
6. Public offer and Privacy Policy
The public offer defines the ordering procedure, the rights and obligations of the parties, cancellation and return conditions, and the dispute resolution process. The privacy policy explains what personal data the site collects, for what purpose, with whom it may be shared, and how users can inquire about the processing of their data. Next to forms where visitors enter their name, phone number, or email, you must include a consent to data processing with a link to the policy.
7. HTTPS and SSL certificate
All pages where data is entered—such as the cart, personal account, and checkout—must open via the secure HTTPS protocol. The certificate encrypts data transmission between the browser and the server, but it does not replace other security measures like protecting keys, checking notifications, and updating modules.
Website Readiness Checklist
Before submitting your application, check that:
- the site opens via HTTPS, with no errors or broken links;
- the catalog is populated, and prices are displayed and match the cart;
- forms are working, and the cart calculates the total correctly;
- the seller's contact information and business details are published;
- the payment, delivery, and return policies are accessible;
- the public offer and privacy policy are posted;
- there are no test sections or placeholder pages;
- the website's content matches the declared business activities.
How to Choose a Payment Processing Service
A low commission is an important, but not the only, criterion. A cheap service that goes down during peak hours, delays payouts, or doesn't support your preferred payment method will end up costing more than any commission. Compare them based on these seven parameters:
Criterion | What to check |
Payment methods | We support Uzcard, HUMO, Visa, and Mastercard, as well as popular payment services, bank card linking, autopay, recurring payments, payment links, installment plans, and other payment tools. |
Commissions and expenses | Transaction fees, connection and service fees, the cost of returns, and fees for additional features |
Payout schedule | Frequency of deposits, accounting for non-business days, and minimum payout amount |
Integration | Ready-made CMS modules, a documented API, test mode, and integration support |
Refunds and receipts | Full and partial refunds, automatic fiscalization if required for your business activities |
Security | PCI DSS certification, tokenization, payment confirmation, notification verification, and anti-fraud |
Support | Operating hours, response time, and assistance with connection and troubleshooting |
Be sure to also ask how the provider expands its list of available payment methods. If new services are added on their end, you won't have to go back to development each time. Before signing the contract, request a pricing plan specifically for your business sector and run some test payments.
Bank or Payment Organization: Which to Choose?
Direct Internet Acquiring from a Bank
This is a good fit for companies that primarily need to accept card payments and are comfortable working directly with a bank. This involves a direct contract, a familiar infrastructure, and the possibility of a custom rate for high-volume businesses.
Limitations: As a rule, there are fewer additional payment methods and ready-made business tools. Payment services must be connected separately, and ready-to-use modules and API documentation for your specific tech stack are not always available. Furthermore, banking processes are often less flexible: changes and improvements go through internal procedures and approvals, so their implementation can take a significant amount of time. A bank may not be able to quickly adapt its payment solution to a company's specific business processes, and the result of such modifications may not always fully meet the initial requirements. This can extend the timelines for launching new scenarios and complicate the scaling of payment infrastructure.
Payment Organization (Aggregator)
This is suitable for businesses that need all popular payment methods at once, such as cards and various payment services, through a single integration. It offers a unified dashboard and ready-made tools like card-on-file, recurring payments, payment links, and payouts. Onboarding is usually faster and support is simpler because all issues are handled by a single partner. The commission may be higher than a bank's, but it covers a whole set of features that would have to be connected and maintained separately if working with a bank.
A rule of thumb: Don't choose between a bank and a payment organization based solely on transaction volume or commission rates.
If a business only needs basic card payment processing and has the in-house resources to build its own integration, support, and additional payment scenarios, direct bank acquiring can be a suitable option.
However, for most companies, it's not just the ability to accept payments that's important, but also having a ready-made payment infrastructure, speed of integration, flexibility, and a partner with business expertise. In this case, a payment organization can offer more: a single integration, multiple payment tools, ready-to-use APIs and modules, ongoing support, analytics, and the adaptation of the solution to specific business processes.
Moreover, even a large merchant with a high transaction volume doesn't necessarily choose a bank directly. For a bank, such a client may be just one of many priorities, whereas a payment organization specializes specifically in payment infrastructure and can engage more deeply with the business's needs.
Therefore, the main question is not "Where is the commission lower?" but "Who can fulfill our entire payment scenario more quickly and effectively, and support our future growth?"
How to Set Up Payment Processing: 7 Steps
Step 1. Choose a payment service
Compare candidates using the criteria table above and be sure to check how the service performs under load: read case studies and ask about uptime and transaction processing speed.
Step 2. Submit an application and sign a contract
Having your documents prepared and your website ready will speed up the verification process. Carefully study the pricing plan: transaction fees, refund conditions, and the payment schedule and deadlines.
Step 3. Get integration credentials
After approval, the payment organization will issue identifiers, keys, and access tokens. Store secret keys securely on the server—in environment variables or a secret management system, not in the open-source code of your pages or in public repositories.
Step 4. Integrate the payment form
For a website built on a popular CMS, you just need to install a ready-made payment module and enter the keys. For a custom-coded website, mobile app, subscription server, or marketplace, API integration will be required for creating payments, getting statuses, handling cancellations and refunds, and error processing.
Step 5. Configure statuses, receipts, and refunds
The website should only change an order's status upon receiving a server notification from the payment service—after verifying its authenticity, the amount, and the order number. The user landing on a "Thank you for your payment" page is not a confirmation. If your business requires fiscalization, set up automatic receipt generation, including scenarios for full and partial refunds.
Step 6. Test all scenarios
Before accepting real money, run tests for all scenarios: successful payment, bank decline, insufficient funds, closing the payment form, notification delays and repeats, and refunds. Be sure to go through the entire process on a smartphone, as the majority of payments come from mobile devices.
Step 7. Launch and monitor
Replace the test keys with live ones, make a test payment for a small amount, and confirm that the transaction is visible in your personal account and that funds are arriving on schedule. Going forward, regularly track the percentage of successful payments, the reasons for declines, and any discrepancies between orders and transactions—this is the main source of growth for your payment page conversion rate.
Online Payment Security
Electronic payments are a high-stakes area: a mistake costs not only money but also customer trust. The minimum set of measures is as follows:
Action | What to do |
Do not store card data | Use a secure form from a PCI DSS-certified payment service—card details must not reach the merchant's server |
Protect secret keys | Store in environment variables or a secrets management system; restrict access to only those who need it |
Check notifications | Verify the digital signature of each webhook; otherwise, an attacker could "confirm" an unpaid order |
Avoid double charges | Assign unique identifiers to operations and track already processed requests |
Verify data on the server | Compare the amount, currency, and order number with the store's data; do not trust parameters from the browser |
Delimit rights | Set different access levels for employees to payments, refunds, reports, and integration settings |
Update modules | Check for CMS compatibility and run a test payment after each update |
Why Your Payment Might Not Go Through: 8 Common Reasons
- Incorrect keys — production and test data mixed up, extra spaces, wrong account;
- Test mode — the site continues to send requests to the test environment after launch;
- Webhook error — notification fails to arrive due to an incorrect address, an unavailable server, or an invalid SSL certificate;
- Invalid signature verification — the site rejects genuine notifications due to an incorrect parameter order or a different secret key;
- Amount mismatch — the payment was created for one amount, but the order cost changed: the system must stop processing and record the discrepancy;
- Outdated module — after a CMS update, the old module stopped working: install a compatible version and repeat the test;
- Bank decline — insufficient funds, card limits, or a suspicious transaction; suggest the client try again or choose a different payment method.
Start diagnostics in the payment service's personal account and notification log — in most cases, the cause will be visible there within a few minutes.
Why Businesses Choose Internet Acquiring and ATMOS Online Payments
ATMOS is a payment organization that helps businesses in Uzbekistan launch a payment acceptance system without complex development:
- A single payment window — accept payments via Uzcard, Humo,Visa and Mastercard cards issued by banks in Uzbekistan, as well as through popular payment services: one API, one contract, and one unified dashboard;
- Payment aggregation — the list of available payment methods is regularly expanding, with new services added without any development on the business's side;
- Security — compliance with the international PCI DSS 4.0.1 standard and annual external audits;
- Reliability — 99.99% service uptime;
- A full suite of tools — card tokenization, auto-payments and recurring payments, funds holding, payouts to cards, and card solvency analysis for scoring;
- Fast launch — documented API, integration guidance, and 24/7 technical support;
- Industry expertise — ready-made solutions for online stores, online services, microfinance organizations (MFOs), airline ticket offices, taxi fleets, BNPL services, restaurants, and cafes (HoReCa).
Want to enable online payments and set up internet acquiring for your website?
Check out the ATMOS solution.
Frequently Asked Questions
Can I set up online payments without a developer?
Yes, if your CMS or other platform/service has a ready-made integration with ATMOS. For example: FlexFin, NEMO, ETS, Exode, Delever, MegaGroup, FapiLab, Bito, and Taximaster. Integration via API will require a developer.
How long does setup take?
With all documents ready and a correctly configured website, a standard setup takes several days. This includes application review, signing a contract, integration, and testing. The timeline for API integration depends on the complexity of your product.
Which is better: a ready-made module or an API?
A module is for a standard online store and a quick start. An API is for mobile apps, subscriptions, marketplaces, and custom order logic.
Can I set up recurring payments for Uzcard and Humo cards?
Yes. The user links their card once, and subsequent charges are made automatically on a schedule. It is important to provide for user consent to auto-payments, notifications about charges, and a simple way to cancel the subscription.
Do I need an online cash register?
It depends on your business activity and tax regime. Clarify the fiscalization requirements with your accountant and check if the payment service supports automatic data transfer for receipts—it does not replace a cash register on its own.
Can I connect several payment services?
Technically, yes, and this increases fault tolerance. However, each additional service complicates accounting, testing, and refunds. Payment aggregation solves the same problem more simply: all payment methods are routed through a single integration.
What should I do if money was charged but the order is not marked as paid?
Do not ask the customer to pay again. Check the transaction in your payment service's dashboard and review the notification history. After the payment is confirmed, the order status will be updated either automatically or manually.
Can I change the design of the payment form?
A ready-made payment page has limited customization options—usually just the logo and basic colors. A custom payment interface via API allows you to fully adapt the design to your product.
How can I increase the share of successful payments?
Give customers a choice of payment methods, enable card-linking for repeat purchases, test the mobile user experience, and regularly analyze the reasons for declines. Often, a few technical fixes can significantly increase payment conversion rates.
Summary
Setting up online payments isn't a one-click process, but a bundle of legal, financial, and technical solutions: choosing a payment service, preparing your website and documents, signing a contract, handling integration, tracking statuses, issuing receipts, and conducting testing and post-launch monitoring. By going through this process correctly the first time, a business gains a payment acceptance system that runs on its own: it shortens the customer's journey to purchase, eliminates manual work, and turns every site visit into an immediate sales opportunity.




