Kaspl
For a Kazakhstan-licensed sportsbook, Kaspi is close to a mandatory local rail—two-way, settling in tenge, and the way almost every adult in the country already moves money. For any offshore or online-casino brand, it is effectively closed: Kaspi is a licensed bank inside Kazakhstan’s payment-blocking regime, and there is no global “Kaspi gateway” to integrate—you reach it through a Kazakh acquirer, where gambling-MCC card/QR acquiring runs an indicative ~2–4%+ MDR (well above Kaspi’s ~1.10% blended take rate). With roughly 15.7 million active users at end-2025—about 76.5% of the population—Kaspi is what decides deposit success in this GEO.
WHY OPERATORS CHOOSE KASPI
The reason to care about Kaspi is coverage, not features. In Kazakhstan, a payment method either works with Kaspi or it barely works at all: the super app is the default wallet, card issuer, and transfer network for the mass market, and licensed local sportsbooks such as Parimatch.kz, Olimp.bet, and 1xBet.kz already lean on it for tenge deposits and cash-outs. If you hold a Kazakh betting license and your cashier cannot credit a Kaspi Gold card, you have a conversion problem, not a nice-to-have gap. That relevance is also strictly bounded—Kaspi is a Kazakhstan solution, not a regional or global one, and it is unavailable to anyone the state has not licensed.
What Kaspi buys a licensed operator
For a licensed operator, Kaspi’s pull reduces to reach, player trust, and cheap domestic movement—here is what each one delivers.
Whole-market reach in one rail. Kaspi gives a licensed operator near-total consumer reach through a single destination—15.7 million active users at end-2025, on top of 14.6 million active payments consumers in FY2025—so a Kaspi-capable cashier reaches the entire addressable market, and because payouts can land back on a Kaspi Gold card or Kaspi account, deposits and withdrawals run through one familiar rail rather than several minor local ones.
Deposits players already trust. For the player, Kaspi is muscle memory: they fund from the same app they use for groceries, utilities, and P2P transfers, in tenge, with no card-number entry on QR or in-app flows. That familiarity lifts deposit completion in a market where trust in unfamiliar checkouts is low.
Cheap domestic tenge movement. Kaspi’s own blended payments take rate is about 1.10% of total payment volume, which anchors how cheap everyday tenge movement is—though gambling acquiring sits well above that (see costs). Settlement is local and in tenge, so a Kazakhstan-licensed entity avoids cross-border FX on the deposit leg.
Proven, high-volume plumbing. The consumer rails Kaspi exposes—Kaspi QR, in-app payment, card issuance on Visa/Mastercard, and “to card”/“to phone” transfers—are mature and high-volume (KZT 44.22 trillion, roughly USD 90 billion, across 6.72 billion transactions in FY2025), so the local acquirer you connect through works with proven, well-instrumented flows rather than a fragile niche method.
Where Kaspi is gated
The constraints are almost entirely regulatory, and they settle eligibility before any commercial question is even asked.
Licensing is the whole gate. Online casinos are explicitly prohibited in Kazakhstan, and online sports betting is legal only through a small set of locally licensed bookmakers. Kaspi, as a licensed second-tier bank, is obligated to block payments to unlicensed and offshore gambling—so “can I use Kaspi?” reduces to “am I licensed here?” If you are not, this method is off the table, full stop.
No merchant gateway to plug into. There is no public Kaspi API for gambling merchants. You do not integrate Kaspi the way you integrate a PSP; you integrate a Kazakh acquirer that carries Kaspi rails, and that acquirer must be willing to board a gambling MCC. If you are unsure which local acquirers will board your license and route to Kaspi, the GR8_TECH team can map that against your target setup before you commit your roadmap to it.
Declines are compliance blocks, not soft declines. The most common failed Kaspi deposit here is not an issuer decline—it is a regulatory block. Between October 2025 and March 2026, Kazakh second-tier banks rejected more than 400,000 transactions tied to blacklisted gambling companies, worth about USD 20.8 million. Staying on the right side of that line is a licensing and routing question, decided before your PSP ever sees the transaction.
One-ecosystem concentration risk. Building a Kazakhstan cashier around Kaspi means depending on a single dominant ecosystem and its risk appetite. If Kaspi tightens gambling controls—or the regulator tightens them for Kaspi—your primary rail moves in one step.
KASPI: MARKETS AND AVAILABILITY
Kaspi is overwhelmingly a one-country method. Revenue is more than 90% concentrated in Kazakhstan, and while the group has begun expanding into Uzbekistan (via the Humo system) and Azerbaijan, those footholds are not gambling-relevant rails today. For an iGaming operator, “Kaspi availability” means one market with a hard licensing gate.
| Market / GEO | Kaspi availability | Operator considerations |
| Kazakhstan | Universal consumer coverage; used by licensed local sportsbooks (Parimatch.kz, Olimp.bet, 1xBet.kz) for tenge deposits/payouts. Bank-level blocking applies to unlicensed/offshore gambling. | Requires a Kazakhstan betting license, a local acquirer/PSP willing to board the MCC, and routing through the state Betting Accounting Center. Online casino is prohibited outright. |
| Uzbekistan | Early expansion via Humo integration; not a viable gambling rail. | Ignore for iGaming; treat as future-watch only. |
| Azerbaijan | Kaspi owns local classifieds/data assets; no gambling payment role. | Not applicable. |
| Rest of world | Not available. | Kaspi does not serve players outside its Central Asia/Caucasus footprint. |
💡 Kaspi is not usable as a gambling rail anywhere except Kazakhstan, and even there it is closed to unlicensed and offshore operators. There is no scenario in which a non-Kazakhstan-licensed casino or sportsbook can legitimately accept Kaspi.
Kaspi and Kazakhstan iGaming: What Operators Need to Know
Before any commercial conversation, confirm you clear the legal gate—Kazakhstan’s regime is unusually strict and actively enforced through the payment layer.
⚠️ Licensing. Only Kazakhstan-licensed sportsbooks may operate online; online casino is prohibited under the country’s gambling legislation (Gambling Business Law, 2007, as amended). Verify your license covers the exact products in your cashier.
⚠️ Payment blocking is live. In May 2026, the Financial Monitoring Agency directed banks and telecoms to block deposits to unlicensed operators; monitoring firm Blask recorded roughly a 50% drop in Kazakhstan iGaming activity in the following weeks. Kaspi is inside that perimeter.
⚠️ Routing through the Betting Accounting Center. Licensed Kazakh bookmaker turnover is expected to pass through the state betting-accounting infrastructure. Confirm how your Kaspi flows reconcile with that layer before launch.
DEPOSITS, WITHDRAWALS AND SETTLEMENT
Kaspi can move money both ways for a licensed local operator, but “both ways” is conditional on license status and on the acquirer you route through. The table reflects the realistic operator view for a Kazakhstan-licensed sportsbook; for anyone else the honest answer is that deposits do not clear at all.
| Area | Operator view |
| Deposit availability | Available to Kazakhstan-licensed sportsbooks via a local acquirer carrying Kaspi rails (QR, in-app, card, transfers). Blocked for unlicensed/offshore operators. |
| Withdrawal availability | Payouts can be returned to a player’s Kaspi Gold card or Kaspi account through the same local acquirer; support and speed depend on that provider and on responsible-gambling checks. |
| Typical deposit speed | Near-instant for the player when the transaction clears; the constraint is approval, not rail speed. |
| Typical withdrawal speed | Same-day to a few business days, driven by the operator’s payout process and the acquirer’s cadence, not by Kaspi itself. |
| Settlement model | Local, in Kazakhstani tenge (KZT); indicative cadence D+1–D+7 depending on acquirer terms—confirm with the provider. |
| Deposit-only risk | Low in principle for licensed operators (payouts to Kaspi are supported), but payout reliability hinges entirely on the local acquirer, not on Kaspi as a brand. |
| Deposit–withdrawal asymmetry | Deposits via QR/in-app are frictionless; payouts depend on the acquirer’s OCT/transfer support and on player-account matching for RG and AML. |
| What depends on the setup | Everything material: your license, the acquirer that boards you, MCC acceptance, Betting Accounting Center routing, and Kaspi’s own risk posture. |
How Kaspi payouts actually run
Kaspi is a payout destination, not a payout processor you control. For a licensed operator, the withdrawal actually runs through your Kazakh acquirer as a credit to the player’s Kaspi Gold card or Kaspi account—so the reliability, limits, and speed of that payout are your acquirer’s characteristics, not Kaspi’s. Expect same-account rules to matter: paying winnings back to the same Kaspi identity that funded the deposit is both an anti-fraud control and an AML expectation, and it is where most manual review time goes. Because settlement is in tenge and local, there is no repatriation step for a Kazakhstan entity, but a non-resident parent will still face FX and treasury questions when moving funds out. If you need to confirm whether a prospective local provider actually supports Kaspi payouts—not just deposits—the GR8_TECH payments team can pressure-test that provider list against your payout SLAs.
COSTS, LIMITS AND APPROVAL
Because exact terms are set by the local acquirer you board with and by your risk profile, treat the costs, limits, and approval figures below as planning benchmarks rather than quotes.
| Item | Value (indicative unless stated) |
| MDR / transaction fee | Indicative ~2–4%+ for gambling-MCC card/QR acquiring in KZT; payouts typically priced separately per transaction. Kaspi’s blended group take rate is ~1.10% (FY2025)—a floor for everyday payments, not a gambling rate. |
| Rolling reserve | Common for gambling MCCs; indicative 5–10% held for a rolling period—confirm with the acquirer. |
| Settlement cadence & currency | Indicative D+1–D+7; settlement in KZT. |
| Deposit limits | Set by acquirer and RG rules; per-transaction and daily caps are standard. Confirm during onboarding. |
| Withdrawal limits | Set by acquirer and AML thresholds; larger payouts trigger enhanced review. |
| Indicative approval rate | High for eligible licensed flows; the dominant decline reason is a compliance/blacklist block, not issuer failure. Reduce declines by confirming license coverage, correct MCC boarding, and Betting Accounting Center routing before launch. |
| FX/repatriation | None for a KZT-settling Kazakhstan entity; relevant only if a non-resident group repatriates funds. |
BUILDING THE PAYMENT STACK AROUND KASPI
Even where Kaspi is available, it covers one job—mass-market tenge deposits and payouts for a licensed operator—so a resilient Kazakhstan cashier needs redundancy and reach around it. The layers below are the ones that actually matter for this method and this GEO; generic “add cards and wallets” filler does not.
| Complementary payment layer | Why operators need it | Priority markets |
| Local KZT card acquiring (Visa/Mastercard) | Redundancy if a Kaspi-specific route degrades; many players hold non-Kaspi cards too. | Kazakhstan |
| A second Kazakh acquirer/PSP | Avoids single-provider dependency on one boarding decision or risk posture. | Kazakhstan |
| Alternative local bank rails/transfers | Reaches players who prefer bank transfer or hold accounts elsewhere. | Kazakhstan |
| Payout orchestration | Routes withdrawals across providers to protect payout SLAs when one channel throttles. | Kazakhstan |
| Reconciliation and monitoring layer | Ties Kaspi-routed flows back to Betting Accounting Center reporting and AML monitoring. | Kazakhstan |
💭 In a market this concentrated, the risk is not choosing the wrong rail—it is having only one. The operators who stay live through enforcement waves are the ones with a second acquirer and orchestrated payouts already wired in. Talk to the GR8_TECH team about building that redundancy into a single cashier rather than bolting it on after the first block.
How operators access Kaspi
There is no direct merchant integration with Kaspi for gambling. Access runs through a Kazakh acquirer or PSP that already carries Kaspi’s rails—QR, in-app, card, and transfers—or through an orchestrator that aggregates local providers, so the build is a standard local-acquirer integration plus boarding rather than a bespoke Kaspi connector. The operator-facing names are those local acquirers, not Kaspi itself; the licensed sportsbooks already running it (Parimatch.kz, Olimp.bet, 1xBet.kz) prove the route exists, but each brand must secure its own gambling-MCC boarding. Expect the integration to return payer identity for same-account payout matching, a transaction reference, an acquirer status/webhook model, and a KZT settlement report—fields you should map to your Betting Accounting Center obligations from day one. Plan onboarding in weeks, not days: the long pole is the license check, not the code, and the gating documents are your Kazakhstan gambling license, ownership and UBO details, target products, expected volumes, and processing history.
MOST COMMON FRAUD AND RISKS
Kaspi’s own rails are well-instrumented, but the risks that bite an operator here are structural and compliance-driven as much as classic payment fraud. The provider (your local acquirer, and Kaspi behind it) mitigates some; the rest stay in your fraud and RG stack.
Regulatory/blacklist blocking. The single largest “loss” event is not fraud—it is a legitimate deposit blocked because the operator or route is deemed unlicensed. This is mitigated only by correct licensing and routing, and it sits entirely with the operator.
Third-party funding and ownership mismatch. A player funding from a Kaspi account that is not their own undermines both AML and RG controls. Same-account payout matching is your first line of defense; the acquirer can support it but cannot own it for you.
Layering across Kaspi’s P2P transfers. High “to card”/“to phone” velocity on Kaspi can be abused to move and layer funds. Transaction monitoring on your side must flag rapid deposit–withdrawal cycling regardless of how clean the rail looks.
💭 None of these are reasons to avoid Kaspi where you are licensed—they are reasons to keep KYC, AML, and responsible-gambling controls firmly in your own stack rather than assuming the dominant local rail handles them.
COMPLIANCE
Working through Kaspi does not move your obligations onto Kaspi. The provider layer reduces plumbing work; ownership of KYC, AML, responsible gambling, and Kazakhstan-specific gambling-payment rules stays with the operator.
| Domain | Provider position | Operator implication |
| PCI DSS | Handled at the acquirer/Kaspi rail level for card and in-app flows. | Keep your own integration and data handling in scope; do not assume full transfer of PCI burden. |
| SCA / authentication | Kaspi in-app and QR flows carry strong native authentication. | Add step-up and payout-change checks in your own flow; native auth is not a substitute. |
| AML & KYC | Kaspi and the acquirer perform their own onboarding checks. | You still run full player KYC/AML and Kazakhstan-specific reporting; provider checks do not cover the operator’s duties. |
| Account ownership | Rails expose payer identity for matching. | Enforce same-account deposit/withdrawal matching; own the exception handling. |
| Responsible gambling | Not the payment provider’s remit. | RG limits, self-exclusion honoring, and intervention are entirely yours. |
| Data protection | Kazakhstan personal-data law applies to local processing. | Confirm lawful basis and data-residency handling with your provider and counsel. |
| Local gambling-payment restrictions | Kaspi actively blocks unlicensed/offshore gambling as a licensed bank. | Only licensed products routed correctly will clear; verify coverage before launch. |
| Recordkeeping & reporting | Acquirer provides settlement and transaction reports. | Reconcile to Betting Accounting Center obligations and retain records per Kazakhstan rules. |
| Sanctions screening | Performed by the bank/acquirer at their level. | Maintain your own screening; do not rely solely on the rail. |
⚠️ The uncomfortable truth to design around: in Kazakhstan, the payment layer is the enforcement layer. Compliance failures here do not show up as fines first—they show up as blocked deposits and a dead cashier.
KASPI: THE OPERATOR TAKEAWAY
For a Kazakhstan-licensed sportsbook, the question is almost rhetorical—Kaspi is the market. With roughly 15.7 million active users and 76.5% population penetration at end-2025, a cashier that cannot credit a Kaspi Gold card is leaving the majority of Kazakh players unreachable. The licensed local operators already prove the route works, and where you clear the license gate, Kaspi should be a primary tenge rail, integrated through a local acquirer and backed by a second provider and orchestrated payouts for resilience.
For everyone else, the answer is equally clear and worth stating plainly: Kaspi is not a way into Kazakhstan. It is a licensed bank inside an actively enforced blocking regime, with no merchant gateway for offshore gambling and hundreds of thousands of transactions already rejected in a single six-month window. There is no clever routing around that. Kaspi is one rail inside a compliant Kazakhstan stack—decisive when you are licensed, unavailable when you are not.
Share
