How to accept payments on a website
The cart works, people add products — then at payment they jump to WhatsApp: “transfer to this card”. You lose conversion and clean accounting. Accepting payments on a site in Bishkek is not a Pay button. It is a chain: method → order status → receipt/notification → recovery on failure.
Methods teams usually connect
- cards via local or international acquiring;
- e-wallets and region-familiar payment rails;
- installments / credit from a partner bank;
- invoice payment for B2B (details + confirmation);
- part online, rest on delivery — for courier flows.
A small online store often starts with 1–2 methods. Subscription products or complex billing also need API integrations and recurring-charge scenarios.
What must work beyond the button
- A payment callback: the order becomes “paid” without Excel.
- Email/WhatsApp to the customer and an alert to the manager.
- Idempotency: a double click must not charge twice.
- A test environment before production — don’t debug on live buyers.
- Refunds and cancels: at least a clear process for who does what.
Without order status, “pay on site” becomes “did you pay? send a screenshot”. More on status exchange is in the API integrations guide.
Timeline and budget
Connecting one provider to a ready store often takes a few days to 2–4 weeks: merchant account, keys, checkout UI, tests. Longer with 1C, multiple currencies, or custom installments. Store-level ranges are in how to launch an online store.
Start with 1–2 methods customers actually use, then add exotic options. A stable checkout beats ten buttons where only two work.
Common mistakes
- turning payments on without SSL and a proper domain;
- never testing mobile checkout — half of drop-offs happen there;
- no test payments and no error log;
- fees and legal copy not aligned with accounting;
- a blank thank-you page with no order number after payment.
A working minimum: one reliable method, a clear status, a notification, and a phone test. Everything else is phase two.
Need payments on the site?
Tell us what you sell (goods / service / subscription), which methods customers ask for, and whether a merchant cabinet already exists. We will suggest a scheme and a connection timeline.