Integrations: so that the website, POS, 1C and messengers work as one.
We connect Kaspi payments, sync products and orders with 1C, send enquiries to the CRM and notify customers on WhatsApp. We have ready-made modules for the most common integrations in Kazakhstan, which is why it takes days rather than weeks.
Who it is for
- Stores and services that need Kaspi payment on the website or in the app with automatic confirmation.
- Companies with accounting in 1C, where stock, prices and orders have to match the website.
- Sales teams on amoCRM or Bitrix24 that need enquiries from the website, forms, WhatsApp and ads to land in the pipeline.
- Businesses that talk to customers on WhatsApp and want to automate notifications, reminders and broadcasts.
What you get.
Payment on the website, in the app, by link or QR. Automatic payment verification, refunds, instalments. Money goes straight to your account.
Exchange of product range, prices, stock, orders and counterparties through OData or CommerceML. On a schedule or in real time.
amoCRM, Bitrix24: enquiries from forms, messengers and ads into the pipeline with source tags; deals passed back to analytics.
The official WhatsApp Business API or our own service: order notifications, appointment reminders, broadcasts, chatbots.
Staff notifications, customer bots, Mini Apps.
Yandex Delivery, Kazpost, CDEK; 2GIS and Google maps, address autocomplete, cost calculation.
Kazakhstani SMS gateways, transactional e-mail, OTP codes.
Poloma, Senet and other POS systems: sales, shifts, receipts. Experience from 1Work.
Any service with an API: banks, marketplaces, e-document exchange, government services, your internal systems.
How to connect Kaspi Pay, in brief.
- You are a Kaspi business customer (sole proprietor or LLP). You apply to connect Kaspi Pay for your website or app.
- Kaspi issues API access and a test environment. Usually 3–10 working days.
- We integrate: payment creation, a payment page or QR, status checks, webhooks, refunds. We test in the sandbox, then in production with a real payment.
- Launch. The money arrives in your Kaspi account, and the website or app sees the payment automatically.
We do this regularly: we have our own multi-tenant Kaspi Pay gateway that powers our products and client projects. More in our article Kaspi Pay on a website.
From enquiry to result.
- 1Schema
Which systems, which data, in which direction, how often. An integration schema and an estimate within 1–2 days.
- 2Access
We obtain the API keys: Kaspi, 1C, CRM, WhatsApp. We help with the applications.
- 3Development
Exchange modules, error handling, logs, failure alerts.
- 4Testing
In test environments and on real data: payments, orders, stock, enquiries.
- 5Launch and monitoring
We switch it on, watch the first days and document it. Then support.
What affects the price.
Kaspi Pay on a website or in an app is ₸100,000–200,000 (we have a ready gateway). Enquiries from the website into amoCRM or Bitrix24 with source tags is ₸60,000–120,000. 1C exchange of product range, stock and orders is ₸200,000–500,000 depending on the configuration. WhatsApp notifications are from ₸100,000 plus API fees.
Complex integrations without a ready API (parsing, RPA, file exchange) are priced separately after the schema.
We do this for ourselves too.
All three of the studio's products run on integrations: Kaspi payments in 1Study and 1Ticket, Poloma and Senet POS systems and a Telegram wallet in 1Work. Inside the studio: a Kaspi Pay gateway, a WhatsApp service and an event service for the Meta Conversions API. For clients: a B2B platform with data exchange, catalogue sync and CRM integrations. See our case studies.
The short version.
How much does it cost to connect Kaspi Pay to a website?
₸100,000–200,000 of work plus the time to get access from Kaspi (3–10 working days). Kaspi's commission is paid by you directly at your rate.
Can we take Kaspi payments in a mobile app?
Yes. For physical goods and services, Kaspi Pay in the app; Apple and Google allow this. For digital subscriptions, purchases go through the stores.
Our 1C is on the accountant's server. Can you connect to it?
Yes, through OData or a CommerceML export. We need access to the database or help from your 1C specialist to publish the web service.
WhatsApp: the official API or a 'grey' one?
For broadcasts and high volumes, only the official WhatsApp Business API, otherwise the number gets blocked. For notifications at low volumes, our Baileys-based service is cheaper and faster. We will advise what suits you.
What if an integration breaks?
Every integration writes logs and sends failure alerts to us and to you. Under support we fix it the same day.
Need to connect Kaspi, 1C or a CRM? We will draw up the schema and price it.
Tell us which systems you have and what needs to pass between them. We will come back with an integration schema and an estimate.