How to accept Kaspi payments without a developer: payment links with a form, online booking with a prepayment, and recurring payments on a schedule.
Not everyone needs an API. If you are a tutor, a studio, an Instagram shop, a club, or a property management company, it is enough to connect a cash register in the dashboard and use the ready-made tools: the customer pays in the Kaspi app, and you see payments in the Транзакции (Transactions) section and in the tool itself.
In the dashboard, under Все инструменты (All tools), there are three tools that work without code:
| Tool | What it is for | How the customer pays |
|---|---|---|
| Payment links | Paying for a service, a contribution, a prepayment, selling in a messenger | Opens a xpayment.kz/pay/… link, fills in a form, pays in Kaspi |
| Online booking | Booking a specialist, a class, a seat, or a rental with a prepayment | Picks a time on the booking page and pays a prepayment |
| Recurring payments | Tuition, rent, building contributions, any scheduled payments | Receives an invoice in the Kaspi app and by email |
Each of them needs a connected cash register. Connecting takes a few minutes: Full onboarding guide. If you do not have a register yet, connect one first.
Later, when you need to tie payment to your website or CRM, the same registers work for the API: Payment links via the API.
A payment link in the dashboard is a payment page with your own form. It is one permanent link: any number of people can pay through it, and you see who paid and how much. Share it on WhatsApp, Instagram, Telegram, or your website.
Open Платёжные ссылки (Payment links) and create a new one. You can start from a template:
| Template | What it is for |
|---|---|
| Оплата услуги (Payment for a service) | One price: a consultation, a class, a repair |
| Взнос с выбором суммы (A contribution with a choice of amount) | Several options: a collection, a donation, plans |
| Предоплата (Prepayment) | Part of the amount in advance, the rest on site |
The wizard has four steps:
Until a link is published, it is stored as a draft and saved as you fill it in. A draft cannot be paid.
The customer opens the link, fills in the form, and gets a Kaspi QR or deeplink: on a phone the Kaspi app opens, on a computer they can scan the QR. After payment the page shows that the payment went through.
The link card contains a list of payments: who paid, how much, answers to your questions, and the payment status. The list can be filtered and exported to CSV. If you no longer need a link, archive it: it stops accepting new payments.
Need the same scenario in your own app or on a site with your design? Use the API: Payment links via POST /v2/payments/link.
Online booking is for cases where a customer books a time and you want them to pay a prepayment. Customers book a specialist, a class, a seat, or a rental and pay in Kaspi. The booking appears in the dashboard right after payment.
xpayment.kz/book/…, and the organization has a shared page listing all cards.Open Онлайн-запись (Online booking), create a card, and choose the register that will receive the prepayments. After publishing, send customers the link to the card or to the shared page.
If you use webhooks, bookings with payment produce the events booking.confirmed, booking.expired, booking.cancelled, and booking.rescheduled (more: xpayment webhooks).
Recurring payments fit when the same people pay you on a schedule: tuition, rent, building contributions, memberships. You enter a list of phone numbers, an amount, and a schedule, and the invoice goes to the customer on its own, both to the Kaspi app and by email.
For each payer (“Новый плательщик”, New payer):
If there are many payers, you can upload the list as a file from a template: before importing, the dashboard shows the errors in the file.
A payer can also pay from the page whose link they received by email.
Open Регулярные платежи (Recurring payments), choose a default register, and add the first payer. These are ordinary xpayment payments, so if you have webhooks set up you also learn about them through payment.* events: xpayment webhooks.