Curated market guide
Kazakhstan PSP routes to verify first
Which Kazakhstan route should a merchant verify first: wallet, bank transfer, aggregator, card/acquirer, or LocalPayMap fallback?
local wallet or bank-app payment route
Use this when conversion depends on familiar customer apps or wallet-like flows and the merchant needs to verify whether the method is available for its entity and checkout model.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Is merchant acceptance available for ecommerce, QR, payment link, in-app, or invoice flows?
- Does onboarding require a Kazakhstan company, local account, tax registration, or local signatory?
- Who handles refunds, reversals, failed payments, reporting, and customer support?
bank transfer or bank-sponsored acquiring route
Use this when the merchant needs local bank settlement, bank app payments, transfer collection, or a bank-sponsored merchant relationship.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Which bank account and company documents are required for onboarding?
- Which customer payment flows are live for this merchant category?
- How are settlement currency, reconciliation files, refunds, and disputes handled?
payment aggregator or PSP route
Use this when the merchant wants one integration or a PSP conversation before building separate bank and wallet relationships.
Do not assume direct onboarding, local-entity access, settlement currency, pricing, or production approval. Confirm the route with the official provider, bank, acquirer, wallet operator, scheme, or PSP before implementation.
- Which Kazakhstan methods are live under the aggregator route?
- Can my current entity and industry be onboarded?
- Which official documents describe production approval, pricing quote, settlement, refunds, and dispute ownership?
Documents to prepare
- Company registration documents
- Beneficial owner and director identification
- Merchant website or app URL
- Product category and risk description
- Expected volume, average ticket, currency, and target buyer profile
Questions to ask
- Do you onboard foreign entities, or is a Kazakhstan entity required?
- Which methods are live for online merchant collection today?
- Is this a direct bank, wallet, acquirer, or PSP relationship?
- Which refunds, reversals, chargebacks, and failed-payment states are supported?
- Can I review official onboarding and written pricing before launch?
If the official contact route is unclear
LocalPayMap does not yet list public Kazakhstan PSP contact leads. Treat the listed methods as screening inputs, then verify live merchant support, entity requirements, settlement, refunds, disputes, and support ownership with the provider before launch.
- Which methods are live for online merchant collection today?
- Is this a direct bank, wallet, acquirer, or PSP relationship?
- Which refunds, reversals, chargebacks, and failed-payment states are supported?
- Can I review official onboarding and written pricing before launch?
Route comparisons
How local customers usually pay
Kazakhstan is digital-wallet and card friendly, with Kaspi Pay and bank app ecosystems playing an important role in everyday consumer payments. Cards remain important, but local shoppers may expect QR, bank app, payment link or wallet experiences. Merchants should ask whether a provider supports Kaspi-related flows, local cards, account transfers, refunds and reconciliation in a way that matches the business model. Foreign merchants should verify whether a Kazakh entity, local bank account, tax registration or local contract is needed for domestic methods. Cross-border ecommerce may be possible through global cards, but that is not the same as full local coverage.
- Local cards and bank app payments. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Kaspi Pay or QR/payment-link routes where available. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
- Global card PSP route for early cross-border testing. Confirm customer experience, failed-payment handling, refund path and settlement impact before launch.
Payment methods to check first
For Kazakhstan, begin with the methods that match real customer behavior, then map each one to a provider that can actually onboard your merchant. Current public records point to Digital wallet, General commerce, Instant payment, Bank transfer and Payment aggregator, but availability can vary by PSP, entity type and industry.
- Start with the payment method customers already recognize, not the provider with the longest logo wall.
- Check whether the method supports online checkout, payment links, QR, app redirects, refunds and clear transaction references.
- Keep one fallback method for buyers who cannot or will not use cards.
- Document which method is mandatory for launch and which can wait for phase two.
What to do if you do not have a local company
Do not assume a foreign company can use the same route as a local merchant in Kazakhstan. Some PSPs can onboard overseas entities, some require a local company and local bank account, and some support only selected industries. The cleanest first email states your incorporation country, product, website, expected volume, average order value, customer location, settlement currency and refund model.
- Ask whether foreign entities are accepted directly or only through a local subsidiary, distributor or merchant-of-record arrangement.
- Confirm local company, tax ID, local bank account, local director, licence and proof-of-address requirements.
- Ask which settlement currencies and payout countries are supported for your entity.
- Get the onboarding answer in writing before promising a local method to customers.
PSP and four-party provider screening
Use provider discovery to separate customer-facing payment brands from the companies that can legally process and settle funds. Public PSP/contact leads for Kazakhstan currently include local PSPs, banks, gateways and aggregators. Compare them by eligibility, method coverage, operational support and documentation quality rather than headline pricing alone.
- Ask regional PSPs and local banks which Kazakhstan methods are live for your merchant category.
- Request links to official onboarding, developer documentation, support and pricing pages.
- Do not rely on marketplace claims unless the provider confirms your entity and industry in writing.
Settlement, currency, refunds and disputes
Treat all pricing and settlement information for Kazakhstan as preliminary until confirmed by the official provider or contract. Fees, payout timing, rolling reserves, FX, chargeback costs and refund rules can change by industry, volume, risk review, settlement currency and integration route.
- Ask for transaction fee, fixed fee, refund fee, chargeback fee, payout fee, FX spread, reserve policy and minimum monthly or setup charges.
- Confirm payout timing, settlement currency, settlement account country, failed-payout handling and reconciliation file fields.
- Check whether refunds must return through the original method and whether partial refunds are supported.
- For cards, confirm dispute workflow, evidence deadlines, chargeback fees and fraud-monitoring rules.
Compliance and operating checks
Before launch in Kazakhstan, prepare KYB and risk material as if the provider will ask for it. Most delays for new merchants come from unclear ownership, unsupported industries, missing licences, incomplete websites, weak refund policies or settlement accounts that do not match the merchant record.
- Prepare company registration, ownership, director ID, website/app URL, product description, terms, privacy policy and refund policy.
- Disclose regulated products, digital content, subscriptions, marketplace activity, high-risk categories and cross-border fulfilment.
- Ask how the provider screens sanctions, fraud, AML risk, chargebacks and customer complaints.
- Keep sensitive or restricted markets at compliance-review level; do not use unofficial workarounds.
Questions to ask service providers
Send a concise written checklist to every Kazakhstan PSP or aggregator so responses can be compared side by side. The goal is to expose hidden entity, settlement, support and technical gaps before engineering work begins.
- Which payment methods are live today for my exact merchant entity, industry and customer geography?
- Do you support hosted checkout, API, plugin, payment links, webhooks, sandbox, refunds and reconciliation exports?
- Who is the merchant of record, who handles chargebacks and who owns customer support for failed payments?
- What documents are requested, how is approval reviewed, and what would cause rejection?
- Can you provide official links for pricing, settlement terms, developer docs and support escalation?
Common beginner mistakes
The most common mistake in Kazakhstan is treating payment acceptance as a logo checklist. Local conversion depends on customer habit, provider eligibility, settlement flow, refund support and operational reliability. A cheaper-looking route can become expensive if it cannot settle where you need, cannot refund cleanly or cannot support the methods buyers expect.
- Choosing cards only when wallets, mobile money, bank transfer, QR or cash-style routes are normal for local buyers.
- Building against an API before KYB, entity and settlement eligibility are confirmed.
- Ignoring refund and dispute flows until the first customer complaint arrives.
- Comparing providers without asking the same written questions of each one.
Questions merchants ask
Which payment methods should a new merchant check first in Kazakhstan?
Start with Digital wallet, General commerce, Instant payment, Bank transfer and Payment aggregator. Then confirm which provider can support your entity, industry, customer geography, settlement currency and refund model.
Can a foreign merchant accept local payments in Kazakhstan without a local company?
Sometimes, but it must be verified provider by provider. Ask whether a local entity, local bank account, tax ID, licence, local director or merchant-of-record route is required.
Which PSPs or aggregators are worth screening for Kazakhstan?
Public leads include local PSPs, banks, gateways and aggregators. Treat them as a shortlist for outreach, not as confirmed eligibility or complete market coverage.
Can I use public fee pages as a final quote?
No. Public fees are screening context only. Final pricing can vary by country, industry, volume, risk review, settlement currency, FX, reserves and contract terms.
What operational questions should I ask before integration?
Ask about onboarding documents, restricted industries, live payment methods, checkout flow, webhooks, sandbox, refunds, disputes, chargebacks, reconciliation files, settlement timing and support escalation.
What should I do if the provider has no public sales email?
Use the official contact form, support page or developer contact route, and send a short brief with your entity country, product, volume, currencies and required payment methods.