Our purpose
CasinoCheck Botswana publishes practical, evidence-led information for people comparing gambling operators, payment options and related risks in Botswana. The aim is to help readers understand what is known, what remains unconfirmed and which questions deserve further checking before they use a service.
Our reviews and guides are written for clarity rather than promotion. We do not treat a polished website, a familiar brand name or a Botswana domain ending as proof that an operator is licensed. We also do not present an unverified statement as an established fact.
How we use sources
We prefer identifiable primary sources for claims about licensing, payment oversight and domain administration. The Gambling Authority’s public bookmaker-licensee list is used for current names, operators, contacts and exact domains shown in those contacts. We describe only what that record supports.
The Bank of Botswana source is used for information about the Bank’s oversight of payment systems and its published electronic-payment regulation and provider information. The MyZaka source is used for the recorded description of MyZaka as a Botswana mobile-money service for sending, receiving, purchases and payments.
The BOCRA source is used for the role of BOCRA in administering the .bw namespace. A .bw address may help identify a domain, but domain registration alone is not treated as a gambling licence.
Sources are checked on a stated date. A dated check does not make information permanent. Public lists, contacts, domains and payment arrangements can change, so readers should treat a review as time-specific information rather than a continuing guarantee.
Licensing claims
We distinguish between a record that identifies a licensee and a conclusion that a particular website is authorised. A public licensee name, operator name, contact detail or exact domain is reported only within the limits of the relevant record. Where the source does not connect a domain to an entity, we do not create that connection ourselves.
We do not infer licensing from branding, advertising, search visibility, customer comments, a payment option or the use of a .bw domain. If the available evidence does not resolve the identity or status of a service, the wording should say that the position is unconfirmed. Readers can consult our Botswana gambling law guide for related context, but that guide does not replace a current authority record.
Operator identity and domain checks
A review may discuss the difference between a brand, an operator, a contact and a domain. These are not automatically the same thing. We reproduce an exact domain only when it appears in the supplied authority record or another accepted source. We do not fill gaps with assumptions based on similar names or redirects.
If a service uses several domains, or if a public record and a live website do not appear to align, the uncertainty is retained. We avoid wording that suggests a confirmed relationship when the evidence shows only a possible association. This protects readers from confusing a domain owner, a brand, a payment service and a licensed operator.
Payment information
Payment content is limited to what the supplied sources establish. The Bank of Botswana material supports statements about payment-system oversight and published electronic-payment regulation and provider information. The MyZaka material supports the description of MyZaka’s functions as sending, receiving, purchases and payments.
Those facts do not establish that every operator accepts MyZaka, that a deposit or withdrawal will succeed, that a transaction will be instant or that a user will recover funds. We do not claim to have made a payment, tested a withdrawal or opened an account unless a separately supplied record directly supports that statement. For practical payment context, readers may use our payments guide, while recognising that availability can vary by operator and account.
Evidence, allegations and unknowns
Our wording separates different kinds of information. A primary record is an official or otherwise direct source relevant to the precise claim. An operator statement is attributed to the operator and is not silently upgraded into independent verification. A user report is treated as contextual information, not as proof of a general pattern.
A complaint or warning is not rewritten as a finding unless a dated competent-source record establishes the adverse fact. Where records conflict, we identify the conflict or leave the point open. We do not invent missing dates, quotations, legal entities, licences, payment methods, withdrawal outcomes, screenshots or personal experiences.
The absence of a record in the material available to us is not automatically proof of wrongdoing. It may simply mean that the available evidence does not answer the question. Our methodology explains this evidence-led approach in more detail.
Updating and corrections
Information is reviewed against the date shown with the source. When a material record changes, we aim to update the affected wording, source date and any conclusion that depended on it. A later review does not erase what an earlier source said; it should make the time difference clear.
Readers who identify an incorrect domain, outdated contact, misleading description or source mismatch can contact us through Contact. A correction request should identify the precise statement, explain why it is inaccurate and provide a reliable supporting record where one is available.
We assess corrections for relevance, evidence and clarity. We do not promise that every submission will be adopted, and a request alone is not treated as proof. We may preserve cautious wording when the evidence remains incomplete or conflicting.
Independence and commercial boundaries
Editorial conclusions are not determined by whether a brand is well known, whether it appears in a search result or whether a reader prefers it. We do not turn an operator’s marketing language into an editorial endorsement. Descriptions should remain proportionate to the evidence and should make meaningful uncertainty visible.
This route has no commercial call to action. Internal links are provided to help readers reach related information, not to imply that a service is approved or suitable. Readers remain responsible for checking current terms, identity details and applicable requirements before deciding whether to use any gambling or payment service.
What readers should check
Before relying on a statement about an operator, compare the precise domain and entity with the latest relevant public record. Do not assume that a .bw address proves gambling authorisation. For payment claims, distinguish between a provider offering a payment service and an operator actually supporting that method for a particular account.
Keep the date of the information in mind. If the identity, licence position, contact details or payment route cannot be matched clearly, treat the matter as unresolved rather than relying on confidence created by branding or convenience.
gamblingauthority.co.bw · bankofbotswana.bw · mascom.bw · nic.net.bw
Frequently asked questions
Does a .bw domain prove that a gambling operator is licensed?
No. The supplied BOCRA record concerns administration of the .bw namespace. Domain registration alone is not treated as a gambling licence.
Do you test deposits and withdrawals?
No test is claimed unless a separately supplied record directly supports it. Information about a payment service does not prove that a particular operator accepts it or that a transaction will succeed.
How do you treat complaints?
A complaint is treated as an allegation unless a dated competent-source record establishes the adverse fact. User reports can provide context but are not automatically proof of a general pattern.
Can an operator’s statement be treated as verification?
An operator statement is attributed to the operator. It is not silently presented as an independent primary finding when the supplied evidence does not verify it.
Why do you show source dates?
Licensing lists, contacts, domains and payment information can change. A source date shows when the information was checked and helps readers judge whether a further check is needed.
How can I request a correction?
Use Contact and identify the exact statement, explain the suspected error and provide reliable supporting material if available. A request is reviewed, but it is not itself proof.