Curated market guide
Uzbekistan PSP routes to verify first
Which Uzbekistan route should a merchant verify first: local card scheme, wallet/app route, BNPL route, or provider-selector fallback?
local card scheme or card acquiring route
Use this when the merchant needs card acceptance or a bank/acquirer relationship for domestic cardholders.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Which bank, acquirer, gateway, or scheme partner can onboard the merchant?
- Does the route support ecommerce, POS, payment link, refunds, disputes, and reconciliation?
- Is a local company, local bank account, tax registration, or local signatory required?
digital wallet or bank-app route
Use this when local customers are expected to prefer app, wallet, QR, or payment-link flows over card entry.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Is online merchant collection available for the exact product category?
- Is access direct, through a PSP, through a bank, or through a technical partner?
- Which payment status, refund, reversal, settlement, and reporting features are documented?
BNPL or installment-style route
Use this when the merchant sells higher-ticket goods and wants to assess buyer financing or installment-style checkout as a separate commercial route.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Which merchant categories, order values, and refund scenarios are supported?
- Which entity and settlement requirements apply?
- How are cancellations, disputes, customer eligibility, and reconciliation handled?
Documents to prepare
- Company registration documents
- Beneficial owner and director identification
- Website or app checkout screenshots
- Product category, refund policy, and customer support process
- Expected transaction volume, average ticket, and currencies
Questions to ask
- Do you support my current entity, or do I need a local entity or local partner?
- Which Uzbekistan methods are available for ecommerce merchant collection today?
- Is the route a payment method, bank relationship, PSP integration, or aggregator integration?
- Which payment status, refund, reversal, and dispute flows are supported?
- Where can I verify official onboarding steps and written pricing?
If the official contact route is unclear
LocalPayMap does not yet list public Uzbekistan PSP contact leads. Use the payment-channel records as a shortlist, then ask providers to confirm live merchant flows, entity requirements, settlement, refunds, disputes, and official production approval.
- Which Uzbekistan methods are available for ecommerce merchant collection today?
- Is the route a payment method, bank relationship, PSP integration, or aggregator integration?
- Which payment status, refund, reversal, and dispute flows are supported?
- Where can I verify official onboarding steps and written pricing?
Route comparisons
How local customers usually pay
Uzbekistan should be researched from the customer's payment habit first, not from a generic global checkout menu. Current public records point to Card acquiring, General commerce, Digital wallet and Buy now, pay later, while provider discovery may include banks, PSPs, gateways, acquirers and regional aggregators. For a small merchant, the practical question is which of those routes a real customer recognizes and which provider can legally onboard the merchant entity. Cards may be enough for some cross-border testing, but local conversion often depends on domestic bank rails, wallets, QR, payment links, cash-style collection or local debit schemes. Ask providers to separate live local methods from roadmap items, then confirm payment status timing, refund mechanics, settlement currency and support coverage before committing engineering work.
- Card acquiring acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Digital wallet acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Buy now, pay later acceptance through a provider that can onboard your merchant entity. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Uzbekistan, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Card acquiring, General commerce, Digital wallet and Buy now, pay later, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Uzbekistan. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Uzbekistan currently include local PSPs, banks, gateways and aggregators. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Ask regional PSPs and local banks which Uzbekistan methods are live for your merchant category.
- Request links to official onboarding, developer documentation, support and pricing pages.
- Do not rely on marketplace claims unless the provider confirms your entity and industry in writing.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Uzbekistan as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Uzbekistan, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Uzbekistan PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Uzbekistan is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Uzbekistan?
Start with Card acquiring, General commerce, Digital wallet and Buy now, pay later. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Uzbekistan without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Uzbekistan?
Public leads include local PSPs, banks, gateways and aggregators. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.