1. Document status and parties
This text is a draft public offer. Platform Operator: [legal operator awaiting approval]. The full legal name, BIN, registered address and official email are pending approval.
Bankemes is a software as a service platform. A Merchant connects its own bank cashier account and uses the platform tools. A Buyer pays for the Merchant’s goods or services. Bankemes is not a party to the sale between the Merchant and Buyer.
2. Scope of the agreement
The Operator gives the Merchant access to Bankemes for technical integration with supported bank services, creation of payment links and invoices, receipt and reconciliation of payment statuses, automation of related operations, and use of the API and MCP.
Available features depend on the current plan, Merchant settings, connected cashier account and technical availability of external services. Website descriptions do not override individually agreed terms.
3. Legal role of Bankemes
Bankemes is not a bank, does not open bank accounts for Merchants and does not sell a Merchant’s goods or services to end Buyers. Funds from a Merchant operation are credited to the recipient of the relevant bank operation, not to Bankemes.
Bankemes is not an official product or representative of Kaspi Bank or any other bank unless confirmed by a separate agreement. This draft makes no conclusion on whether payment-services regulation applies to the architecture. That question requires a separate legal review.
4. Registration and acceptance
A capable individual, sole proprietor or authorised company representative may register if they have lawful authority to use the connected cashier account.
After approval, acceptance should occur through a separate interface action after the user has had an opportunity to review the current version. The current backend does not record the offer version or a separate acceptance event, so this mechanism must not be described as implemented until an audit trail is added.
The user must provide accurate details, protect passwords, API keys and devices, and revoke keys and contact Bankemes promptly if unauthorised access is suspected.
5. Bank integration and authority
The Merchant confirms lawful authority to connect the cashier account and use the relevant bank account, must comply with its bank agreement, and receives no banking authority through Bankemes that it did not already have.
Bankemes does not claim that every automation method is officially authorised by the bank. The Merchant evaluates whether technical automation is permitted in its relationship with the bank.
6. Risks of external bank services
Using third-party automation may lead to extra checks, restrictions or changes in service terms imposed by the bank. Decisions to block or restrict an account, cashier or session are made by the relevant bank under its own rules.
Bankemes does not guarantee the absence of blocks, restrictions, OTP challenges, terminated bank sessions, interface or API changes, rejected invoices or operations, or temporary unavailability of external services.
Bankemes is not liable for independent bank decisions outside the Operator’s control unless the consequences were caused by a breach of Bankemes obligations or applicable law. Bankemes does not guarantee that a block will be removed, service restored or compensation paid by a bank. The Operator remains responsible for its own breaches.
- suspension or blocking of Kaspi Pay
- cashier restrictions or session termination
- additional authentication
- changes to bank interfaces and policies
- rejection or delay of a bank operation
7. Operations and payment statuses
Creating a payment request or bank invoice does not mean that payment has completed. A payment is confirmed only after the relevant bank status and, where applicable, amount have been received and checked.
If the bank does not provide a reliable result, the operation may remain pending or require manual review. The Merchant is responsible for the amount, description, goods, services and legal basis of an invoice. Bankemes is responsible for performing its own technical obligations properly.
8. Buyers, goods and refunds
The Merchant is responsible for lawful sales, quality and delivery, fiscal records and required documents, consumer claims and purchase refunds. Bankemes does not become a party to the Merchant-Buyer transaction merely by providing technical infrastructure.
A technical error by Bankemes is assessed separately and does not exclude the Operator’s responsibility for its own conduct.
9. API, MCP and AI agents
The Merchant chooses which applications, developers and AI agents may access its account. Actions within properly granted authority may be treated as Merchant actions unless caused by a Bankemes breach.
Operations requiring owner confirmation must use the platform approval process. Approvals must not be bypassed, and bank passwords or one-time codes must never be sent to an AI agent in an ordinary message. The Merchant is responsible for changes made to third-party software by a developer or agent it invited unless damage was caused by Bankemes.
10. Recurring invoices
Bankemes invoice schedules, Buyer subscriptions in the Merchant’s own product, and the Merchant’s subscription to Bankemes are separate arrangements.
A recurring invoice is not an automatic debit. The Buyer pays every bank invoice manually. Under the Merchant API, the Merchant manages Buyer entitlements and access to its product. A schedule hosted in Bankemes operates only within enabled features and confirmed settings.
11. Plans and billing
Price and access period are governed by the separate Subscription and Billing Terms. The public price of KZT 4,990 per cashier and the current calendar-period model require a final owner decision after backend review.
Bankemes does not make automatic debits. Issuing an invoice does not mean it has been paid. Trial, grace, refund and future-invoice cancellation rules must be approved before this offer takes effect.
12. Service availability
The Operator may perform maintenance, resolve incidents, change compatibility and restrict dangerous operations. Absolute uptime and a 99.9% SLA are not promised. Material changes to approved terms will be notified by the method and within the period approved by the owner.
13. Liability
To the extent permitted by Kazakhstan law, the Operator is not liable for losses directly caused by independent third parties or circumstances beyond its control where those consequences were not caused by an Operator breach.
Liability for the Operator’s own breaches is determined by applicable law and the agreement, including Articles 358-359 of the Civil Code of Kazakhstan. A liability cap equal to twelve months of subscription payments is not included and requires a separate owner decision and legal review.
14. Ending use
The Merchant may disable future invoices in the cabinet and send a request through official contacts. Creation of new operations may be restricted after the paid and approved grace periods expire. Existing operations must still be reconciled.
When access ends, keys should be revoked, invoice schedules stopped, and data retained or deleted under the approved Privacy Policy and mandatory legal requirements.
15. Changes, governing law and disputes
The law of the Republic of Kazakhstan applies. A new version takes effect only after approval, publication and notice under the agreed process. Changes do not remove remedies granted by law.
Claims must be sent to the approved official email, which is not yet available. A dispute that cannot be resolved through negotiations is handled under Kazakhstan law.
16. Operator details
Full legal name: [awaiting approval]. BIN: [awaiting approval]. Registered address: [awaiting approval]. Official email: [awaiting approval]. Phone: +7 707 701 66 23.