Your own affiliate programme, built in

A separate partner portal where affiliates register, create campaigns and referral links, follow their statistics and request payouts, and a partners section in the back office where the operator approves them, sets commission and settles payouts.

It comes with every launch rather than as a third-party tool bolted on, which means commission is calculated from the same ledger the casino's own reporting uses. There is no second system to reconcile against, and no argument about whose number is right at the end of the month.

A partner moves from pending to approved, and can be suspended or sent back to pending. The model and rates can be set at approval, and every partner can be given individual rates that override the defaults, with a reset back to them.

Revenue share, CPA and a hybrid of the two. Revenue share is a percentage of the NGR of the players a partner referred; CPA is a fixed amount for each first deposit; hybrid pays both.

Defaults for revenue share, CPA per first deposit and the admin fee apply to every partner without individual rates. The revenue share is on NGR — GGR after realised bonus cost and provider commission — so a partner is paid on what their players actually earned the casino, not on turnover inflated by promotions.

Every day at 00:15 UTC, for the previous day. The net commission is credited to the partner's balance in the portal, where they can see it and request a payout.

A daily settlement means a partner can check yesterday's result this morning instead of waiting for a monthly statement, which is one of the things affiliates compare programmes on. The operator can also run settlement by hand — for yesterday as the standard close, or for the current UTC day as an interim check.

The partner requests a payout from the portal in USDT, on TRC-20, ERC-20, Solana or TON. The operator sends the payment and marks the request paid, or declines it; both actions need a fresh two-factor code.

Payouts to partners are made by the operator outside the platform rather than sent automatically. The platform keeps the balance, the request and its status, and records who marked it paid — the transfer itself stays under the operator's control, which is where most operators want a payment to people outside the company to stay.

Clicks, registrations, first deposits, deposits, redeposits, deposit amount, average deposit and EPC — earnings per click — with a funnel and a list of campaigns, filterable by period and sortable by any metric.

The same figures appear on the operator's partner list, so the best-performing partners and the ones sending registrations that never deposit are visible side by side. Notifications can be sent to the players a specific partner brought in, which makes partner-specific promotions possible without exporting a list.

Each partner — and each of their campaigns — can have its own set of welcome bonuses. A player arriving through that link gets that set; without one, the casino's standard welcome bonuses apply. That lets a partner promise their audience an exclusive offer the platform will actually honour.

Through a lead API. The tracker pushes a lead, the player is created and sent to the casino already logged in, and the tracker polls for statuses — registration, first deposit, deposits. There are no postback URLs to configure.

The API key is shown once at creation and stored only as a hash, so a lost key is reissued, never recovered. Keys are bound to an IP allowlist, or signed with HMAC-SHA256 over the method, path, body, a timestamp and a single-use nonce. Rotating a key keeps the old one working for a while so the tracker can switch; revoking stops it at once. Each integration has per-minute and per-day limits.

Two rules protect the operator. A lead for an email that already has an account is reported as existing and never earns a conversion, so a partner cannot claim a player the casino already had. And a retry with the same click ID returns the same lead instead of creating a second account. The auto-login code handed back is valid for 120 seconds and works once.

Yes, in two ways. A sign-up form on the partner's landing page can create the account and move the player to the casino already logged in, or the landing page can show the partner's bonuses and send the player to register on the casino.

The sign-up form uses a public key bound to the landing page's domain and a Cloudflare Turnstile captcha, so the key can sit in the page's JavaScript without being a secret. A server-to-server mode signed with HMAC is available where the form posts through the partner's own backend.

The second route suits one landing page serving many partners: the partner is chosen by a slug in the page address, a single request returns the partner's name, image, tracking link and bonuses, and the bonuses shown are granted automatically when the player registers through that link. That is how the ready-made partner landing pages work — a page for every partner, set up on request at no extra charge.

Revenue share only pays on real NGR, CPA only on first deposits, and existing players are never re-attributed. On top of that, the fraud scoring flags referral rings and self-referral — players invited from the same network as the partner or referrer.

Managing partners, viewing their payouts, marking payouts paid, declining them and issuing tracker keys are separate permissions in the back office, and key actions are written to the audit log. The fraud rules are set out on anti-fraud; how player-to-player referrals differ from partners is on referrals and streamers.

No. This page is about running an affiliate programme for other people's traffic on your casino. If you are an affiliate team with traffic of your own and want to stop selling it to other brands, that is covered on the page for affiliate teams.