When a store launches, payments are usually left to the last moment — a mistake. It's the block that shapes the architecture of the whole project, from the structure of an order to how that order reaches 1C.

What's on the market

  • Kaspi Pay. The most familiar path for a buyer: payment happens in an app they already use daily. For retail this noticeably reduces abandoned carts.
  • Bank acquiring. Classic card payment on the site. Universal, works with any card including foreign ones.
  • Freedom Pay. A gateway covering several payment methods at once, including instalments.
  • Halyk. Acquiring from the country's largest bank, often chosen by companies that already bank there.
A practical rule: if you sell to consumers at retail, start with Kaspi. If you work with companies and invoices, start with invoicing and add acquiring second.

What happens after "Pay"

This is where most of the invisible work lives. A payment system doesn't simply "take money" — it sends your site a notification about the result. Your site has to accept that notification, verify its signature, find the right order and change its status.

  • Repeated notifications. A gateway can send the same event twice. The order must not be paid twice as a result.
  • A lost response. The customer closed the tab right after paying — the order still has to update, because the notification goes to your server, not to their browser.
  • Mismatches. The amount in the notification must be checked against the order, otherwise the price can be tampered with client-side.
  • Refunds. The cancellation path is designed together with payments, not six months later in a panic.

Connecting to accounting

Payments are useless if a manager then copies the order into 1C by hand. Exchange is configured both ways: products and stock come from the accounting system to the site, orders and payments go back. The critical piece is error handling — if the connection to 1C drops, the order must queue rather than vanish.

Keep exchange logs. When it turns out a month later that one order never arrived, there's no way to investigate without them.

How long it takes

Connecting one payment method to a finished store is days of work, not weeks. A 1C or CRM integration is quoted separately, usually from ₸280,000 and four days, because it brings a staging environment and data reconciliation with it.

What genuinely belongs in the timeline is not development but access: the contract with the bank or payment provider, the company details, the test key. That part doesn't depend on the contractor and is regularly the longest.