operator
Wizards supplier profile
A disclosed supplier profile for Wizards covering its public game, platform, app, certification-readiness, marketing, and advisory service pages.
Read the evidenceSupplier category
Platforms
Core platform, back-office, account, and operational systems.
What decision does this category support?
Which product, account, wallet, content, data, operational, and regulatory responsibilities belong to the operator, the platform, and each connected supplier?
What evidence should a buyer request?
- A module map, data flow, integration inventory, and responsibility matrix for the proposed configuration.
- Release, security, incident, service-level, reporting, change-notice, and acceptance records.
- Commercial dependencies, data portability, transition assistance, termination rights, and an executable exit plan.
Which supplier records are published?
What should stay separate?
A white-label description, product list, or single-API claim does not prove one legal entity, one licence boundary, one operating responsibility, or one accepted implementation.
Continue the evaluation
- Compare build, buy, and integration models
- Use the platform RFP template
- Map RGS, aggregator, platform, and operator roles
Use the same evidence questions for every candidate and keep unknowns visible. Direct supplier and project intake is not currently offered.