1. Purpose of Bankemes
Bankemes provides technical tools for connecting a Merchant’s cashier account, creating payment scenarios, and using the API, webhooks, MCP and AI agents. These Terms apply together with the Offer, Privacy Policy and Subscription and Billing Terms.
2. User requirements
A user must have legal capacity and authority to act for the stated business, connect a cashier and process supplied data. Use of Bankemes does not remove obligations under law, the bank agreement or Buyer rights.
3. Account and security
Registration uses a phone number and one-time code. The user is responsible for its password, phone access, API keys and authorised users, must use unique secrets, and must report a suspected compromise promptly. Bankemes may require reauthentication where there is a security risk.
4. Kaspi cashier accounts
Only a cashier account the user is lawfully authorised to use may be connected. A Kaspi password or OTP must not be given to support or an AI agent. The bank may end a session or restrict the cashier, and Bankemes cannot reverse that bank decision.
5. API, webhooks and keys
An API key must be stored only on the user’s server. The user verifies webhook signatures, uses Idempotency-Key and does not treat a success_url redirect as proof of payment. A compromised key must be revoked immediately. Technical request limits are mandatory.
6. MCP and AI
The user verifies every MCP client and agent, grants minimum necessary permissions and revokes access when work ends. Owner confirmations must not be bypassed. Changes to a third-party project must be reviewed before production use.
7. Acceptable use
Users may create lawful payments and invoices, integrate their own business, receive statuses, deliver signed notifications and automate actions within granted permissions. Data must be accurate and personal-data rights respected.
8. Prohibited conduct
Bankemes must not be used for unlawful activity or in a way that threatens the platform, banks or other users.
- fraudulent operations and fictitious invoices
- use of another person’s cashier without permission
- circumvention of bank restrictions or approvals
- unauthorised access or forged payment statuses
- use of stolen API keys
- exploitation of vulnerabilities outside coordinated disclosure
- bulk traffic that disrupts the platform
- breaches of personal-data law
9. Review and restriction of operations
An ambiguous operation may be held for bank reconciliation or an authorised operator decision. This protects against duplicate credit and false status and does not mean that Bankemes takes the funds.
10. Suspension and access restrictions
Bankemes may apply proportionate restrictions where there are reasonable signs of a security threat, unlawful activity or material breach. The user will be notified where notice does not increase risk and is not prohibited by law, and may contact support.
A paid period is not confiscated arbitrarily. Consequences and any refund are assessed under the agreement and law.
11. Intellectual property
Exclusive rights in the Bankemes software, design, documentation and marks belong to their respective owners. The user receives a limited right to use the service during lawful access. Rights in Merchant content and data remain with the relevant rights holder.
12. Responsibility
Each party is responsible for its own breaches under Kazakhstan law and the approved agreement. No limitation applies where the law prohibits excluding or limiting liability. The user is responsible for lawful sales, supplied data and instructions to agents.
13. Complaints and requests
The phone and messaging channels are published on the Contacts page. The official email and Operator details remain pending. A request should identify the account and operation but must not contain a password, OTP or complete API key.
14. Termination
The user may stop using Bankemes, disable future invoices and revoke keys. Open operations must be resolved and schedules stopped before closure. Data is retained or deleted under the Privacy Policy and mandatory law.
15. Changes to these Terms
This draft does not apply until approved. Future versions require clear notice, an accessible copy of the text and a separate user action where renewed consent is required. The backend does not currently record consent versions, which is a separate technical requirement.