Skip to content

Buyer subscriptions through MCP and the Merchant API

Set up recurring buyer invoices with a Bankemes schedule or your own application. The buyer pays every invoice manually in Kaspi; there is no automatic debit.

Open AI agents

Steps to follow

  1. Choose where the schedule and buyer access are managed. Bankemes can issue invoices on its schedule; your server remains responsible for access to your product or service.
  2. The agent finds the customer or creates a record from authorized data. Review the name, recipient phone, amount and purpose. Tool responses mask the phone number.
  3. For a Bankemes schedule, choose recurrence or explicit dates, an Almaty hour and a missed-run policy. The agent provides a page to approve the exact parameters; creation requires your consent.
  4. Inspect the schedule, its invoices and confirmed payments. Tools support pause, resume and cancel; review already issued invoices separately.

If your application manages subscriptions

The agent implements Merchant API remote-invoice calls and signed-webhook verification in your project. Your application stores subscribers, renewal dates and access rules. Create one invoice per buyer and period, and never extend access twice for a redelivered event. Do not run both scheduling models for the same buyer and period.

Buyer subscriptions and the Bankemes plan are separate

The buyer pays you for your product. You pay Bankemes for the cashier’s platform access. Archiving a customer does not erase financial history; cancel active and paused schedules before archiving. MCP accepts a customer phone only when creating the record; the owner changes or clears it in the dashboard.

Example task for your agent

Set up recurring Bankemes invoices for my customers. First show the customer, amount, calendar, sending hour and missed-run policy. Create the schedule only after my approval in Bankemes. Change product access only after a confirmed payment.

Your Kaspi password, SMS codes and bank session stay with you. Credentials use protected configuration; access to your project code is granted separately.

For developers and AI agents

The English Markdown reference contains tool schemas, parameters, request examples and access restrictions.

Technical reference in English