Online Payment Audit Checklist: Testing Websites and Bots Before Peak Sales
A step-by-step checklist to audit online payments, MXIK (IKPU) codes, fiscal receipts, and refunds on your website and Telegram bot before the major shopping season.
To keep online payments running smoothly on your website or Telegram bot during peak sale seasons, business owners need to verify four key areas: edge-case payment gateway stability, accurate transmission of MXIK (IKPU) codes to your virtual cash register, automated refund processing, and seamless mobile checkout. In our experience at NDC, a comprehensive technical payment audit takes 2 to 4 business days and prevents costly disruptions when customer traffic spikes.
In Brief
- Fiscalization errors and receipt discrepancies carry penalties under Article 227-1 of the Tax Code of 2% of quarterly revenue, while incorrect MXIK (IKPU) codes result in a 1% fine on the item value.
- Internet acquiring fees across banks in Uzbekistan average 0.5%–1% for HUMO and UZCARD cards, and 1.5%–3.5% for Visa and Mastercard.
- BNPL and installment services offer shoppers credit limits up to 35 000 000 UZS (so'm) with zero down payment, paying merchants the full purchase amount upfront.
- Before launching sales, always test failure states alongside successful checkouts: card declines, insufficient funds, order cancellations, and partial refunds.
Why You Must Audit Payments Before Peak Season
During 11.11, Black Friday, and the New Year rush, traffic to your storefront multiplies. If a customer spends time selecting items, enters their card details, and then encounters a frozen gateway or an uninformative error, they will instantly bounce to a competitor. Every abandoned checkout directly burns your ad budget.
Beyond customer retention, tax compliance is equally critical. In Uzbekistan, accepting online payments via local payment services is strictly tied to fiscal receipt generation. A developer bug in payload formation can cause a customer's card to be charged while failing to register an electronic fiscal receipt with the tax authorities.
Under Law No. ZRU-927 dated 29.05.2024, the penalty under Article 227-1 of the Tax Code of the Republic of Uzbekistan for missing fiscal receipts or failed tax system integrations is 2% of net revenue for the reporting quarter, escalating to 20% for repeated violations within a year. Additionally, under Law No. ZRU-741 dated 29.12.2021, an incorrect MXIK (IKPU) code penalty applies at 1% of the sold item's value. Routine payment gateway testing protects your business from these penalties.
Part 1: Payment Gateways and Error Handling
Most businesses test their payment setup superficially: open a product page, click checkout, enter test credentials, and check if the order status shows 'Paid'. However, real issues consistently occur in edge cases.
As outlined in the Payme Merchant API testing documentation, sandbox verification must cover authorization failures, incorrect order totals, unconfirmed transaction cancellations, and post-confirmation refunds.
What Business Owners Should Verify
- Session timeout. What does the shopper see if the payment page sits open for 15 minutes before they submit? The order must never remain stuck in a pending status.
- Insufficient funds. Does the system display a clear, localized message like 'Insufficient funds on your card' rather than cryptic technical errors in English?
- Interrupted payments. If the user clicks the browser's back button or closes the gateway window, the items in their shopping cart must remain intact.
- Payment captured without site confirmation. If the card is charged but the server momentarily loses connection with the gateway, the order status in the admin dashboard must update automatically via background webhooks.
Question for your developers: “Do we have automated webhooks configured to update the order status if a customer completes payment but closes the browser before being redirected back to our site?”
Part 2: Fiscalization and MXIK (IKPU) Codes
Every online retail transaction must generate an electronic receipt via a registered virtual cash register. Each receipt must detail the product name, VAT rate, quantity, price, and a 5-digit or 17-digit MXIK (IKPU) classification code.
Before holidays, stores routinely add gift sets, gift cards, and seasonal bundles. If a content manager creates a new item without an MXIK code or copies an incorrect code from an existing product, the system will issue non-compliant fiscal receipts.
What to Check Before Launching Promotions
- MXIK codes on promotional items. Ensure that every discounted product, bundle, and gift set has an up-to-date, verified code from the national tasnif.soliq.uz directory.
- Fiscal receipt display. After running a test checkout, inspect the receipt link or scan the QR code: verify that your company details, total amount, and itemized list match the order.
- Shipping charges. If delivery is paid, it is legally a separate service and must appear on the receipt as an independent line item with its own MXIK code.
- Discounts and coupon codes. When a promo code is applied, the final total in the virtual cash register receipt must adjust proportionally without distorting the VAT calculation.
Question for your developers: “How does our system handle checkout if an item in the cart lacks an assigned MXIK code? Does it block the transaction or fall back to an invalid default?”
Part 3: Refunds and Order Cancellations
During peak sale events, return rates naturally rise—shoppers order wrong sizes, change their minds, or order multiple items to choose one. Without an automated refund workflow, your accounting team will waste hours handling manual claims, collecting card details, and executing direct bank transfers.
Modern acquiring gateways allow one-click refunds directly from your store's admin panel. When triggered, the gateway cancels the charge or sends funds back, while the virtual cash register automatically prints a reverse fiscal receipt.
| Payment Method | Estimated Fee | Refund Details | Best For |
|---|---|---|---|
| HUMO and UZCARD via internet acquiring | 0.5%–1% (NBU charges 0.8% for UzCard and 0.5% for HUMO) | Instant refund back to the card via API or acquiring portal | Mass-market retail stores operating across Uzbekistan |
| International Visa / Mastercard | 1.5%–3.5% | Refund processed within several minutes up to several banking days | Brands targeting tourists and international shoppers |
| BNPL and Installment Services (Uzum Nasiya, Alif) | Varies by individual provider plan | Refund automatically closes or adjusts the customer's credit contract in the app | Electronics, furniture, and fashion stores with average order values from 300 000 UZS (so'm) |
Acquiring rates for domestic cards start at 0.5%, as reflected in publicly available data from NBU internet acquiring. Adding installment plans also deserves priority: services such as Uzum Nasiya grant buyers credit limits up to 35 000 000 UZS (so'm) for 3 to 24 months with 0% down. If you sell higher-ticket merchandise, ensure monthly installment breakdown estimates display cleanly right in your checkout cart.
How to Test the Refund Flow
- Place a small test order using a real payment card.
- Initiate a partial refund for a single item from your store's admin dashboard.
- Verify that the exact amount returns to the card without deducting unexpected fees from the customer.
- Confirm that a corresponding return receipt is recorded correctly in your Soliq tax cabinet.
Part 4: Checkout Experience on Mobile and Telegram Bots
Across our projects, over 75% of peak-season retail orders originate from mobile devices. If your payment screen is not optimized for smaller viewports, conversion rates plummet before users even enter their card details.
For Telegram bots, utilizing native Telegram Payments or a responsive WebApp storefront is vital. If a bot forces customers to open a lengthy external URL in a separate, slow browser window, abandonment rates skyrocket.
Mobile Checkout Checklist
- Minimal form fields. Never demand unnecessary details. Full name, phone number, and delivery address are sufficient. Request passport information only when processing bank installment plans.
- Autofill and numeric keypads. Card input fields should trigger the numeric keypad immediately on mobile devices, with card expiry dates formatted automatically with a slash.
- Gateway load speeds. Payment screens must open in under 1–2 seconds. Whenever we build online stores or deploy mobile interfaces, we always stress-test the cart on throttled 3G connections.
- In-app payments for Telegram bots. When using native integrations, the payment sheet should pop up directly inside the messenger rather than launching third-party browser tabs.
If you operate standalone mobile apps alongside your web store, make sure payment sessions don't reset when customers switch back and forth between their banking app and your store to retrieve an SMS confirmation code.
Common Mistakes That Wreck Sales
While prepping e-commerce platforms for major sales events, we regularly uncover three recurring pitfalls:
- Forgotten sandbox credentials. Developers test payment integrations in sandbox mode and forget to switch to live production API keys before launch. As soon as real traffic lands, shoppers encounter gateway errors and leave.
- No fallback payment provider. If a store relies on a single payment processor, any temporary gateway outage halts sales entirely. Integrating a secondary payment provider provides a crucial safety net.
- Inventory synchronization lag. If a customer successfully pays for an item, but the warehouse inventory system reports it out of stock an hour later, your business suffers reputational damage and pays non-refundable payment processing fees on cancellations.
If your business needs a resilient commerce platform built from the ground up, we design corporate websites and e-commerce portals with fault-tolerant payment architectures. Explore our past work in our project portfolio or review typical launch budgets on our pricing page.
Frequently Asked Questions
How do I test Payme and Click payments before peak sales?
To test safely, your developer switches the payment module into sandbox mode. Using test card numbers, they simulate various outcomes: successful transactions, insufficient balances, authorization declines, and aborted checkouts. Prior to launch, always make one live test purchase for a nominal amount using a real bank card and production keys, followed by an immediate test refund.
What should I do if an online receipt is issued with an incorrect MXIK (IKPU) code?
If an MXIK error is detected, correct it through your Soliq taxpayer portal. Issue a return receipt for the faulty transaction, then generate an amended receipt containing the accurate classification code. Doing this promptly avoids the 1% penalty on the product value for fiscal reporting discrepancies.
Does a company need separate bank accounts for each payment gateway?
No, opening separate bank accounts is not required. Acquiring banks and payment gateways consolidate daily proceeds and transfer them directly into your existing primary corporate settlement account at any commercial bank in Uzbekistan, net of agreed acquiring fees.
How can I integrate Uzum Nasiya installments into an online store?
Your business signs a merchant partnership agreement with the BNPL provider, after which developers integrate their checkout widget or API. When choosing this option, shoppers authenticate with the provider, and once approved, your store receives order confirmation and the full purchase amount deposited directly into your bank account.
If you are preparing your website, Telegram bot, or mobile app for the shopping rush and want to guarantee checkout stability, we can help. Reach out via our NDC contact page: we will audit your integrations, inspect payment logs, and ensure compliant fiscalization so you can capture every sale safely.
