Kaspi Pay on a website and in an app: how to connect it

Kaspi is the payment method people in Kazakhstan expect by default. If a website has no Kaspi, some buyers leave to ask “can I pay with Kaspi?” on WhatsApp — and half of them are lost. We connect Kaspi Pay in our own products and in client projects, and here is everything you need to know before you start.

The options

Kaspi Pay for websites (API). A full integration: the buyer taps “Pay”, lands on a Kaspi page or receives a QR code, pays, and the site gets an automatic confirmation. Suitable for stores, services and apps.

Kaspi QR. A static or dynamic QR code the buyer scans in the Kaspi app. Simpler to set up, but payment confirmation has to be checked through the API or by hand.

Payment link. Generated for a specific amount and sent via WhatsApp or Telegram. Convenient for orders through messengers and bots.

Kaspi Shop. This is not payment on your site but Kaspi's marketplace, with a commission. A website of your own with Kaspi Pay does not replace it — it complements it: no commission and your own customer base.

What the business needs

1. Be a Kaspi business customer: an individual entrepreneur or an LLP with a Kaspi business account.
2. Apply for Kaspi Pay for a website or app through your manager or the business dashboard.
3. Get API access and a test environment. In our experience, 3–10 working days.
4. Have a website or app to integrate into — and a contractor to do it.

Integration stages

Creating the payment. The site passes the amount, order number and description to Kaspi and receives a link or a QR code.

Payment. The buyer pays in the Kaspi app — from their balance, by card or in instalments if enabled.

Confirmation. Kaspi notifies the site (webhook) or the site polls the status. The order is marked paid, the buyer receives a confirmation, the goods ship or access opens.

Refunds. Full or partial refunds through the API, reflected in the Kaspi dashboard.

Reconciliation. A daily reconciliation of payments between your database and Kaspi's reports, so nothing is lost.

Integration usually takes 3–7 working days of work after access is granted, plus testing.

Instalments and credit

Kaspi instalments (0-0-12 and others) and credit are enabled within the same API — the buyer picks the option at checkout. For the business this raises the average order value, but the commission on instalments is higher. Terms are set by your agreement with Kaspi.

Kaspi in a mobile app: Apple and Google rules

Apple and Google require purchases of digital content and subscriptions to app features to go through their systems, with a 15–30% commission. But physical goods, services and anything consumed outside the app can — and should — be paid for through Kaspi. That is how delivery, taxis, doctor bookings and courses with live classes work.

Our product 1Study is built exactly this way: students pay schools directly through Kaspi, and Apple allows it because the course is the school's service, not a feature of the app. The line is fine, and it is important to get it right before submitting to the stores.

Common mistakes

• Checking payments by hand. “Send us a screenshot of the transfer” means lost orders and fraud. Only automatic confirmation through the API.
• Not handling cancellations. The buyer opened the payment and closed it — the order hangs. You need timeouts and statuses.
• Keeping API keys in the site's code. Keys live only on the server, in environment variables.
• Skipping reconciliation. Once a day, compare your orders with Kaspi's report. Discrepancies happen.
• Forgetting refunds. Refund through the API, not “we'll transfer it manually”.

What it costs

Kaspi Pay integration work at a studio: ₸100,000–200,000 for a website or app; we have a ready-made payment gateway, so we sit at the lower end of the range. Kaspi's commission is by your tariff, paid directly to Kaspi. More under integrations.

If we build the site — a store or an app — Kaspi goes into the estimate as a separate line, and from day one the money goes to your account, not through us.