All Slots Casino Kenya: identity, domain and licence evidence

The Kahnawake identity chain and its limit

The captured Kahnawake Gaming Commission permit-holder page binds three useful pieces of information together: a foreign regulator record, the legal name Baytree Interactive Limited and the domain allslotscasino.com. It is the clearest supplied primary source for answering which entity and host are associated with All Slots Casino.

That chain has a strict jurisdictional boundary. A permit appearing in a Kahnawake record is evidence about the status recorded by that authority. It does not transfer into a Kenyan authorisation, replace a GRA Kenya entry or settle whether services may lawfully be offered to a person in Kenya. Foreign authorisation proves identity only for this assessment and never transfers to the target country.

The primary identity record can be inspected in the Kahnawake Gaming Commission permit-holder record. It should be read as a foreign permit-holder source, not as a Kenyan licence record.

Kenya status: what remains open

GRA Kenya is the local licensing source supplied for this assessment. Its captured source is labelled “Licensed gaming companies 2025/2026”, and the ledger expressly requires the current licensing period to be recaptured before publication. That timing condition prevents a stronger local conclusion from being drawn from the preserved material.

An amber signal is therefore appropriate. It records an open evidence question rather than a finding of wrongdoing, illegality or non-existence. A green signal would require current primary Kenyan evidence matching the precise legal entity and domain. A red signal would require an official adverse record or corroborated documented adverse evidence, neither of which is supplied here.

Before making a decision, compare the entity and host against the current GRA Kenya licensed-operator source and follow the practical steps for checking a GRA gambling licence. A name that looks similar is not enough: spelling, legal suffix, domain and licensing period should align.

Verified domain evidence without a direct casino link

The domain supported by the captured Kahnawake record is allslotscasino.com. It is stated here as evidence, not provided as a clickable casino destination. Avoid treating search advertisements, shortened links, messaging-app links or lookalike domains as confirmation of the official host.

The domain evidence is meaningful because it comes from an official foreign permit-holder record and is reinforced at the identity level by two independent sources. Gambling Insider Canada identifies the relationship between All Slots Casino and Baytree Interactive Limited in its independent All Slots review. Fruity Slots also identifies the All Slots and Baytree relationship in its independent review record, while not establishing Kenyan authorisation.

Neither independent publisher is a regulator. Their role is corroborative context for identity, not licensing authority. Their pages cannot establish GRA Kenya approval, guarantee that a payment recipient belongs to Baytree Interactive Limited or prove that every site using the All Slots name is genuine.

For a method that separates host evidence from branding, use the Kenyan casino domain verification checklist. Suspected copies or deceptive hosts can also be assessed using the clones and phishing guide.

Operator identity is not the same as payment identity

Even where the domain and operator relationship are supported, a payment may involve a separate payment provider, merchant descriptor, bank acquirer or mobile-money recipient. The supplied sources do not identify an M-PESA paybill, till number, bank account, card descriptor or payment provider for All Slots Casino. No specific payment method should therefore be treated as verified from this evidence packet.

In particular, there is no supplied evidence establishing that All Slots Casino accepts M-PESA in Kenya. A promotional statement, chat message or familiar logo would not by itself prove who receives or controls a payment. If an M-PESA instruction appears, record the paybill or till, account reference, recipient name shown before confirmation, transaction code, amount and timestamp. Cancel rather than confirm if the displayed recipient conflicts with the expected merchant and the discrepancy cannot be explained through verifiable records.

A transaction should be proved through records from the payment provider and the account, not through a cropped balance image alone. For a recipient-name discrepancy, follow the M-PESA paybill-name mismatch evidence steps.

Withdrawal claims cannot be verified here

No withdrawal test, withdrawal speed, KYC result or successful cash-out record was supplied. It would be unsafe to describe withdrawals as fast, delayed or reliable. The evidence supports neither a positive performance claim nor an adverse finding.

If a withdrawal is pending, preserve the request time, amount, status, account identifier and every later status change. Record any identity-document request and the date on which you responded, but redact unnecessary personal information when sharing a complaint bundle. If a fee is requested before funds can be released, do not assume it is legitimate merely because the request uses the casino’s name. Preserve the demand and consult the guidance on a fee requested before withdrawal.

A useful withdrawal chronology separates four events: the request submitted by the player, acceptance or rejection shown by the account, any payment reference issued by the operator, and actual receipt by the bank or mobile-money account. Those events may occur at different times, and one screenshot rarely proves all four.

Complaints: allegations, records and reporting routes

No complaint count, substantiated complaint outcome or official adverse finding is included in the supplied evidence. A user complaint should remain an allegation unless transaction records, correspondence and a competent dated decision establish more. Repetition on forums or social media would not turn an allegation into a regulatory finding.

Start by sending a concise written complaint through the contact route available in the account relationship. State the account identifier, disputed transaction, relevant dates, requested resolution and a reasonable response deadline. Do not send passwords, PINs or one-time codes. Keep the original message and any acknowledgement rather than relying only on screenshots of a conversation.

If the issue concerns possible Kenyan licensing or conduct within GRA Kenya’s remit, use the guide to complaining to GRA Kenya. If the issue concerns an unrecognised card charge, first contact the issuing bank promptly and preserve the statement descriptor; the unrecognised gambling charge guide explains how to organise that record. Suspected phishing should be treated as a security incident rather than an ordinary withdrawal dispute.

Evidence-preservation checklist

Create a chronology before messages disappear or account displays change. Preserve original files where possible and keep a working copy with sensitive details redacted for routine sharing.

1. Record the full domain exactly as displayed, including the protocol and any subdomain.
2. Save the date and time of access and a full-screen capture showing the browser address bar.
3. Preserve the disclosed legal entity name and any licence identifier exactly as written.
4. Export or save deposit and withdrawal ledgers, including pending, cancelled and rejected entries.
5. Retain payment-provider receipts, transaction codes, merchant descriptors and recipient names.
6. Save complete support conversations with timestamps, case numbers and attachments.
7. Keep copies of the complaint sent, delivery evidence, acknowledgement and response.
8. Write a short chronology linking each claim to a document without editing the originals.
9. Redact passwords, PINs, one-time codes, full card numbers and unnecessary identity data from shared copies.
10. Recheck the current GRA Kenya register because the preserved local source covers the dated 2025/26 table only.

A strong bundle distinguishes observed facts from conclusions. “The account showed pending at 14:20” is an observation; “the operator stole the funds” is a conclusion requiring much more evidence. File names that include dates and event types make later review easier.

Dated source record

All four accepted records were checked on 23 August 2026. Their roles differ and should not be blended.

The local register’s date limitation is decisive for the amber signal. The Kahnawake record supplies a useful entity-domain chain, while the two independent records reinforce that identity relationship. None converts foreign evidence into Kenyan permission.

Practical decision point

The evidence supports a cautious sequence: confirm the exact host, identify the legal entity, recapture the current GRA Kenya licensing period, and preserve payment records before relying on any transaction claim. If an exact current local match cannot be established, treat Kenyan status as unresolved rather than filling the gap with a foreign permit, review-site statement or casino-branded badge.

Do not infer M-PESA availability, withdrawal performance or complaint history from the identity chain. Those are separate questions requiring separate records. The amber finding may change if current primary Kenyan evidence later binds the same entity and domain, or if an official adverse record emerges.

Continue only after completing the identity and evidence checks

Frequently asked questions