Qut PayWebsiteDashboardKnowledge baseAPI (OpenAPI)Guide for AI agentsРУСҚАЗEN

Connecting to CRM and other systems

Qut Pay has two levels. The first is a ready-made solution you simply install. The second is connecting through your CRM's own webhook or API capability. Both work; the only difference is the time it takes to connect.

Level 1. Ready-made solution

No code is needed. Install it, enter the key, and it works.

SystemWhat to do
WordPress / WooCommercePlugin → guide
OpenCart 4Module, README inside the archive
Tilda, Webflow, any HTML formCabinet → Integrations → "Form hook", put the link into the form's action field
n8nTwo ready-made workflows: creating an invoice and receiving events
1CGuide
TelegramPlatform bot: /invoice 5000, payment notifications (guide)

Level 2. Connecting via the API

There is no ready-made module, but you can connect. There is one condition: the CRM must be able to send outbound HTTP requests (usually called an "outgoing webhook", «исходящий вебхук»), or you need a developer.

CRMHow it connects
Bitrix24Outgoing webhook or n8n
amoCRM, KommoDigital pipeline webhook or REST API
AltegioWebhook and API
МойСклад, RetailCRMREST API
Any other systemREST API + webhook

This list is an example, not a limitation. Any system that can send HTTP requests can be connected.

Flow

There are two directions; usually both are needed.

CRM → Qut Pay (creating an invoice). When a deal moves to the "Awaiting payment" stage, the CRM sends a request to our API and receives a payment link and a QR in the response.

POST https://api.qut.kz/api/v1/invoices
X-API-Key: qp_live_…
Content-Type: application/json

{
  "amount": 25000,
  "description": "Deal #1042",
  "externalOrderId": "1042",
  "metadata": { "dealId": "1042", "manager": "Айгүл" },
  "customer": { "phone": "77001234567", "name": "Customer" }
}

The response contains payUrl, qrUrl and id. The CRM sends that link to the customer.

If the CRM cannot send JSON and can only submit a plain form, use the "Form hook": it recognises the amount, phone, email, name and comment fields by itself.

Qut Pay → CRM (payment notification). When the customer pays, we send a webhook to your address. metadata and externalOrderId come back unchanged, so you immediately know which deal was paid.

{
  "event": "invoice.paid",
  "invoice": {
    "id": "inv_…",
    "status": "paid",
    "amount": 25000,
    "externalOrderId": "1042",
    "metadata": { "dealId": "1042", "manager": "Айгүл" },
    "paidAt": "2026-09-10T05:12:00.000Z"
  }
}

The signature is in the X-QutPay-Signature header, HMAC-SHA256. Verification examples: Website integration.

If you have no developer

Copy the guide for AI agents in full, give it to ChatGPT, Claude or Cursor, and set the task: "connect Qut Pay payments to my CRM". The guide lists every endpoint, field and error. Do not paste the API key or the webhook secret into the chat; put them only on your own server.

The same text is ready in the cabinet: Integrations → "Guide for AI agents" → "Copy with task".

Testing

Do everything in sandbox mode first; it runs without real money. By changing the invoice status manually in the cabinet, you check that your CRM handles the webhook correctly. Once everything works, cabinet → Kaspi → connect a Cashier and switch to live mode.

Help

If you get stuck while connecting, write to us: cabinet → Support, or WhatsApp +7 778 881 3333, or /support text in Telegram @qutpaybot.


Need help? WhatsApp +77788813333 · kazprose@gmail.com · 09:00–21:00 (Алматы)
You can also write from the dashboard: Support.

Qut Pay is an independent service, not affiliated with Kaspi Bank JSC. Kaspi and Kaspi Pay are trademarks of their owner.