How does a Payme payment work?
The merchant creates an order and sends the shopper to a Payme checkout page, or the shopper pays from inside the Payme app. The shopper selects one of their linked Uzcard or Humo cards, confirms with a code, and Payme debits the card.
On the merchant side, Payme’s Merchant API calls the merchant’s server in steps. It checks that the order can be paid, creates a transaction, then performs it once funds are captured. A cancellation method, CancelTransaction, reverses a created or completed transaction.
Payme Business also offers a Subscribe API for card tokens. Card details are stored on the merchant’s server only as an encrypted token, which lets a merchant charge a saved card for repeat purchases. Payme recommends asking for a PIN before each charge on a saved token, and deleting the token after three wrong attempts.
Only legal entities and registered entrepreneurs can open Payme Business cash desks. Payments land in the merchant’s settlement account in Uzbekistan, and Payme offers cash desks with billing, without billing and for on-site payment.
Why does Payme matter for merchants?
Uzbekistan’s card market runs on two domestic schemes, Uzcard and Humo, and Payme is one of the main ways people pay those cards online. Spot.uz names Paynet, Payme and Click as the three largest payment operators. Payme reported net revenue of UZS 492.7 billion in the first half of 2026, up from UZS 327.1 billion a year earlier, and net profit of UZS 205.9 billion.
It sits in a large ecosystem. TBC Bank Group, which owns Payme, counted 24.2 million registered users across its Uzbek ecosystem at the end of March 2026, up 23% in a year, and 5.8 million digital monthly active users in June 2026. TBC describes the Payme app as a market leader.
It reaches shoppers in several places. Payme accepts payments through its app, Telegram bots and payment links sent by SMS or email, as well as on-site payment at physical points of sale, so one merchant account can collect online orders, invoices and in-person payments. For merchants with repeat customers, card tokens from the Subscribe API make the second purchase a one-step action.
What can go wrong?
Payme’s step-by-step protocol is strict. If the merchant server answers a check or perform call with the wrong error code or too slowly, the payment fails even though the shopper did everything right.
Shopper-side declines happen. Shoppers whose card has no SMS notification service cannot receive the confirmation code, and insufficient balance or card limits produce declines.
Orders can change between steps. An order that changes price or stock between the check and perform steps needs careful handling to avoid charging for something that cannot be supplied.
Refunds depend on implementation. Payme says refunds are only possible when the merchant has implemented CancelTransaction, and it refuses a cancellation once the order is marked as fully delivered. Reconciliation can also drift when the merchant’s records and Payme’s transaction states disagree after a timeout, so both sides need to treat the transaction state, not the browser redirect, as final.
How would Omno handle Payme?
Omno would connect to Payme through a provider and expose it as a standard pay-in through the API and the hosted checkout, so the merchant would not maintain its own Merchant API endpoints. The final status would reach the merchant by webhook, which is the source of truth. Merchant rules would decide when to show Payme, Click or a direct Uzcard or Humo card form, and a shopper whose payment fails could choose another method. Cancellations would run through the same API, and the routing-decision log would show how each payment was handled.