Bring Tole payment capabilities into your product
Customers connect Kaspi inside your product: your backend creates a session and forwards the cashier phone number and SMS code to Tole through the signed API. During onboarding, you choose whether each customer pays or your platform settles the monthly statement.
externalCustomerId→HMAC-SHA256→- Connection API: phone → OTP→
- Signed webhook
OTP · credentials · payment confirmation
Tole for platforms
Two billing modes
In the standard mode the customer pays Tole and the partner receives a share. In pay as you go the platform pays the discounted aggregate of customer plans.
HMAC and IP allowlist
Separate sandbox/live keys, replay protection, least-privilege scopes, and signed webhooks.
API-only onboarding
Phone and SMS-code forms live in your product. Forward values only through your backend and never persist them in logs or storage.
You choose the mode
Choose customer-paid or platform pay as you go during onboarding. The selection is recorded immediately in your profile.
How integration goes live
- 1
Onboarding without an application
Learn the integration model and the complete customer API path. There is no manual approval or waiting period.
- 2
Sandbox
Issue a test key, register IPs and a webhook, then verify HMAC, customer creation, and error handling. Sandbox does not create a connection grant or cover an end-to-end invoice/QR flow; Kaspi onboarding and the customer-bound data plane require a live key.
- 3
API onboarding
Create a connection session, submit the cashier phone, then the SMS code, and wait for completed. Subscription checkout is used only when the customer pays.
- 4
Operate through the API
Your backend uses the HMAC API and receives status changes through signed webhooks.
Start without an application
Complete the visual onboarding, choose a billing model, and activate your integrator profile immediately.
Activation immediately unlocks API credentials, webhooks, and the complete reference in your dashboard.