A licence, registration, transaction order, and technical certificate answer different questions. This guide separates those boundaries before a buyer treats any one record as a route to launch.
It is an interpretation model, not a provider register or legal advice. The full entity-level records remain in the dated credential tracker; regulator terminology and requirements must be checked for the proposed entity, product, and market.
Document-to-decision path
Status matters only after the holder and permission scope are clear. An active certificate can still be the wrong document for market access; a verified record can accurately show that an application is only pending.
Start with the holder, applicant, supplier, operator, buyer, and counterparties. A group brand is not a substitute for the entity written into the record.
Determine what the entity may operate, supply, host, transact, submit, or certify. Local category names can be narrower than their ordinary-language meaning.
Keep the credential or order ID apart from an entity tracking number, workbook section, registry stream, class, and historical Board File reference.
Active, pending, inactive, and unknown describe the record. Verification describes certainty about that state. Neither axis can replace the other.
Record the operator, product, content, testing, payment, market-access, contract, and go-live decisions that this document does not settle.
Axis one · normalized permission kind
Counts are relationships in the current structured dataset, not a claim about the total number of licences held by each group. Each example is selected from the live provider records rather than written into this page by hand.
The named entity's recorded permission for the stated activities, brands, sites, products, territory, and term.
That another buyer can borrow or inherit the permission, that every supplier module is approved, or that a new brand can launch without its own decisions.
Recorded example
Recorded scope and boundary
Active remote Casino, Bingo, Gambling Software, real-event betting and virtual-event betting activities
The supplier entity and activity expressly recorded by the authority for the stated market and term.
A buyer's operator eligibility, approval of every module or game, market access, a hosted route, or permission to contract through another group entity.
Recorded example
Recorded scope and boundary
Michigan Supplier License - Internet Gaming for Pariplay USA Ltd; operator approval and approval for other Aristocrat Interactive modules remain separate
Only the holder, buyer or brand, domain, activities, products, oversight, and territory actually named in the authority or attributable operating record.
A portable licence owned by the buyer, universal sublicensing, availability in another jurisdiction, or undisclosed rights under a supplier's group licences.
Current verified example: not confirmed for this permission kind.
The exact product, parties, transaction, conditions, and dates written into the decision.
Plenary supplier licensure, approval for unnamed counterparties, approval of every technical submission, or continuation after the recorded term.
Narrow transaction-decision example
Recorded scope and boundary
Roxor Gaming, Ltd. is the order applicant. The order renews PRN 0212601 and approves 16 named internet-gaming transaction chains through 1 February 2027; Pariplay USA Limited is named in 12 of those chains. Product submissions remain subject to separate DGE technical approval, and the order is not plenary Pariplay CSIE licensure.
Conformity or testing evidence for the named system, version, standard, control scope, and assessment period.
An operator or supplier licence, market access, approval of a different build, live production performance, or contractual service levels.
Recorded example
Recorded scope and boundary
GiG Core and GiG Data information-security processes under ISO 27001:2013; current certificate and transition status remain unconfirmed
Axes two and three · fields and record state
These lenses can apply to any permission kind. The same B2B record can carry an entity tracking number, a registry section, an active status, and verified certainty without those fields becoming interchangeable.
That the exact entity appears under the literal authority field or heading captured in the record.
A credential number the authority never called a licence ID, a broader permission than the listed class, or approval of every product associated with the brand.
Entity-tracking and section example
Recorded scope and boundary
Michigan Supplier License - Internet Gaming for Pariplay USA Ltd; operator approval and approval for other Aristocrat Interactive modules remain separate
Registry stream and class example
Recorded scope and boundary
Registered as an iGaming Critical Gaming Systems Provider and iGaming Platform Provider; not an operator registration or approval for every group product
Only the exact recorded state and scope, such as a pending application or an elapsed term.
Active permission, rejection, continuation during renewal, current registry presence, or approval under an unidentified entity.
Pending-status example
Recorded scope and boundary
Sports Wagering Manufacturer application
Non-current-status example
Recorded scope and boundary
Legacy 365/JAZ sublicense under the former Curaçao framework; the former sublicense system and orange seals are no longer valid
Procurement handoff
Require the respondent to map each proposed module to the contracting entity, permission kind, authority record, status, term, product scope, and unresolved decision. A logo wall, country list, certificate badge, or statement that licensing is supported is not a completed map.
No. A B2B record concerns the named supplier and stated software, system, content, or service scope. The buyer still needs the operator structure and every product, content, testing, payment, and market-access decision required for its project.
Not unless the authority itself labels it that way. This project preserves entity tracking numbers, workbook sections, registry streams, and classes under their literal labels instead of turning them into credential IDs.
The product label alone does not establish that. A usable hosted route needs evidence for the licence holder, buyer or brand, domain, activities, products, jurisdiction, approval process, and regulatory responsibilities. Those boundaries are deal- and market-specific.
Yes. Verified describes certainty about the recorded state, not a favourable outcome. An application can be pending, a term expired, or a status unknown without becoming active permission.
No. Certification can support a technical submission for the tested system and version, but it does not replace operator, supplier, product, content, integration, or go-live approval and does not establish production reliability.
This page explains how to classify and question a record. The licence tracker is the dated entity-level dataset. Use this guide to interpret a kind or status, then inspect the exact entity, scope, status, and term in the tracker.