What do I search to verify the licence claim?

Search OGL/2024/832/042 via the regulator flow, then confirm BETQUEST B.V. is the licensee/operator.

Why do I see FUNOPTIC LTD on payment descriptors?

Because it is disclosed as the payment agent; descriptor formatting is bank/provider dependent.

What if the operator stops operating?

This page describes no automatic compensation scheme. Your leverage is your evidence pack + documented escalation path.

Knowledge base

BetJam Kenya licensing information

This page is written to help you separate “claims” from “verifiable identifiers” and to collect a clean evidence pack if anything goes wrong. It’s not a marketing page; it’s a practical checklist for Kenya.

Legal disclaimer: Informational transparency only (not legal advice). Gambling involves financial risk. Access is 18+ and only where online gambling is lawful for you.

Quick facts (copy/paste safe)

Item	Value
Regulator	Curaçao Gaming Control Board (CGCB)
Licence ID	OGL/2024/832/042
Stated effective date	1 October 2024
Operator (legal entity)	BETQUEST B.V.
Operator registration no.	164560
Disclosed payment agent	FUNOPTIC LTD
Payment agent registration no.	HE 452385
Terms-change notice (stated)	minimum two weeks

What this licence route usually implies for Kenya (short, practical)

Think of a Curaçao licence as a verifiable identity + process baseline (KYC/AML, disputes flow, basic compliance), not as a guarantee that you’ll get the same consumer remedies you’d expect from a locally licensed Kenyan operator.

What you can do: confirm the licence ID and match the operator name; keep screenshots and timestamps.
What you shouldn’t do: treat it as interchangeable with a Kenya BCLB licence in enforcement style and remedies.

If you’re deciding where to play, licensing is one input into your risk model (not the entire model).

Licence verification (do it like an auditor)

60-second flow

Order matters: regulator → licence ID → licensee/operator match.

Open the official Curaçao Gaming Control Board website.
Find the licence lookup/verification area (labels and layout can change).
Search the licence ID OGL/2024/832/042.
Confirm the returned record matches BETQUEST B.V. as the licensee/operator.

What to save (evidence you’ll actually use)

a screenshot of the regulator result page showing the licence ID
the operator name on that result
the timestamp (your system clock is fine)
the URL you used (copy it into your notes)

If a third-party “badge directory” contradicts the regulator lookup, treat the directory as noise.

Operator identity (who you’re contracting with)

This is the entity responsible for platform terms, verification requests, and complaint handling.

Field	Value
Legal entity	BETQUEST B.V.
Jurisdiction	Curaçao
Registration number	164560
Registered office	Abraham Mendez Chumaceiro 03, Willemstad, Curaçao

Payment agent (why your bank statement may show a different name)

Disclosures describe a payment-agent model: the operator runs the service, while a separate entity can appear in processing/settlement flows depending on provider rails and routing.

Field	Value
Payment agent	FUNOPTIC LTD
Jurisdiction	Republic of Cyprus
Registration number	HE 452385
Registered address	5, A.G. LEVENTIS, THE LEVENTIS GALLERY TOWER, Fl.: 13th, Apt.: 1301, Nicosia, 1097, Cyprus

Keep these artifacts (it saves days later)

transaction ID(s) + timestamps
payment method used
cashier confirmation (screenshots/export if available)
any support ticket IDs

Also note the stated rule-change notice: at least two weeks between announcement and the update taking effect (if you don’t accept the update, the simplest action is to stop using the service before it becomes effective).

Payment methods (don’t treat any list as a promise)

Source materials mention a broad set of methods; real availability is always cashier + your account.

Visa, Mastercard, Astropay
PIX, Mercado Pago, MBWay, Webpay, FPS
Perfect Money, Skrill, Neteller
USDT (TRC-20), BTC, ETH

Treat your in-account cashier list as the only accurate list for your profile.

KYC / AML (what triggers it and what “good docs” look like)

Verification typically appears because of withdrawal flows, provider requirements, and risk scoring (it’s process, not “punishment”).

Typical request packs

Trigger	Typical documents
Withdrawal stage	passport / national ID / driver’s licence
Address verification	proof of address within the requested recency window
Source-of-funds	income/business/bank documentation (case dependent)
Risk clarification	additional items if inconsistencies exist

Fast rejection reasons (avoid re-uploads)

Doc type	What usually breaks it
ID	glare, cropped corners, unreadable text, expired doc
Address proof	mismatch with profile, missing date/name, too old
SoF	no clear trail from income → funding method

Kenya note (BCLB vs international licence)

Kenya’s BCLB regulates locally licensed operators. A Curaçao-licensed service is a different route, which can change complaint pathways and remedies. Don’t treat “international” and “local” as the same category.

Self-checks you can do without trusting anyone

Check	What it tells you	Where you check
TLS/HTTPS	encryption in transit	browser certificate details
2FA availability	stronger account access control	account security settings
Fraud monitoring presence	controls exist around suspicious patterns	usually visible only through compliance outcomes

For casino fairness/testing, evidence is usually provider + specific title. If you want proof, use the game/provider documentation rather than generic footer badges.

Disputes (treat it as a case file)

Step 1 — open a support case

Live chat (where available)
Email: [email protected]
Form: Contact form

Step 2 — switch to formal complaints if it’s not resolving

Email: [email protected]
Include: user ID, timestamps, transaction references, prior ticket IDs

Step 3 — escalate to CGCB after internal exhaustion

Prepare an evidence pack (correspondence log, identifiers, transaction refs, screenshots, supporting files). Regulator review is oversight and does not guarantee a particular outcome.

Minimal complaint template (copy, fill, send)

Subject: Complaint — account [ID], issue [short label], date range [YYYY-MM-DD → YYYY-MM-DD]

Body:

Account ID / username:
Issue summary (1–2 sentences):
Timeline (UTC+3 or your local time):
Transactions involved (IDs, amounts, methods):
What resolution you request (specific):
Evidence list (screenshots, statements, chat exports):
Previous ticket IDs:

FAQ

It is disclosed as operating under a Curaçao remote licence, not a Kenya BCLB licence. Your legal position depends on current Kenyan rules and your circumstances.