Steps to follow
- Give the agent the application URL and access to the appropriate repository. Without code access, it can provide instructions but cannot change the site.
- The agent creates the website resource and selects the cashier. Review that choice: it determines which seller receives the money.
- Test credentials and the webhook secret are delivered into the project’s server environment. They must stay out of chat, browser code, Git and logs.
- The agent adds server-side payment creation and webhook signature verification. The application grants goods or access only after a confirmed result; live credentials require your separate approval.
What to check in the code
- Repeating an idempotency key must not create another payment.
- A repeated webhook must not grant goods or access twice.
- A browser return must not replace verification of the bank status and amount.
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