# Payment Providers in Kyrgyzstan: From QR Acceptance to Reconciliation

When comparing payment providers in Kyrgyzstan, start with the journey from a customer's payment to a matched order and usable merchant funds. A familiar QR experience can make checkout look straightforward. The provider comparison becomes more useful when it also covers payment confirmation, reporting, settlement and a separately qualified payout service.

## A numerical starting point for the provider comparison

We reviewed **61 unique historical payment offers** linked only to this country: 30 collection offers and 31 payout offers. They provide a structured starting point for comparing payment costs, access to funds and operational requirements. 82 additional offers linked to several countries are excluded from the country-only calculations below.

The source is the PayStar export dated 14 September 2026, supplied by payment gateways. We recomputed its aggregates, but did not independently verify its commercial statements. This is a historical sample, not a market survey, a count of PSPs or methods, or proof of active connections and current availability. Conditions can change weekly or more often. Independent country, currency and method associations do not establish every possible payment route. Direction counts and settlement-label charts cover all recorded currencies. Only the percentage comparison below is restricted to explicit KGS fee records.

61 unique offers linked only to this GEO, across all recorded currencies; not methods, providers or live connections. [Download SVG](https://paystar.uk/kyrgyzstan-payment-solutions/media/2026-10-08-v2/charts/offers-en-desktop-download.svg)

## What the recorded KGS percentage components show

We calculate the arithmetic mean of explicit percentage components stated in KGS, giving each comparable offer equal weight. A record qualifies only when its structured percentage matches one unambiguous percentage in the original fee description. Offers in another fee currency, missing percentages and ambiguous descriptions are excluded.

We also exclude bound or conditional percentages such as “from”, tiers and explicitly restricted customer categories. Exact nominal percentage components with fixed minimums or caps can remain in the sample; those minimums and caps still affect the final charge.

| Direction | n | Mean | Median | Range |
| --- | --- | --- | --- | --- |
| Collections | 28 | 6.53% | 6% | 4.5–10.5% |
| Payouts | 26 | 2.82% | 3% | 1.5–4% |

Explicit KGS percentage components only. n is the comparable sample in each direction; missing fees are excluded, not zero. [Download SVG](https://paystar.uk/kyrgyzstan-payment-solutions/media/2026-10-08-v2/charts/fees-en-desktop-download.svg)

**These are percentage components, not all-in payment prices.** Fixed charges, FX, tax, reserves, minimums and charges for refunds or other exceptions must be assessed separately. This sample is not weighted by payment volume, contains no measured conversion rate and cannot rank provider quality. Small or insufficiently independent groups are withheld.

### A hypothetical payment calculation

Take an illustrative payment of 1,000 KGS; this is not a typical market ticket. Applying the rounded means shown above gives:

- Collections: 1,000 KGS × 6.53% = **65.3 KGS**.
- Payouts: 1,000 KGS × 2.82% = **28.2 KGS**.

Each line is a separate direction, not a combined service quote. The arithmetic shows only the percentage part. Ask for an actual quote at your ticket size, volume, business model and settlement currency before calculating net proceeds.

## When money becomes usable matters

Collection offers across all recorded currencies. T/D labels are recorded as supplied, without assuming calendar or business days. Other includes complex labels and pooled groups below 3 records. No guaranteed settlement time. [Download SVG](https://paystar.uk/kyrgyzstan-payment-solutions/media/2026-10-08-v2/charts/timing-en-desktop-download.svg)

A successful payment notification and money available to your business are different events. Treat recorded settlement labels as questions for a provider: what starts the clock, which cut-off applies, are weekends counted, which account is credited, and can a reserve or review delay availability?

For payouts, agree prefunding, beneficiary validation, rejection handling and how returned funds appear in your balance. An incoming-payment settlement label does not prove payout completion time.

### A cash-buffer planning example

If a business must fund 100,000 KGS of obligations per day, a one-day gap requires 100,000 KGS; a three-day gap requires 300,000 KGS. The additional buffer is 200,000 KGS. This is a hypothetical constant-flow model, excluding fees, reserves and volatility, not an observed settlement promise.

## Start with the QR payment your customer will actually use

Kyrgyzstan's QR framework provides an important local starting point. The National Bank's published rules establish a common standard and interoperability through interaction operators. They also distinguish payment notifications from the subsequent settlement process. [Source: National Bank of the Kyrgyz Republic, QR payment rules](https://www.nbkr.kg/contout.jsp?lang=ENG&material=126094).

For a merchant evaluating QR payment acceptance, our practical recommendation is to ask a shortlisted provider to demonstrate the complete purchase using the customer applications relevant to the business. Record which application starts the payment, the merchant identity shown to the customer and the confirmation that reaches your own system.

Then try the same purchase on one phone. A desktop QR demonstration can leave an important mobile journey untested: the customer must move from your checkout into a payment application and return to the order. Ask how the provider supports that sequence and how the merchant recovers the order if the customer closes the browser.

Coverage should be written down for the agreed merchant service. A list of application logos is only an opening question; the decision requires the supported purchase flow and evidence of its behaviour.

## Ask what connects the payment to the order

Consider a hypothetical online merchant receiving several payments for 1,500 KGS within the same minute. An amount and a successful customer screen leave the operations team with a matching problem. Ask the provider to show how each payment remains linked to its specific order.

Use this comparison during a demonstration:

| Merchant requirement | Evidence to request |
| --- | --- |
| Identify the purchase | Order reference preserved in the confirmation and transaction report |
| Confirm the amount | Amount and currency recorded alongside the provider's transaction reference |
| Release goods reliably | The merchant-side status used to authorise fulfilment, with a way to retrieve it again |
| Handle interruptions | Procedure for a missing notification, delayed result or repeated delivery of the same result |
| Close the books | Sample report connecting transactions, deductions and settlement batches |

These are qualification questions, not claims that every local provider offers the same fields. Review the samples with the person who will reconcile payments each day. That often exposes more useful differences than another checkout screenshot.

## Qualify ELCART acceptance as its own service

ELCART's official website describes internet acquiring for online purchases made with ELCART cards. This provides a separate local acceptance topic to investigate alongside QR. [Source: ELCART, internet acquiring](https://elcart.kg/).

Ask whether the proposed contract and integration cover the ELCART purchase flow you need. Request a demonstration of customer authentication, payment confirmation and refunds for that service. If a proposal includes both cards and QR, establish whether they share reporting, merchant balances and settlement statements or require separate operational work.

For a business also considering Uzbekistan, keep a country-specific acceptance checklist. The [Uzbekistan payment provider guide](https://paystar.uk/uzbekistan-payment-solutions) examines UZCARD and HUMO separately; those names should not be carried into a Kyrgyzstan requirement simply because both markets are in the same regional expansion plan.

## Build a separate brief for KGS payouts

Our snapshot contains almost equal numbers of incoming and outgoing offers. This is a feature of the recorded sample, with no implication about market size or demand. It is a useful reason to prepare two qualification briefs.

For KGS payouts, specify the business purpose, recipient category, destination instrument, typical amount and expected daily total. Ask each provider to confirm which combinations it accepts and what information it requires to validate a beneficiary.

Next, examine funding and exceptions. How is the payout balance funded? What happens when a recipient is ineligible or a destination rejects the transfer? Which status proves completion, and how is a returned amount shown in the balance and report? Obtain the provider's retry procedure before deciding how your operations team should respond to an uncertain result.

A refund of an earlier purchase also deserves its own question. Confirm its relationship to the original transaction, permitted timing and destination rather than treating every outgoing transfer as an interchangeable operation.

## Compare the cash cycle alongside the price

For collections, ask when confirmed revenue becomes available to the merchant, in which account and currency, and under which deductions. For payouts, ask how much prefunding is needed and when unused or returned funds become available again.

Compare proposals against the same business scenario: expected payment sizes, daily volumes, collection and payout mix, and settlement destination. Record percentage and fixed charges, minimums, any reserve, conversion terms and charges for relevant exceptions. Then request a worked statement using that scenario.

A KGS-labelled offer does not by itself establish the currency ultimately received by your company. Include company jurisdiction, business activity and intended settlement account in the initial discussion, so eligibility and the cash cycle are assessed together.

## The role of PayStar

PayStar provides information for comparing payment solutions and, where agreed, a technical layer for connecting and operating them. PayStar is not a bank or payment service provider and does not accept, hold or settle customer or business funds in its own name.

You select the payment provider and enter into a direct agreement with it. The provider processes payments and performs settlement under that agreement. Local eligibility, required authorisations and commercial terms must be confirmed for your company and use case. A method described in this article is not a promise that it is available through PayStar for your business.

Information about payment options is free. Payment processing and any agreed technical services have separate commercial terms.

## Official sources and research scope

- [NBKR: QR payment rules](https://www.nbkr.kg/contout.jsp?lang=ENG&material=126094)
- [ELCART: internet acquiring](https://elcart.kg/)

Research check: 8 October 2026. The export date remains 14 September 2026. Local scheme descriptions are context, not confirmation of a particular provider’s capabilities.