Take The Bank rules and ten-spin evidence

Take The Bank is listed by Betsoft as live from 29 October 2019. Its official product page publishes five reels, 75 paylines, 96.08% RTP, medium volatility and a 20.12% hit rate. The distinguishing structure is a ten-spin base sequence: a bomb counter moves from 10 to zero while robber symbols become bombs, then the recorded bombs convert to Wilds.

The same source documents a bonus triggered by three police-car symbols. It awards a moving set of 5, 7 or 10 Wilds. Betsoft also describes a purchase control, but the public page does not state its cost, stake range, maximum win, selection probabilities or local availability.

Verified specification

Field	Official value	What still needs live Help
Listed live date	29 October 2019	Exact deployed build
Reels	5	Visible row count
Paylines	75	Direction and line map
RTP	96.08%	Active operator profile
Volatility	Medium	Studio classification only
Hit rate	20.12%	Includes sub-stake returns
Base progression	10 paid spins	Persistence and reset rules
Bonus Wilds	5, 7 or 10	Selection probability

How the Heist Spins sequence works

The official description says the bomb counter counts down from 10 to zero. Robber symbols convert into bombs during those spins; after the tenth step, the bombs turn Wild. This is a progression mechanic, not ten free spins and not stored cash value.

Start an audit before the first paid spin. Save the counter, total stake and empty grid coordinates. After every settlement, mark each new robber, the bomb position it creates and the remaining counter. On the conversion spin, compare the final bomb set with the Wild positions and then use game history to reconstruct each winning line.

If the client closes halfway through, do not wager merely to test persistence. Reopen the title, record the restored counter and compare it with the last settled round. A visual reset, a server-side reset and a delayed animation are different outcomes. Support should receive the round IDs and timestamps if the display disagrees with history.

The 75-payline paytable

Seventy-five paylines means line geometry matters. A cluster that looks connected may not follow an active route, while a less obvious diagonal may qualify. Open Help and capture the complete map, pay direction, minimum matching length and whether any symbol pays when it starts away from the first reel.

Transcribe symbol values by matching length and by stake unit. Do not copy figures from another Betsoft title or from an affiliate review. The official public page does not expose the whole paytable, so exact symbol awards remain deployment-level facts.

Wild substitution must also be checked. The product page confirms bomb-to-Wild conversion and moving Wilds, but it does not enumerate every excluded symbol. Record whether the Wild replaces the robber, police car, bomb or any other special object, and whether a converted Wild can participate in more than one of the 75 lines.

Police cars and moving Wilds

Betsoft states that three police cars start the bonus game. The feature provides 5, 7 or 10 Wild symbols, and all Wilds move to new locations on every spin. The public copy does not publish the number of free spins, retrigger conditions or odds attached to each Wild quantity.

Record the opening selection screen and count the Wilds before the first feature spin. Use a fresh grid diagram for every result. The quantity should be separated from position: a Wild moving from reel two to reel four is not a new Wild. At settlement, count the objects again and compare their coordinates with the line-win breakdown.

Do not infer that ten Wilds is common simply because it is the largest advertised state. Without probability data, expected value cannot be reconstructed. Likewise, a feature screenshot showing a large award does not establish a maximum win.

Purchase control and version boundaries

The provider says the feature can be purchased and that the player can select the number of Wilds. That confirms the concept globally, not its availability in a New Zealand account. Operator configuration, jurisdictional rules and product version can remove or alter the control.

Before confirming a purchase, capture its displayed cost, chosen Wild quantity, total stake, RTP notice and cancellation path. Compare the wallet deduction with the confirmation amount. If Help presents a separate return profile, report it independently rather than blending it with 96.08%.

The control is a wager, not a deposit bonus and not free access. This review therefore does not quote an unverified price or recommend a purchase. The useful question is whether the interface discloses enough information to understand the transaction before confirmation.

RTP and hit-rate interpretation

RTP is a long-run mathematical percentage, not a session forecast. At 96.08%, the theoretical model still permits extended losses and uneven feature spacing. The 20.12% hit rate describes rounds classified as hits; some may return less than the stake.

Keep three columns in a session ledger: stake deducted, gross award and net change. A hit belongs in the second column even when the third remains negative. Separate ordinary line wins, tenth-spin Wild conversions and feature settlements so the mechanism behind each result remains visible.

Never use a short personal sample to declare the RTP false or confirm it. A small set is valuable for checking interface behaviour, not reverse-engineering certified mathematics.

Mobile and history checks

On a narrow screen, confirm the counter remains visible without covering the spin control or stake value. Open the paytable in portrait and landscape, then verify that line diagrams, feature descriptions and the RTP label are readable without clipped columns.

Test interruption safely by leaving before a wager, returning and checking the saved display. After a completed round, compare the animation with server history. History should expose the stake, result and identifier even when the presentation skips or reconnects.

Accessibility checks include focus visibility, readable contrast, motion controls where offered and a non-colour-only explanation of the counter. If a bomb state is communicated only by flashing colour, document that limitation.

Evidence checklist

• Match the exact title and Betsoft provider label.
• Confirm the 29 October 2019 live date only as catalogue history.
• Record 96.08% from current Help.
• Capture all 75 paylines and pay direction.
• Save the 20.12% hit-rate label without interpreting it as profit frequency.
• Photograph the counter before spins 10, 5, 1 and conversion.
• Map every robber, bomb and resulting Wild coordinate.
• Confirm whether progression survives a reconnect.
• Record the police-car trigger wording.
• Count 5, 7 or 10 moving Wilds on every feature spin.
• Leave free-spin quantity unavailable until Help states it.
• Capture purchase cost and any separate RTP before confirmation.
• Preserve round IDs for disputed settlements.
• Verify New Zealand availability only at operator-account level.

Practical verdict

A worked verification record

Suppose the counter shows three before a settled round. The audit entry should include the stake, starting balance, robber coordinates, resulting bomb coordinates and counter after settlement. Repeat for counters two and one. On the conversion result, list every bomb that became Wild and every payline credited through those positions. This record does not predict the next cycle; it demonstrates whether the displayed sequence followed the documented rule.

If a robber lands where a bomb already exists, do not silently count two objects. Capture the animation and consult Help for replacement or stacking language. If the counter reaches zero after a disconnect, compare the server timestamp with the local replay. The purpose is to isolate presentation latency from a genuine settlement problem.

For the feature round, create a second table with starting Wild quantity, location set for each spin and awarded paylines. This keeps the 5, 7 or 10 selection separate from movement. The two tables together provide a concise evidence pack that support can understand without relying on memory.

Take The Bank is straightforward to identify but easy to describe inaccurately. Its key evidence is temporal: ten paid rounds build a position set, then Wild conversion resolves it. A responsible review must preserve that sequence instead of reducing the game to a generic robbery theme.

The feature round adds a second audit problem because Wild quantity stays conceptually separate from Wild movement. The official page gives the possible counts but leaves several operational fields to live Help. Those gaps should remain visible rather than being filled with third-party numbers.

FAQ

What RTP does Betsoft publish?

96.08%, subject to confirming the active deployed profile.

Are the ten Heist Spins free?

No. The official description presents them as a base-game progression counter.

What happens at zero?

Accumulated bomb positions convert into Wilds.

What starts the bonus game?

Three police-car symbols.

How many moving Wilds appear?

The documented options are 5, 7 or 10.

Is the purchase control guaranteed in New Zealand?

No. Provider documentation does not prove local operator deployment.

Sources

• Betsoft, Take The Bank, official product page, checked 9 October 2026.
• Betsoft official games catalogue, checked 9 October 2026.

How to verify the version you can actually open

A provider page proves that a title exists and describes the supplier's intended rules. It does not prove that a casino accepts players in New Zealand, that the title is enabled for a particular account, or that the highest published RTP is the version in the lobby. Treat availability, operator eligibility and product configuration as three separate checks.

Start with identity, then configuration

Open the game only through the authenticated casino lobby. The information or help panel should identify Betsoft, the exact title and the active mathematical return. Compare the reel or grid layout, paylines or cluster rules, named features and symbol behaviour with the official product material. Similar artwork or a matching title is not enough when the help file is missing or inconsistent.

When the supplier publishes several RTP values, report all of them as configurations. Do not assume the highest option is deployed. RTP is a theoretical long-run measure across a very large number of rounds; it is not a refund rate for one player and cannot predict the next result. Volatility is different: it describes how unevenly results are distributed on the provider's scale.

Read stake controls as money, not interface decoration

Provider sheets often quote a reference range in euros. That range does not establish New Zealand-dollar support or the limits in a specific account. Before a paid round, identify the total amount that will leave the balance. If the interface separates denomination, coins and lines, verify the combined total. If Extra Bet is active, calculate its full cost before pressing spin.

Feature-buy prices are multiples of the current bet, not promised returns. A 100x purchase at a $1 stake costs $100; at a $2 stake it costs $200. Availability can vary by market and some mathematical configurations may not support the control. If the live help does not explain the price, delivered feature and active RTP, leave the option unused.

Keep simulation figures in their proper scope

A game sheet may publish a maximum result observed in a large simulation. That is not automatically the contractual maximum payout and never describes a likely session. Preserve the provider's wording, sample size and configuration. Check the live rules for a binding cap and the operator terms for any separate payout limit. Do not turn an extreme result into a promotional headline.

Audit a disputed round

If an animation freezes or a connection drops, do not repeat the wager immediately. Reopen the game through the authenticated lobby and inspect round history. Record the time, total stake, balance movement and round identifier. The result can be settled by the gaming system even when the device never displays the final animation. Send evidence through verified operator support; never disclose a password, recovery phrase or one-time code.

Read the paytable as a calculation document

The paytable should explain what creates a win, which symbols substitute, where special symbols can land and how multiple awards combine. For line games, confirm direction and active paylines. For cluster games, confirm adjacency, minimum group size and the order of collection. For respins, identify what remains locked, what resets the counter and what ends the feature. A graphic effect can illustrate those rules but cannot replace them.

Separate addition from multiplication. Several prize values may be added before a multiplier applies, while reel-specific multipliers can sometimes multiply together only when each reel participates in the same win. Reconstruct one low-stake result from game history. If the arithmetic cannot be matched to the help file, stop and ask the operator rather than guessing.

Do not confuse hit frequency with a profitable round

Provider sheets can publish hit frequency or category probabilities. A hit simply means a round returned a qualifying amount; it can be smaller than the stake. “Big”, “Mega” or “Epic” thresholds are provider reporting categories, not promises. They are useful for comparing mathematical versions only when definitions and samples are the same.

Random outcomes do not become due after a long gap. A feature that appeared repeatedly in a demo or marketing clip has no obligation to repeat in a funded session. Previous rounds do not create a debt from the next random result.

Confirm market and device behaviour independently

A title can exist in the supplier catalogue while an operator disables it for a territory, currency, device or bonus. Language localisation is not evidence of legal availability. Confirm the operator's identity, accepted countries and current lobby separately from the provider review.

On mobile, verify that balance, total bet, feature state and help remain visible without overlap. On desktop, check that browser zoom does not hide a purchase control or change the apparent denomination. Mathematical configuration should not change merely because the screen changes; if the help shows another RTP, treat it as a different deployment and record it.

Keep a compact evidence record

For any fact used in a review, save the title, provider, official URL, document date when available, access date and exact territorial scope. For a live session, add the operator domain, Game ID, RTP, currency and a non-sensitive screenshot of the help panel. This makes later corrections possible when a supplier updates a sheet or an operator changes configuration.

Missing information should remain missing. Do not estimate an RTP from results, convert a euro reference range into an operator's NZD limit, or treat another casino's configuration as evidence. A transparent “not confirmed” is more useful than a precise-looking number without the correct source.

Use limits that survive the feature design

Collection meters, expanding grids, sticky symbols and near misses can make a session feel unfinished. Unless the rules explicitly preserve progress, the visible state has no value after the round or feature ends. Set a money limit and time limit before launch, count feature buys immediately, and stop at the limit even when a meter appears close to an upgrade.

No random game is an income plan. Do not borrow, use essential funds or raise the stake to recover a loss. If play stops feeling recreational, use timeout, deposit-limit or self-exclusion tools and consult the site's responsible gambling guide.