← Back to Blog

Per-Game RTP Documentation: Why Operators Should Demand It (and What to Ask For)

By Games4Titans Team · September 1, 2026

The request rarely arrives from a regulator. It comes from a payment partner three weeks into onboarding, or an aggregator's due-diligence questionnaire, or your own finance person trying to reconcile a monthly report — and it is always shaped the same way: list every game you run, with its documented RTP. At that moment an operator either forwards a document that already exists or opens an email chain with a supplier who treats game math as a trade secret. Per-game RTP documentation is the difference between those two weeks, and it costs the supplier almost nothing to provide — which makes its absence worth reading as a signal.

This guide covers who actually asks for per-title RTP records and why the requests are increasing, what a complete game documentation sheet contains, how to verify the numbers rather than just file them, and the red flags that predict a difficult supplier relationship before you sign anything.

Who asks for per-game RTP documentation — and why the list is growing

Operators sometimes assume RTP paperwork is a licensed-market problem. The opposite is closer to the truth. Sweepstakes and crypto operators, who mostly run without a formal gaming regulator, face more document requests from commercial partners, not fewer — because when no regulator has inspected the games, every counterparty runs its own inspection instead.

• Payment partners. Banks and processors serving gaming-adjacent businesses have compliance teams of their own. A schedule of games with documented return percentages and a certification reference is a standard artifact in their onboarding files. "We can get that from our supplier" is an answer that stalls an application; attaching the sheet is an answer that closes it.
• Platforms and aggregators. Any distribution partner that lists your content asks where the math comes from. Documented per-title RTP with a certification lineage is the first line of that answer.
• Your own finance function. Reconciliation — comparing what the games should return in theory against what your reporting says they did return — is impossible without the theoretical number for each title. This is the quiet, internal reason the documentation matters even if no partner ever asks.
• Player disputes. When a player claims a game is "rigged", the productive response is a documented RTP, a certified RNG reference, and — ideally — a public page they can check themselves. Suspicion thrives exactly where documentation is missing.

The procurement conclusion follows directly: per-game RTP records belong on the checklist you run before signing a content deal, at the same level as API quality and commercial terms. Collecting them retroactively, title by title, from a supplier with no habit of publishing is slow at best.

What a complete game documentation sheet contains

One number per game is the minimum, not the standard. A documentation sheet an operator can actually work with carries five things per title:

1. Theoretical RTP — with its versions

The headline number: the percentage of total stakes the game returns to players over the long run, as designed by the math model. Where a game ships with multiple selectable paytable versions, the sheet should say so and list them — a single number for a game that can be deployed at more than one return level is incomplete documentation. We covered how selectable versions work, and why operators routinely misuse them, in our configurable RTP guide.

2. Hit frequency

How often the game pays anything at all — a percentage of spins or rounds that end in a win. Two games at an identical RTP can feel completely different to players when one hits every third spin and the other every ninth, and hit frequency is also what determines how quickly your observed numbers converge toward theory (more on that below). Suppliers publish this less often than RTP; ask anyway.

3. Maximum win

The cap, expressed as a multiple of total bet. It bounds your exposure per round and belongs in the same table as RTP, because a high-cap title behaves very differently in reconciliation than a low-cap one at the same return percentage.

4. The RNG certification reference — worded honestly

Outcomes must come from a random number generator tested against GLI-19, the industry standard for RNG evaluation, by an independent laboratory — in our case BMM Testlabs. Read the wording of any certificate you are handed with care. The certification covers the RNG — the randomness source — not each individual game title. A supplier that writes "our RNG is certified under GLI-19" understands its own paperwork. One that advertises its game titles themselves as carrying the certification, without qualification, either does not, or is hoping you will not — and that distinction is one of the cheapest due-diligence tells available. We wrote up what the standard does and does not cover in our GLI-19 certification explainer.

5. Math documentation on request

Behind the summary sheet sits the full mathematical model: reel compositions, paytables, and probability accounting reports (PAR sheets). You will rarely read them line by line, but a partner performing deep diligence might, and a supplier who cannot produce them on request does not fully control the math it is selling. Every game we deliver includes its PAR sheets.

For operators running dual-currency deployments — Gold Coins and Sweep Coins as text-label currencies on the same titles — the documentation should confirm what the math does across modes: outcomes are computed as stake times multiplier, so the model behaves identically whichever label the wallet applies. If a supplier's answer to "does the RTP differ by currency mode" is vague, keep asking until it is not.

Theoretical versus observed: the reconciliation trap

The most common misuse of RTP documentation happens after signing, when an operator compares month-one actuals against the theoretical number and concludes something is broken. Usually nothing is. Theoretical RTP is a long-run property; over small volumes the observed figure swings wide of it as a matter of arithmetic, and the width of those swings depends on the game's hit frequency and win distribution. A high-frequency, low-cap game settles toward its documented number quickly. A long-tail title that concentrates return in rare large wins can sit three or four points under theory for weeks, then leap past it in one session.

Concrete numbers make the spread visible. Across our live catalogue, every one of our 254 games publishes a documented RTP — the band runs from 88.34% on the tightest arcade title to 99.64% on blackjack. Of those, 144 titles also publish a documented hit frequency, ranging from 10.68% to 54.70% with an average of 27.86%. A game hitting one round in ten needs far more volume to converge than a game hitting one round in two — which is exactly why the hit-frequency column belongs in the sheet next to the RTP column. Documentation that includes both lets your finance team set sane expectations for how fast each title's actuals should approach theory, instead of escalating every early-month deviation. The design logic underneath — how return, frequency and win distribution trade off against each other — is covered in our game mathematics guide.

A practical reconciliation rule: define, per title, a volume threshold below which you do not evaluate RTP deviation at all, and investigate only games that stay outside a tolerance band after crossing it. The documented hit frequency is the input that lets you set those thresholds per game instead of guessing one global number.

Verify the numbers — do not just collect them

A sheet you filed unread is compliance theatre. Verification is quicker than it sounds, because the useful checks are mostly comparisons:

• Check the public record. A supplier confident in its math publishes it. Our RTP list carries the documented return of every title in the catalogue, publicly, without a login — compare any sheet we send you against that page and the numbers must match.
• Read the per-game fairness report. Each of our titles has a fairness report — a one-page record of its RTP, math profile and certification lineage, with a linked simulation chart that runs the game's real math over a large sample so you can watch the observed return converge on the documented figure. That is the same verification your finance team will later perform with production data, run in advance.
• Compare against the game client. Open the game's own paytable and help screens and check that what the player sees matches what the documentation claims. A mismatch between the sheet and the client is a defect somewhere, and better found before launch than after a player finds it.
• Confirm the certification reference resolves. A certificate has an issuer and a scope. Check the lab is real and independent, and the scope covers the RNG behind the titles you are actually licensing.

Red flags in supplier RTP paperwork

Some patterns predict friction reliably enough to treat as disqualifying, or at least as grounds for harder questions:

• "RTP available on request" with nothing public. If the numbers only exist inside a sales conversation, every future request — from a payment partner, an auditor, a platform — routes through that same conversation.
• A single catalogue-wide "average RTP". An average across dozens of titles is marketing, not documentation. Reconciliation happens per game; the paperwork must too.
• Certificates that name games instead of the RNG. As above — either a misunderstanding of the supplier's own certification or a bet on yours.
• Documentation that contradicts the client. A sheet claiming one return while the in-game paytable implies another means the documentation process is decorative.
• No answer on selectable versions. If a game can be deployed at multiple return levels, the sheet should say which version your contract covers. Silence here becomes a dispute later.
• Undated, unversioned sheets. Math models get revised. Documentation with no date and no version identifier cannot be matched to the build you are actually running, which defeats its purpose the first time a partner asks "as of when".

What we publish, so you can check us first

We built our documentation stack so that the diligence described in this article can be run against us before anyone signs anything: a public per-title RTP list across the full catalogue, a per-game fairness report with a live simulation chart, PAR sheets delivered with every game, and outcomes drawn from a GLI-19 certified RNG independently tested by BMM Testlabs. If a number on any of those pages disagrees with a document we hand you, that is our defect to explain — which is precisely the position your supplier should be comfortable occupying.

Frequently asked questions

What is per-game RTP documentation?

A per-title record of each game's documented return-to-player percentage, ideally alongside its hit frequency, maximum win, selectable paytable versions and RNG certification reference. It is the artifact payment partners, platforms and finance teams ask operators to produce.

Why does a payment processor care about game RTP?

Processors serving gaming-adjacent businesses run their own compliance reviews, and a documented game schedule with a certification lineage is standard evidence in them. Operators without a formal regulator get more of these requests, because the partner's diligence substitutes for a regulator's.

My observed RTP does not match the documented number. Is something wrong?

Over small volumes, almost certainly not — observed return converges on the theoretical figure only as volume grows, and slower for low-hit-frequency games. Set per-title volume thresholds before evaluating deviations, and investigate only persistent outliers beyond them.

Is a higher RTP always better for my casino?

No. RTP is the player's share; its complement is your gross margin. The right level is a business decision balancing player experience against economics — what matters for procurement is that the number is documented, certified at the RNG level, and consistent between paperwork, public pages and the game client.

What should I ask a game provider before signing?

Request the per-title documentation sheet, confirm which paytable version of each game your contract covers, check the RNG certification wording and issuer, and compare the sheet against whatever the provider publishes publicly. If those four steps produce friction, expect the relationship to produce more of it.

Run the check against us

The fastest way to evaluate this article is to use it: open the RTP list, pick any three games, and trace each one from public number to fairness report to in-game paytable. That is per-game RTP documentation working the way procurement needs it to — public, consistent, and checkable without anyone's permission. Then tell us what you are building — the same documentation follows every title into your deployment.