Brazil does not approve a game because a studio is reputable. It approves a described, disclosed, certified build, and the certificate names the game rather than the company that made it. Under the Secretariat of Prizes and Bets regime, an online game offered to Brazilian players has to be certified by an entity whose operational capacity the Ministry of Finance has recognised, and that certificate has to be issued specifically for Brazil. The operator then has to keep it valid for the whole life of its authorisation, and revalidate it whenever a critical component of the game is added, changed or removed.
That structure changes what a commissioning brief has to contain. The technical annexe to Portaria SPA/MF nº 1.207/2024 is not a list of marketing claims; it is a list of things the artefact must do and show, written at the level of the player interface, the game cycle, the random number generator and the paytable. This article works through the parts that most often arrive late in a project — after art is signed off and the frontend is built — and what a publisher should therefore settle before production starts.

The certificate belongs to the build
Three clauses decide the shape of the deliverable. Portaria SPA/MF nº 1.207/2024 requires in article 5 that online games be certified by a recognised certification entity, and that the certificates attest full conformity with the technical requirements in that ordinance and its Annex I. Article 6 then removes any ambiguity about geography: certificates “must be issued specifically for Brazil by certification entities qualified by the Secretariat”.
Article 7 answers the question studios actually ask. An operator may present a valid game certificate issued in the name of the game supplier or developer with whom it holds a service contract. A studio that commissions, builds and delivers a title can hold the Brazilian certificate itself; the operator then relies on it. The same article adds the exception that catches distributed titles: where the operator offers the games through technology other than its own betting system, it must also present a certificate of integration between the platforms. A game delivered through a third-party RTP or aggregation layer is therefore two certification objects, not one.
Read together, those clauses produce a simple rule for a commission: the certificate is versioned to the build, addressed to the Brazilian market, and issued to whoever is accountable for the game. A studio that has certified the same mathematics for another jurisdiction has certified nothing here.
The disclosures that have to exist before the first bet
Brazil front-loads disclosure. Article 4 of the ordinance requires that at the moment of the bet the game present a multiplication factor for each unit of national currency staked, defining what the player receives on a win, and that the paytables covering all possible winnings be made available to the player before betting.
Annex I then sets out what “available” means in practice:
- RTP before the session starts. Item 29 requires the game’s art to carry the return-to-player figure for each game offered, without the player having to open a session, and item 29(a) requires the art to explain how that figure was determined and how the player can reach it — including any betting requirements.
- Variable contributions shown separately. Where progressive or incremental jackpots, time-limited prizes or incentive prizes contribute variably to RTP, item 29(b) requires that contribution to be clearly disclosed.
- Realised RTP has to name its sample. If the figure displayed is a realised RTP rather than a theoretical one, item 29(d) requires the number of games used in the calculation and the period considered.
- The top prize needs a probability statement. Item 30 requires that the highest advertised prize, where it depends purely on randomness, occur at least once in one hundred million plays — unless the art clearly states the real odds of that prize.
The last point is the one that most often forces a design conversation. A headline “maximum win” that a studio cannot support at that frequency, and does not want to publish odds for, is a specification defect rather than a marketing preference.
The paytable itself is the strictest artefact in the annexe. Item 11(e) requires it to include all possible results and winning combinations with their corresponding payout values for every betting option available in the game. Item 11(k) requires the art to describe how coincident wins are treated: whether a payline pays only its highest combination or all combinations, whether a symbol qualifying for both a line and a scatter pays both or only the larger, and how simultaneous scatter combinations are handled. If the maths has a rule, the art has to state it.
The session is the unit the rules measure
Two definitions do most of the work in a build. A game session runs from the start of the game to its end, and the ordinance treats thirty minutes of player inactivity as ending it. A game cycle runs from one bet to the next: it starts when the player stakes, and item 6(c) makes free spins, second-screen features and player choices part of that single cycle rather than separate events.
From those definitions the annexe derives obligations that are easy to miss in a frontend specification:
- no new bet may start in the same session before the current cycle is complete and the available funds and game history have been updated, unless the action that starts a new game also ends the current one (item 6(e));
- staked or committed amounts are deducted from the credit counter or account balance, and no bet may be accepted that could take the balance negative (item 6(b));
- a credit counter, where one is used, must be displayed in Reais and visible whenever a bet can be placed or a transfer made, and restricted incentive credits must be staked before unrestricted funds (item 10);
- during a session the interface shows available funds, the selected game’s title, the current bet and any committed amounts, plus the precise result of the last completed bet and the amount won (item 7);
- leaving a session transfers any counter balance back to the account (item 10).
For a studio, that is a state model, not a set of screens. A build that lets a player queue a spin during a free-spin sequence, or that keeps winnings in a temporary counter after the session ends, is non-conforming in a way that no amount of testing at the end of production reliably fixes.
Interface obligations that change the art and layout
The annexe also constrains the interface itself, and those constraints land on design files rather than on code. Item 2 requires that any resize or overlay of the player interface map accurately to the reflected display change and click points; that every interactive area affecting the game be clearly identified by function; that there be no hidden or undocumented touch areas or buttons affecting the game, its integrity or its result; and that information display be adapted to the interface. On a small screen a summarised version of the game information may be shown — with the paytable excepted — provided the full version is reachable from a secondary, help or otherwise easily identified screen.
Item 3 adds that simultaneous or sequential activation of several interface devices must not malfunction the game or produce results contrary to its designed architecture. In practice that is a multi-touch and rapid-input test case, and it belongs in the acceptance criteria rather than in a post-launch bug list.
Two further items decide what the help screens must contain. Item 11(b) requires the help information to be reachable without any deposit or bet, and to describe any game feature: free spins, a double-or-gamble option, timers, symbol transformations, progressive and incremental jackpots. Item 11(f) requires the art to indicate clearly that prizes are shown in Reais, and item 11(g) requires that where the art announces a prize in credits, that prize must be winnable in a single game or in a series enabled by an initial game, with the criteria stated. Item 11(h) closes the door on the obvious workaround: the game must not change advertised prizes after the bet is made.
The maths constraints a brief has to accept
The payout requirements are stated as properties rather than as a single number, which is why they belong in the maths brief:
- Minimum RTP of 85%, theoretically, over the game’s expected life, and item 28(a) requires it to be met by all betting configurations — not by the default stake alone.
- Jackpot RTP at the floor. Where progressive or incremental jackpots are included in the calculation, item 28(b) requires the minimum to be met using the lowest available jackpot parameters during the game’s life, such as the reset or minimum value.
- Excluded prizes. Jackpots and incentive prizes external to the game are not counted in the payout percentage unless they are necessary for its operation.
- RNG independence. Item 23 requires that chance events be influenced only by an approved RNG, that the game not limit or discard selected results, that it not substitute a losing result, and that events be independent — a game must not adjust the probability of a feature from prior prize history, and must not adjust its theoretical RTP from prior payouts.
- Constant probability. Item 27 requires the mathematical probability of any random event to be constant unless stated in advance in the game art.
- No simulated-physics drift. Where the game simulates a physical object used to determine the result, item 25 requires the simulated behaviour to match the real object’s properties unless the art says otherwise, and independent objects to behave independently.
- No hidden source code, and a result display long enough for the player to check the outcome (item 24).
- No community incentive prizes. Item 36 prohibits incentive prizes in which players contribute to or compete for a shared prize — a constraint worth naming early, because community and shared-pot features are a common pitch.
What triggers revalidation, and the record it depends on
The change-control clause is the one that sets the calendar. Article 5(4) requires game certificates to be revalidated whenever a critical component is added, changed or removed, and article 5(5) requires the revalidated certificate to be sent to the Secretariat through the betting management system within five business days of issue. “Critical component” is defined in both ordinances as any component whose failure or compromise could cause loss of player rights, loss of federal revenue, obstruction of the regulator’s access to operational information, unauthorised access to betting system data, or non-compliance with the rules governing the market.
That definition is broad enough to make a studio’s own dependency list a commercial document. A new third-party bonus engine, a changed RNG, a new payment-adjacent integration or a re-platformed frontend are all candidates for the same question: is this a critical component, and does the certificate have to be revalidated before the change goes live rather than after?
Two further obligations shape the evidence pack. Article 10 of the ordinance requires data, information and documents relating to online games to be at the regulator’s disposal for at least five years from creation — which is a retention requirement on build records, maths reports and paytable versions, not only on transaction logs. And under Portaria SPA/MF nº 722/2024 the operator’s own certification regime requires an evaluation report within ninety days of authorisation, annual revalidation of certificates, and revalidation whenever critical components of the wider betting system change. A game is certified inside that system, so a studio’s release date and an operator’s certification calendar have to be planned together.
What to put in the commission
The practical output of all this is a deliverable list that can be agreed before production, and checked at handover:
- a game certificate issued for Brazil in the name of the party that will hold it, with the build version it describes;
- an integration certificate where the game reaches players through a platform other than the operator’s own betting system;
- a versioned paytable pack covering every bet configuration and every coincident-win rule the maths implements;
- an RTP statement that names the method — theoretical or realised — and, for realised figures, the sample and period;
- a session and cycle specification: what ends a session, what belongs to a single cycle, what the interface must show during play;
- a critical-component register with the studio’s classification of each change, so revalidation is a decision rather than a discovery;
- help and rules content in Brazilian Portuguese, reachable without a deposit, describing every feature the build contains;
- the retention set: maths reports, paytable versions and build records kept for the five-year window.
None of that is exotic engineering. It is the difference between a game that can be certified once and a game that can be revalidated on the operator’s timetable — and the second is what a Brazilian launch actually needs. A studio that builds the paytable, RTP statement and cycle model as release artefacts, rather than reconstructing them at submission, spends its certification window on testing instead of on archaeology. Publishers scoping that work can request a project quote with the market and the bet configurations named in the brief; the certification submission and localised certification evidence guides cover the wider pack these documents sit in.
This article describes the published text of the ordinances cited and draws no legal conclusion. The operator remains responsible for its authorisation, and the certification entity decides conformity against the build it tests.
Questions suppliers ask
Is a Brazilian game certificate issued per studio or per game?
Per game. Portaria SPA/MF nº 1.207/2024 requires online games to be certified by a recognised entity, requires the certificates to be issued specifically for Brazil, and allows an operator to present a valid certificate issued in the name of the game supplier or developer with whom it holds a service contract. The certificate therefore attaches to the game and the build it describes, not to the studio’s catalogue as a whole.
What RTP does a game have to reach to be offered in Brazil?
Annex I, item 28 requires each game to pay, theoretically, a minimum return to player of 85% over its expected life, and item 28(a) requires that minimum to be met by all betting configurations. Where progressive or incremental jackpots are counted in the RTP, the minimum has to be satisfied using the lowest jackpot parameters available during the game’s life, such as the reset value.
Does the paytable have to show every winning combination?
Yes. Item 11(e) requires the paytable information to include all results and winning combinations together with their corresponding payout values for every betting option available in the game, presented at the start of the session and available for consultation at any time during it. Item 11(k) adds that the art must state how coincident wins are handled — for example whether a payline pays only its highest combination or all of them.
When does a game session end in Brazil?
The ordinance defines a game session as the period from the start of the game covered by a bet to its close, and treats thirty minutes of player inactivity in that game as ending it. Leaving the game also ends the session, and any credit counter balance is transferred back to the player’s account.
What counts as a change that forces the certificate to be revalidated?
Any inclusion, alteration or exclusion of a critical component. Both ordinances define a critical component as one whose failure or compromise could cause loss of player rights, loss of federal revenue, obstruction of the regulator’s access to operational information, unauthorised access to betting system data, or non-compliance with the market rules. The revalidated certificate must reach the Secretariat through the betting management system within five business days of issue.
Can an operator rely on a certificate the studio already holds?
It can, if the certificate is valid and was issued in the name of the game supplier or developer under a service contract, and if it was issued specifically for Brazil. Where the games are offered through technology other than the operator’s own betting system, the operator must also present a certificate of integration between the platforms.









































