Ontario B2B supplier register

Ontario iGaming platform suppliers: exact entity, registration and term

Four current manufacturer-class supplier registrations connect four provider profiles to four exact legal entities. Each registration is kept separate from the operator route, product acceptance and the actual deployment.

Inspect exact registrations Separate the operator route Run buyer gates

Current status checked August 13, 2026. Page materially updated August 13, 2026.

Supplier registration is one layer of the route

It establishes a current manufacturer-class registration for the named entity and recorded period. It does not become the buyer's operating authority, approve every product, or prove that an integration is live.

Count legal roles separately

Four supplier permissions, plus a separate operator context

The supplier count contains only current exact-entity B2B rows. Three current site registrations held by one operator entity are shown separately and never added to it.

current B2B registrations

exact supplier entities

provider profile contexts

separate operator registrations

Current exact-entity register

Contract against the registration holder

Every row is current, exact-entity and dated. A known end date is a control point for re-checking; it is not an inferred renewal or a prediction about what follows.

CSV JSON

Swipe horizontally to view all columns.

Current Ontario manufacturer-class supplier registrations by exact legal entity, number, provider context and recorded period.
Exact entity / provider context	Registration / status	Recorded period	Permission boundary
Delasport Limited Delasport	GRSM1458238 Recorded active Gaming-Related Supplier - Manufactures	March 17, 2026 through March 16, 2027	The supplier registration belongs to the named B2B entity. It is not an operator registration, an operating agreement, or a hosted route that transfers to a buyer.
Digitain (MT) Limited Digitain	GRSM1487506 Recorded active Gaming-Related Supplier - Manufactures	March 30, 2026 through March 29, 2027	The supplier registration belongs to the named B2B entity. It is not an operator registration, an operating agreement, or a hosted route that transfers to a buyer.
Bragg Gaming Group Inc. Bragg Gaming Group	GRSM1231399 Recorded active Gaming-Related Supplier - Manufactures	April 4, 2026 through April 3, 2027	The supplier registration belongs to the named B2B entity. It is not an operator registration, an operating agreement, or a hosted route that transfers to a buyer.
PARIPLAY USA LIMITED Pariplay	GRSM1227571 Recorded active Gaming-Related Supplier - Manufactures	December 4, 2025 through April 3, 2027	The supplier registration belongs to the named B2B entity. It is not an operator registration, an operating agreement, or a hosted route that transfers to a buyer.

Term-control queue

Re-check in recorded-end-date order

The next supplier term in this set ends March 16, 2027. Procurement should set a review trigger before each date rather than treating today's status as permanent.

1. Delasport Limited

Re-check before March 16, 2027 · GRSM1458238

2. Digitain (MT) Limited

Re-check before March 29, 2027 · GRSM1487506

3. Bragg Gaming Group Inc.

Re-check before April 3, 2027 · GRSM1231399

4. PARIPLAY USA LIMITED

Re-check before April 3, 2027 · GRSM1227571

Separate operator context

Three site registrations belong to one operator entity

These records explain an operator relationship inside one provider profile. They do not add three suppliers, establish Soft2Bet B2B supplier approval, or create a hosted route for another buyer.

Canadix Limited

3 current site-specific operator registrations

Soft2Bet context

These site-specific operator registrations belong to the named operator entity. They are not platform-supplier permissions and do not create a hosted operating route for another buyer.

OPIG1280338

Operator - Internet Gaming registration for tooniebet.ca / Tooniebet

March 5, 2026 through March 4, 2027

OPIG1526283

Operator - Internet Gaming registration for on.betinia.com / Betinia

April 8, 2026 through April 7, 2027

OPIG1456605

Operator - Internet Gaming registration for www.on.swiper.com / Swiper

July 16, 2026 through July 15, 2027

Field contract

Five layers that must not be collapsed

Exact legal entity

The company that carries the registration. A parent group, provider brand and product name are separate identity layers.

Supplier registration

A manufacturer-class B2B permission for the named entity. It is not an operator registration or an operating agreement.

Recorded period

The effective and end dates attached to the current record. No renewal or continuation after the end date is inferred.

Product acceptance

The controlled modules, games, betting products, versions and integrations accepted for a launch. Supplier registration does not replace it.

Deployment

The separate contract, integration, hosting, data-flow and production-acceptance event for one operator route.

Ontario buyer decision path

Turn a current registration into an approvable launch route

A current supplier record clears the entity-and-registration gate. It leaves the operator, product, deployment and continuing-control decisions open.

Lock the exact supplier entity

Which legal entity and registration number will supply each contracted module?

Accept when

The proposal, contract schedule, invoice route and technical-responsibility map use the same exact entity and registration number.

Hold when

The route relies only on a group, product or trading name.

Keep the operator route separate

Which operator entity, site registration and operating agreement will receive the supplier's services?

Accept when

Supplier and operator entities, registrations and responsibilities are recorded as separate legal routes.

Hold when

A supplier registration or related operator entity is treated as the buyer's authority to operate.

Freeze product and version scope

Which modules, games, integrations and release versions are accepted for the launch?

Accept when

Every controlled component maps to technical assessment, certification and acceptance evidence for the proposed release.

Hold when

The manufacturer-class registration is used as blanket product or title approval.

Prove the deployment chain

Who contracts, hosts, integrates, controls data and accepts each component in production?

Accept when

The entity chain, data flow, subcontractors, wallet authority and production acceptance agree in one deployment record.

Hold when

Registration is treated as proof of a contract, integration, launch or operating result.

Control the recorded term

What happens before the recorded end date or when entity, status or scope changes?

Accept when

Re-check, notice, suspension, regression, rollback and exit owners are enforceable before production access.

Hold when

Renewal or continuation is assumed from the current active status.

Continue the diligence chain

Carry the exact entity into scope, acceptance and contract

Global credential register

Compare exact permissions and recorded terms across jurisdictions.

Continue

Approval-type ontology

Separate supplier, operator, hosted, product and technical roles.

Continue

RFP response matrix

Make the supplier answer entity, product, data and exit questions consistently.

Continue

Implementation plan

Convert the accepted route into owned deliverables and go/no-go gates.

Continue

Ontario B2B supplier-register questions

How many current Ontario B2B supplier registrations are in this comparison?

Four exact manufacturer-class supplier registrations are current in the covered provider set. The count describes this comparison's verified current records, not every supplier in Ontario.

Does a supplier registration let a buyer operate an Ontario gaming site?

No. The operator entity, site-specific operator registration, operating agreement and operating responsibilities form a separate route.

Why are the Canadix registrations not included in the supplier count?

They are three current site-specific Operator — Internet Gaming registrations held by one operator entity. They are shown separately and are not platform-supplier permissions.

Does a manufacturer-class registration approve every product?

No. Each module, game, betting product, version and material change still needs the applicable technical assessment, certification and release acceptance.

Does omission mean a provider lacks Ontario permission?

No. Only verified, current, exact-entity records are published here. Missing, non-current or insufficiently scoped evidence remains outside the register without becoming a negative conclusion.