Market finder

Find PSPs by market

Browse PSPs, acquirers, wallets and gateways by country. Add your industry and entity context for the questions to ask, or contact LocalPayMap if you cannot find a suitable route.

Selected market: KazakhstanPublic contact leads: 0

Decision summary

Kazakhstan: who to contact and what to ask

0 public leads: 0 with public email, 0 form-only, 0 official-page-only.

Entity status is still unclear. Write down company jurisdiction, settlement currency, target customers, industry, and expected volume before asking providers about eligibility.

No industry selected. If this is gaming, short drama, SaaS, travel, or marketplace activity, state it clearly before asking for pricing.

Regional planning

Planning more than one country?

Use a regional hub to narrow the provider categories first, then verify each country route before implementation.

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?

3
wallet_or_bank_app · curated

local wallet or bank-app payment route

Kaspi.kzQiwi Wallet

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_acquiring · curated

bank transfer or bank-sponsored acquiring route

Halyk BankForteBankAltyn Bank

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 · curated

payment aggregator or PSP route

Freedom Pay

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?
KYB prep

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
Due diligence

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?
Contact route fallback

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?

Not enough public leads yet

Public contact coverage is still thin for this market. Submit your target market, industry, and entity context so LocalPayMap can help structure a public-information shortlist.

Ask LocalPayMap on WhatsApp

Questions to ask before integration

  • Does this provider support my merchant entity location, industry, and transaction model?
  • Is a local company, local bank account, tax registration, licence, or local contact required?
  • Which local wallets, bank transfers, card acquiring, refunds, and dispute flows are actually supported?
  • What settlement currency, timing, reserves, chargeback fees, and contract fees apply in writing?
  • Are API, plugins, webhooks, sandbox, reconciliation exports, and go-live support available?

Pricing and settlement caveat

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.