Protection should come before optimisation
Harm-First Orchestration is the decision order we are building: harm and safer gambling first, then fraud and abuse, then compliance, and only then commercial optimisation. It is in active development, not behaviour available today.
In active development
This capability is in active development. It is described here as design intent, not as behaviour available today.
The decision order
Decision hierarchy
The hierarchy is designed to give every decision a defined order, so growth can never silently override the controls protecting the player, the operator and the licence.
In active development
- 01
Harm and safer gambling
Player protection holds the highest priority and can stop a downstream commercial action before it starts.
- 02
Fraud and abuse
Potential fraud, bonus abuse and suspicious behaviour are assessed before any incentive or payout proceeds.
- 03
Compliance
Identity, jurisdiction and regulatory controls decide whether the action is permitted at all.
- 04
Commercial optimisation
Retention, bonuses and engagement are optimised only once every layer above has returned clear.
The goal is not another dashboard that reports risk
Most platforms optimise each system independently. We are building toward a different operating model, one where a commercial decision is only considered after player protection, fraud and compliance checks return clear.
Explainable, not opaque
A decision records the layer that made it and the policy it applied.
One context, not four opinions
Protection, risk, compliance and commercial logic read the same player record.
A refusal ends the sequence
When a higher layer does not return clear, nothing below it runs at all.
What exists today, and what is being built
The parts you can inspect are in the left column. The orchestration layer that coordinates them is in the right one, and it is not available on the platform today.
On the platform today
Inspectable in the back office
- Responsible gambling states in the account coreFreeze, suspend, ban and self exclusion held on the account itself rather than in a marketing tool.
- Included
- Tiered compliance model, T0 to T4A five tier trust model per player, with thresholds configurable per brand.
- Included
- Compliance gated transactionsThe wallet reads a player's compliance standing before any money moves.
- Included
- Bonus terms enforced by the engineBet caps, payout ceilings, per game weighting and expiry applied without a person in the loop.
- Included
- A full audit trail behind every actionPlayer, staff and system events in one searchable stream with actor, location and device.
- Included
- One decision order shared by all four layersA single sequence the whole platform follows, rather than four systems acting independently.
- Not included
- Harm signals that can halt a commercial actionA player protection signal that stops a bonus, an offer or a payout before it is issued.
- Not included
- One explainable record of why an action was allowedA single readable answer to why the platform did what it did, assembled as the decision is made.
- Not included
In active development
Design intent, not behaviour
- Responsible gambling states in the account coreFreeze, suspend, ban and self exclusion held on the account itself rather than in a marketing tool.
- Not included
- Tiered compliance model, T0 to T4A five tier trust model per player, with thresholds configurable per brand.
- Not included
- Compliance gated transactionsThe wallet reads a player's compliance standing before any money moves.
- Not included
- Bonus terms enforced by the engineBet caps, payout ceilings, per game weighting and expiry applied without a person in the loop.
- Not included
- A full audit trail behind every actionPlayer, staff and system events in one searchable stream with actor, location and device.
- Not included
- One decision order shared by all four layersA single sequence the whole platform follows, rather than four systems acting independently.
- Included
- Harm signals that can halt a commercial actionA player protection signal that stops a bonus, an offer or a payout before it is issued.
- Included
- One explainable record of why an action was allowedA single readable answer to why the platform did what it did, assembled as the decision is made.
- Included
Rows in the right column describe design intent. They are not available on the platform today. Checked August 2026.
The controls that ship as standard
None of this waits for the orchestration layer. These are in the product now, and they are what the decision order is being built to coordinate.
Player protection
Deposit and session limits
Set against the account and enforced by the platform, not by a reminder.
Self exclusion
A player state held on the account, not a suppression flag in a campaign tool.
Account freeze and suspension
Available to scoped staff and written into the audit trail as it happens.
Player safety states in the account core
Protection sits inside the account model rather than in a layer bolted beside it.
Fraud, compliance and evidence
Tiered compliance engine, T0 to T4
Deposit and withdrawal eligibility decided automatically, not through a support ticket.
Compliance gated transactions
Compliance standing is read before the wallet moves anything.
Bonus abuse controls
Bet caps, payout ceilings, per game weighting and expiry enforced by the engine.
Full platform audit trail
One tamper evident stream covering players, staff and systems.
Regulator evidence packs
Reports built on the audit trail rather than assembled by hand.
Why the order matters
Optimisation runs first by default
In most stacks the retention tool, the bonus engine and the risk vendor all act on the same player without seeing what the others saw. Whichever runs first effectively decides.
Protection becomes an exception path
When safer gambling checks sit at the edge of the operation, they are something a person remembers to run rather than something the platform does before anything else happens.
Evidence is reconstructed afterwards
If four systems each hold a fragment of one decision, answering a regulator means rebuilding the story from four exports and hoping the timestamps agree with each other.
That is the operation most teams run today.
The advantage is not another feature. It is fewer disconnected systems making decisions about the same player.
Questions about the decision order
Account freeze, suspension, ban and self-exclusion, built into the account core rather than added as a marketing setting. Because they are states on the account itself, every other part of the platform has to respect them: a self-excluded player cannot be reactivated by a campaign, and a frozen account cannot quietly take a deposit.
Deposit and session limits sit alongside them, as do the tiered checks that run before money moves. The controls are ordinary. Where they live is the part that decides whether they hold.
You are, and we build the platform so that you can be. We supply the checks, the tiers, the gates and the record. You decide which markets to accept, where thresholds sit, what evidence each tier requires and what happens to an escalated case.
On the White Label route we also carry our own obligations as the licensee, which is why a new casino needs both platform approval and your explicit launch. Neither of us can sign that off alone.
Every player sits at a tier from T0 to T4, and the tier decides what they are allowed to do: how much they can deposit, whether they can withdraw, and which checks must clear before either changes.
Thresholds are configured per brand, so a market with strict affordability expectations does not inherit the settings of one without. The decision happens in the account core in real time rather than through a support ticket, and the wallet consults the tier before it moves any money.
Tell us what your compliance team actually needs
We would rather hear the requirement than describe a roadmap at you. Bring the questions your regulator asks and we will show what the platform can evidence today.
We reply within one working day.
