Skip to content
iGaming Platform Provider
Malta B2B permission register

Malta B2B suppliers: exact entity, permission and critical-supply scope

Twelve active B2B permissions connect thirteen provider profiles to twelve exact supplier entities. Each permission stays attached to its legal entity, service classes, status and recorded term; operator, product and deployment conclusions remain separate.

Individual status checks run through August 13, 2026. Page materially updated August 13, 2026.

Critical supply is not operating authority
A Malta B2B permission records what the named supplier entity may supply. It does not transfer to the buyer, convert a related B2C licence into a hosted route, approve every product or prove that a deployment is contracted and live.

Count the relationship and the permission separately

One shared permission does not become two licences

The Pariplay permission appears in both the Pariplay product profile and the Aristocrat Interactive group context. It remains one exact entity and one permission in the canonical count.

13

provider-to-permission relationships

13

provider profile contexts

12

exact B2B permissions

1

permission with a recorded end date

Canonical B2B permission register

Contract against the entity and permission number

Every row is an active, exact-entity B2B critical-supply permission. Status-check dates remain row-specific, and missing term dates stay undated.

Swipe horizontally to view all columns.
Active Malta B2B critical-supply permissions by exact entity, provider context, service class, status and recorded term.
Exact entity / provider contextPermission / statusService classesRecorded termStatus checked
Altenar Software Limited
MGA/B2B/582/2018
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Delasport Limited
MGA/B2B/875/2021
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Digitain (MT) Limited
MGA/B2B/592/2018
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Everymatrix Software Limited
MGA/B2B/201/2011
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
iGamingCloud Limited
MGA/B2B/330/2016
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live bettingType 3 peer-to-peer games

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Kambi Malta Limited
MGA/CRP/185/2010
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
LNW Gaming Malta Limited
MGA/B2B/112/2004
Recorded active
B2B critical supply
Type 1 casino

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Oryx Gaming Limited
MGA/B2B/298/2015
Recorded active
B2B critical supply
Type 1 casino

The service class is not approval for every platform module, game title, product version or later change.

Current recorded term: 2025-10-04 through 2035-10-04.August 13, 2026
Pariplay Malta Limited
MGA/B2B/469/2018
Recorded active
B2B critical supply
Type 1 casinoLottery gaming services

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Playtech P.L.C.
MGA/CRP/137/2007
Recorded active
B2B critical supply
Detailed service type not separately recorded

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Soft Construct (Malta) Limited
MGA/B2B/286/2014
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live bettingType 3 peer-to-peer gamesType 4 controlled skill games

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026
Stable Aggregator Ltd
MGA/B2B/942/2022
Recorded active
B2B critical supply
Type 1 casinoType 2 fixed-odds / live betting

The service class is not approval for every platform module, game title, product version or later change.

Recorded active; no entity-specific start or end date is stated.August 13, 2026

Critical-supply service map

Permission scope is a service-class map, not a product catalogue

One permission can cover several service classes, so these counts overlap. They count exact permissions carrying each class, not products, games or production deployments.

11 permissions
Type 1 casino

The permission includes Type 1 casino critical supply. Individual games, versions and release acceptance remain separate.

8 permissions
Type 2 fixed-odds / live betting

The permission includes Type 2 fixed-odds betting, including live betting where stated. It does not settle the operator or trading route.

2 permissions
Type 3 peer-to-peer games

The permission includes Type 3 peer-to-peer bingo or game services. The exact contracted service still needs its own scope map.

1 permissions
Type 4 controlled skill games

The permission includes Type 4 controlled skill games. It does not extend that class to unrelated products.

1 permissions
Lottery gaming services

Lottery gaming services are part of the recorded critical-supply scope for one exact entity permission.

1 permissions
Detailed service type not separately recorded

The corporate B2B permission is active, but this record does not assign a narrower Type number. No service class is inferred.

Permission-role boundary

B2C records stay outside the supplier-permission count

Two provider profiles also connect to active Malta B2C operator permissions. Their entities and roles differ from the B2B supplier register and cannot be substituted for it.

Swipe horizontally to view all columns.
Malta B2C operator permissions recorded separately from B2B supplier permissions.
Provider context / operator entityOperator permissionOperating scopeSupplier boundary
Soft2Bet
Maltix Limited
MGA/B2C/486/2018
Recorded active
Type 1 casino; Type 2 fixed-odds / live betting for the websites attached to the permission.This is an operator permission held by the named B2C entity. It is not a B2B platform-supplier permission and does not create a hosted route for another buyer.
BetConstruct
SCGO Limited
MGA/B2C/292/2015
Recorded active
Type 1 casino; Type 2 fixed-odds / live betting for the websites attached to the permission.This is an operator permission held by the named B2C entity. It is not a B2B platform-supplier permission and does not create a hosted route for another buyer.
B2B supplier entity
Counted only when exact entity, permission number, active status and critical-supply scope are all retained.
B2C operator entity
A separate permission and attached operating scope. A group relationship does not transfer it to a platform buyer.
Hosted and deployment route
Counted only after the licensed entity, contract, website, product scope and production acceptance form one exact route.

Malta permission acceptance path

Six gates from permission record to production release

The sequence prevents a valid supplier permission from being stretched into conclusions about the buyer's operator route, product acceptance or live deployment.

1
Lock the exact B2B entity
Which named entity and permission number cover each supplied service?
Accept

The proposal, contract schedule and technical responsibility map all use the same exact entity and permission number.

Hold

The route relies on a group name, product brand, affiliate pool or a different contracting entity.

2
Map every service class
Which contracted modules sit inside Type 1, Type 2, Type 3, Type 4 or lottery supply scope?
Accept

Every module maps to the recorded service class for the same entity, with out-of-scope components identified separately.

Hold

A general platform label or one service class is used to cover unrelated modules by assumption.

3
Keep the B2C route separate
Which exact operator entity, permission and attached website will receive the supplied services?
Accept

The B2B supplier route and B2C operator route are documented as separate permissions and responsibilities.

Hold

A supplier permission or a related group operator permission is presented as the buyer's operating authority.

4
Freeze product and version scope
Which modules, games, versions and controlled changes are accepted for the proposed launch?
Accept

The permission class, technical evidence, product inventory and release baseline agree at item and version level.

Hold

The B2B permission number substitutes for product, title or version acceptance.

5
Prove the production route
Which entity contracts, hosts, integrates and operates each component in the actual deployment?
Accept

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

Hold

A permission is treated as evidence that the product is contracted, integrated or live.

6
Contract the continuing controls
What blocks release when entity, status, term, service scope or product version changes?
Accept

Notification, re-check, regression, suspension, rollback and exit owners are enforceable before production access.

Hold

Initial diligence is treated as permanent permission for later entities, products or releases.

Field contract

Five fields that must not collapse into “Malta licensed”

Exact legal entity

The company that carries the permission. A provider brand, parent group or product name is a separate identity layer.

B2B critical supply

Permission for the named supplier entity and recorded service classes. It is separate from the B2C operator route.

Service class

The Type 1, Type 2, Type 3, Type 4 or lottery boundary recorded for the permission. It is not a product catalogue or title approval.

Recorded term

Entity-specific start and end dates retained only when present. Active status is not converted into an inferred expiry date.

Deployment

A separate operator, contract, product, integration and production-acceptance event. A permission alone does not establish it.

Malta B2B permission FAQ

Questions that change a buyer decision

Does a Malta B2B permission let the supplier operate the buyer's casino?

It records critical-supply permission for the named B2B entity and service classes. The operator entity, B2C permission, attached website and operating responsibilities remain a separate route.

Why are there thirteen provider relationships but twelve B2B permissions?

Pariplay Malta Limited and permission MGA/B2B/469/2018 support both the Pariplay profile and the Aristocrat Interactive group context. Those are two profile relationships to one underlying permission.

Does Type 1 critical supply approve every casino game?

The Type 1 class defines the recorded B2B service boundary. Game title, product version, technical acceptance, contract scope and production release remain separate controls.

Why does only one permission show a dated term?

Only the Oryx Gaming Limited row contains a current-term start and end date in this dataset. The other permissions remain recorded active without an inferred start date or expiry date.

Carry the exact permission into implementation

Use the global credential register for cross-market context, then carry the Malta entity, permission, service class and operator dependency into the implementation gates.