A casino “network” may connect brands, licence holders, platform suppliers, affiliates, payment processors and owners across several countries. Similar websites or shared technology do not prove common control. A defensible investigation defines each relationship, verifies it independently and distinguishes infrastructure from legal responsibility.
Define the network question
State whether the enquiry concerns ownership, licensing, payments, software, marketing, player accounts or regulatory responsibility. Record the exact domains, brands, dates and customer markets involved. Without that scope, investigators can mistake ordinary white-label services for ownership or combine unrelated businesses.
Verify each licence holder and domain
Search the competent regulator’s register for the exact legal entity and website. Capture licence status, permitted activities, trading names, domains and enforcement history. The UK Gambling Commission advises consumers to compare a site’s claimed licence with its public-register entry and listed domain. Apply the same exact-domain method in our licence-verification guide.
Build separate relationship layers
Create maps for legal ownership, directors, licences, technology, payment flows, domains, customer support and marketing. Keep the layers separate until evidence connects them. Shared odds, game catalogues, design, hosting or service providers may suggest a commercial relationship but do not, alone, establish ownership or control.
Trace companies and beneficial owners
Collect registry filings, shareholder records, accounts, director histories, trademarks and material contracts. Identify the natural persons who ultimately own or control each entity, and record gaps or jurisdictional limits. Compare registered ownership with who appoints management, funds operations and receives distributions.
Follow the money
Map deposits, withdrawals, merchant descriptors, payment agents, gateways, banks and crypto wallets. Reconcile customer transactions across the chain and identify the contractual recipient. Use the role-based method in our payment-agent investigation; a processor’s presence does not establish knowledge or complicity.
Test technical connections carefully
Preserve DNS, certificates, analytics identifiers, app-publisher details, code, account behaviour and support contacts with timestamps. Technical overlap can change and may reflect a common vendor. Corroborate it through contracts, filings, invoices or communications before drawing conclusions.
Match responsibility to the relevant period
Ownership, licences and service agreements change. Build a timeline showing who operated the customer-facing service when the disputed activity occurred. Do not attribute later conduct to a former owner or assume a current licence covered an earlier domain.
Malta Media’s investigation into possible relationships among betting brands is a useful example of separating account continuity, access tests and matching odds from proof of ownership. Secondary reporting remains a lead that should be checked against primary records and responses.
Publish an evidence matrix
For each asserted connection, list the supporting record, date, alternative explanation, confidence level and response from affected parties. Separate verified corporate links, service relationships, regulator allegations and unresolved similarities. Expert input may help interpret technical, financial or legal evidence, but it cannot replace the evidence itself.