You can build the best sportsbook and casino in a market and still lose the player at the deposit screen. Payments are where product promises meet local reality, and nowhere is that more true than in South Africa.
Over the past six months we have shipped release after release focused on one goal: a payment experience that feels native to South African players, not translated for them. Here is what that stack looks like today, and the thinking behind it.
Meeting players on the rails they already use
South African players do not deposit one way. Some reach for a card. Some live inside their banking app. Many buy a voucher at a till with cash. A payment stack that only covers one of those behaviours quietly filters out everyone else.
That is why our iGaming platform now runs a broad, locally-tuned set of methods side by side. Through our Stitch integration, players can deposit with cards, digital wallets including Apple Pay and Samsung Pay, Pay by Bank, and the standalone Capitec Pay and Absa Pay flows. These are the channels South African players already trust for everyday spending. Samsung Pay deposits use encrypted on-device payment data, keeping the checkout both fast and secure.
Vouchers as a first-class citizen
In many markets vouchers are an afterthought. In South Africa they are a primary deposit rail, so we treat them like one.
BluVoucher deposits now run through a direct integration rather than a gateway, removing steps from the player journey and giving us full control over the flow. The Flash integration supports 1Voucher, Flash Exclusive Vouchers and FNB Vouchers through the same simple 16-digit PIN redemption players already know. And when a voucher fails, invalid or already redeemed, players now see a clear, specific, translatable message instead of a generic technical error. Fewer confused players, fewer support tickets.
Closing the loop on cards
A deposit method that cannot pay you back is half a product. With the Strafin card integration, deposits and withdrawals run through the same provider with card tokenization: a true closed loop where money returns to the card it came from. Alongside it, providers like Safeway and Finera cover both deposits and withdrawals, and Ozow transactions now store the masked account number as the payment instrument, keeping payment records accurate and consistent across the platform.
The details that make it feel native
Localization is not a language file. It is a hundred small decisions. We replaced the term “Fiat” with “ZAR” in the cashier because players should never have to decode financial jargon to see their own currency. Deposit entry points are clearly labelled. And identity, sanctions and bank account verification for the South African market run through a unified FraudCheck flow, so compliance happens consistently behind the scenes. It is the same discipline that stands behind our GLI certifications.
Every one of these changes shipped through our regular release cycle. You can trace them version by version in our public release notes.
What this means for operators
If you are entering South Africa, the payment stack is not a checklist item. It is the difference between a player who deposits and a player who leaves. Running on OpenTag means the local rails, the voucher flows, the closed loops and the compliance checks are already built, tested and live on real brands.
My colleague Ivaylo wrote about how we automate casino merchandising with the same philosophy: build the machinery once, so operators can focus on strategy. Payments are no different.
