Updated: June 2026. TL;DR: For the Kyrgyzstan market, integrate local payment systems — MBank, O!Money, Elcart — plus Visa/Mastercard via an aggregator. Stripe and PayPal won't cut it: most customers pay through local apps, and missing them loses a large share of checkouts. Merchant approval takes a few weeks, so start it in parallel with development. Always verify payments server-side and handle callbacks idempotently.
If you're launching an online store or mobile app for the Kyrgyzstan market, international payment gateways alone won't cut it. Stripe doesn't operate in Kyrgyzstan. PayPal has limited adoption. Your customers pay through local apps and systems — and if you don't integrate them, you lose a significant percentage of potential purchases at checkout.
This guide covers the payment landscape in Kyrgyzstan in 2026 and what integration actually involves.
The Kyrgyzstan Payment Landscape
Kyrgyzstan's payment ecosystem is mobile-first and heavily concentrated in a few local systems:
MBank — the most popular mobile payment app in Kyrgyzstan. Nearly every adult with a smartphone has MBank. For B2C e-commerce and services, this is the highest-priority integration.
O!Money (O!Pay) — the mobile payment system from O! (Megacom). Large user base, works via USSD and mobile app. Strong presence in regions outside Bishkek.
Elcart — the national card system (НСПК КР). Used for government payments, salary disbursements, and retail. Important for reaching users who don't have Visa/Mastercard but do have an Elcart card.
Visa / Mastercard — via a local payment aggregator. Options: iPay.kg, Freedom Pay (formerly Freedom Finance), Optima Bank acquiring. Most Kyrgyz banks have acquiring services, but aggregators simplify integration.
Cash on delivery — still significant for e-commerce, especially for high-value items and in regions. Not a payment integration per se, but affects checkout flow design.
Integration Methods
MBank
MBank offers a merchant API for accepting payments. The integration flow:
- Register as a merchant in MBank's system — requires business registration documents, about 1–3 weeks
- Receive merchant credentials and API access
- Implement the payment initiation and confirmation callbacks on your server
- Customer pays by scanning a QR code or entering your merchant ID in the MBank app
The API is RESTful and reasonably documented. Development time: 1–2 weeks for a developer familiar with payment integrations.
O!Money
Similar merchant integration to MBank. O!Money also supports QR payments and push-payment initiations. Business registration required (1–3 weeks). Development time: 1–2 weeks.
Elcart
Integration is via Kyrgyz banks or directly through НСПК КР. Often bundled with bank acquiring services rather than standalone. If your bank processes Elcart, it's typically part of the same payment terminal/gateway integration as Visa/Mastercard.
Visa/Mastercard via Aggregator
iPay.kg and Freedom Pay are the most commonly used aggregators for web/app integration. Both provide:
- A hosted payment page (simplest integration — redirect to their page, receive callback)
- API-based integration (more control over UI/UX)
- 3D Secure support
- Supports Visa, Mastercard, and often Elcart through the same integration
Development time for aggregator integration: 1–2 weeks. Merchant registration: 2–4 weeks depending on the bank.
Recommended Integration Stack by Project Type
Small e-commerce store (WooCommerce):
- iPay.kg plugin (exists for WooCommerce)
- MBank QR code display at checkout
- Total development effort: 1–3 days
Next.js / custom web app:
- Freedom Pay or iPay.kg REST API
- MBank merchant API
- O!Money merchant API
- Total development effort: 2–4 weeks for all three
Flutter mobile app:
- Same APIs, implemented as HTTP calls from the app
- Payment confirmation via deep link or polling
- Total development effort: 2–4 weeks
Technical Considerations
Webhook reliability. Kyrgyz payment systems use callbacks/webhooks to notify your server of payment completion. Always verify payment status server-side — never trust the client's report of a successful payment.
Idempotency. Callbacks can arrive multiple times. Implement idempotency keys to avoid processing the same payment twice.
Testing environments. Most Kyrgyz payment providers offer sandbox environments. Test thoroughly before going live — payment integrations are where errors are most costly.
Refund support. Not all local systems support programmatic refunds via API. Check refund flow for each provider you integrate.
Currency. All local payments are in KGS (Kyrgyz Som). If your app shows prices in USD, handle the conversion carefully and consistently.
Compliance and Registration Timeline
Plan 4–8 weeks for the business registration and merchant approval process across all providers. This is typically the long pole in the tent for Kyrgyzstan e-commerce launches.
Required documents typically include:
- Business registration certificate
- Company charter
- Tax registration
- Bank account details
- Signatory authority documents
Start the registration process as early as possible — development can proceed in parallel against sandbox credentials.
Discuss payment integration for your project →
Frequently Asked Questions
Which payment systems does a Kyrgyzstan e-commerce store need?
At minimum: MBank (the most popular mobile wallet — top priority for B2C), O!Money (strong in regions), Elcart (the national card system, for users without Visa/Mastercard), and Visa/Mastercard via an aggregator like iPay.kg or Freedom Pay. Keep cash on delivery as an option — it's still significant for high-value items and in the regions.
Does Stripe or PayPal work in Kyrgyzstan?
No. Stripe doesn't operate in Kyrgyzstan and PayPal has limited adoption. International gateways alone will lose you a large share of checkouts. You need local systems (MBank, O!Money, Elcart) plus a local aggregator for international cards.
How long does payment integration take?
For a WooCommerce store with the iPay.kg plugin plus MBank QR — 1–3 days of development. For a custom Next.js or Flutter app integrating MBank, O!Money and an aggregator — 2–4 weeks. The longer pole is merchant registration: 2–4 weeks per provider, and 4–8 weeks total for business registration and approvals. Start registration early and build against sandbox credentials in parallel.
What are the most common integration mistakes?
Trusting the client's report of a successful payment instead of verifying server-side; not implementing idempotency keys (callbacks can arrive multiple times and double-charge logic); skipping sandbox testing; and assuming every provider supports programmatic refunds (many don't). Also handle currency carefully — all local payments settle in KGS.
Aunimeda — e-commerce development and payment integration for the Kyrgyzstan and Central Asian markets, with teams in Los Angeles, Bishkek, and Almaty since 2010. We build for clients across Central Asia, the US, and worldwide. Discuss your project →