NZ-NI-0273 · source record 6 October 2026
Midas Coins — the stack grows until Midas collects it
Coin values land on the first four reels; Midas appears only on the fifth and awards the current collection without emptying the bonus stack.
Supplier sources below. Operator eligibility needs a separate check.

Midas Coins by Quickspin uses a 5×3 layout with 25 lines. Its core loop is a Coin Collect feature: Coin symbols build value across reels one to four, while Midas can appear only on reel five and awards all visible Coin values.
The official product page is unusually specific about the Coin denominations, reel restrictions, starting stack, retriggers and 50× purchase. It is not equally specific about RTP, maximum exposure, stake range or New Zealand distribution. A reliable review keeps that boundary visible instead of importing missing values from third-party listings.
Verified facts at a glance
Midas Coins uses five reels, three rows and 25 fixed lines. Coin values can appear on the first four reels, while the Midas collector is restricted to the fifth. The Marigold Wild substitutes for ordinary symbols but not for the Satyr Scatter or Midas.
Three or more Satyr Scatters award 12 All Is Golden Free Spins. The source says the Satyr symbol pays 2×, which is a Scatter payment statement rather than a global bonus multiplier. During the feature, the Coin Stack starts at 3× bet, grows whenever Coins land and can be paid each time Midas appears without being emptied.
The public page lists a 50×-bet purchase for instant entry with three Satyrs and 12 spins, subject to market availability. It does not confirm that the game or purchase is offered by a New Zealand-facing operator.
How the 25-line base game should be read
The underlying reel game uses fixed lines rather than ways or clusters. Open the live paytable to identify each line and ordinary symbol award. A set of adjacent matching icons that does not follow an active line should not be counted as a win.
Coin and Midas symbols form a collection event distinct from ordinary line settlement. On a base spin, record the Coin values visible on reels one through four and whether Midas lands on reel five. When Midas appears, the provider says all Coin values on those four reels are awarded. Preserve the final server credit rather than inferring it solely from animation.
The official page does not state the frequency of any Coin value. A table of denominations is not a probability table. The 500× Coin is a published possible value, not evidence that it appears often.
Complete Coin denomination table
Quickspin lists fourteen Coin values: 1×, 2×, 3×, 4×, 5×, 7×, 10×, 15×, 20×, 30×, 50×, 100×, 200× and 500× bet. Keep the bet-multiple unit attached to every value. A coin marked 10 represents ten times the stake basis defined by the game, not ten dollars or ten New Zealand dollars by default.
For a settlement check, transcribe each Coin value and its reel position, then add them once. If Midas is absent, do not credit the visible group merely because its sum is large. If Midas is present, compare the calculated collection with the game’s history and account balance.
Currency conversion is a second step. Multiply the verified bet-multiple award by the recorded stake only after confirming which wager value the game uses. The live history should provide the final currency result and remains authoritative if the display rounds decimals.
The fifth-reel Midas restriction
The collector only appears on the last reel. This creates a clear evidence check: a screenshot purporting to show Midas collecting from another reel should be treated as a version conflict, misidentified game or display issue until the official help confirms it.
Midas awards all visible Coin values on reels one through four. The restriction separates collector and collected objects. Do not include a decorative number attached to Midas unless the paytable explicitly defines one, and do not treat ordinary gold-themed symbols as Coin values.
During Free Spins, Midas awards the current Coin Stack rather than merely the Coin symbols on that single screen. This is why base-game collection and feature collection need different ledger fields.
Marigold Wild scope
The Marigold Wild can replace ordinary symbols but excludes Satyr Scatter and Midas. When reconstructing a 25-line win, mark each substitution and preserve the original symbol. A Wild cannot be used to manufacture an extra Scatter trigger or collector appearance.
The official page does not publish the Marigold’s landing frequency or any expanding, sticky or multiplier behaviour. Those properties should not be inferred from the flower design. The verified role is substitution with two named exclusions.
If a line contains multiple Wilds, use the live paytable and round history to determine the credited combination. Avoid guessing which substituted symbol maximises the line when the game has already supplied the settlement.
Triggering All Is Golden Free Spins
Three or more Satyr Scatters award 12 spins. Capture the trigger grid, Scatter payment and opening counter as separate elements. The Satyr’s stated 2× payment does not mean that all Free Spin wins are doubled.
The public source gives one starting allocation for the qualifying threshold and does not publish larger starting awards for four or five Satyrs. If a live version presents a different table, record its game ID and rules sheet rather than silently replacing the provider copy.
At feature start, the Coin Stack should display 3× bet. Record that value before the first spin. The stack is a persistent feature state; it is not the same as the balance and it is not automatically paid at the end unless the actual rules or Midas event establishes payment.
Growing the Coin Stack
Every Coin landing during Free Spins is added to the stack. For each spin, write the opening stack, list newly landed Coin values, calculate the expected closing stack and compare it with the display. This produces a transparent sequence even when several denominations arrive together.
Suppose the stack begins at 3× and a spin lands 2×, 7× and 20× Coins. The expected next state is 32× before considering a Midas award. This arithmetic example illustrates the ledger only; it does not claim that the combination is likely.
If Midas also appears, preserve both the stack growth and collection events in the order shown by the game. The official description says all Coins landing are collected into the stack and Midas awards the current value. A replay or live help should resolve the precise animation order when both occur on one spin.
Midas can award the same growing stack more than once
The defining feature rule is that a Midas payment does not empty the Coin Stack. After a collection, the displayed stack remains available and can grow further on later spins. A second Midas appearance therefore awards the then-current stack again.
Use separate ledger columns for stack value and Midas awards. If a 40× stack is paid, retain 40× as the next opening state. If later Coins add 12×, the stack becomes 52×; a subsequent Midas would then collect 52× under the published rule. These figures are explanatory examples, not reported outcomes.
Do not add the stack to the final return merely because the bonus ends with a positive display. The provider text says Midas awards it; it does not say the remaining stack is automatically paid on expiration. Verify any end-of-feature treatment in the live help.
Retrigger accounting
Additional Satyrs during Free Spins add spins according to a stepped table: one Satyr adds one spin, two add two and three add five. Record the remaining counter immediately before the triggering spin, subtract the consumed spin if the interface does so first, and then record the added amount.
The Satyr symbols can also carry their stated payment. Keep that credit separate from the spin addition. A retrigger extends the opportunity for Coins and Midas to land; it does not itself pay the current Coin Stack.
The public page does not describe an award for more than three additional Satyrs. Do not extrapolate the sequence. Use the active paytable if the reel layout can display another count.
Reconciling a complete bonus
A practical feature sheet needs six columns: spin number, opening Coin Stack, new Coin values, closing stack, Midas collection and retrigger change. Add a seventh for the server’s currency credit when checking a dispute.
At the end, sum ordinary line wins, Satyr payments and every Midas collection exactly once. Do not add each Coin both when it enters the stack and again as a direct balance credit unless the history explicitly shows both operations. The stack is an accumulator; the Midas event is the payment trigger.
If the connection drops, reopen the same round and compare remaining spins and stack value. Starting a new paid round does not replace a missing feature. Save the last known state, round ID and balance for authenticated support.
The 50× purchase
Quickspin states that paying 50 times the bet buys entry to All Is Golden Free Spins with three Satyrs and 12 spins. The purchased feature otherwise works like a naturally triggered bonus according to the public copy.
Before confirmation, record the stake, full currency debit and game version. The 50× price is not the feature’s guaranteed return and should not be compared directly with the largest 500× Coin as if one predicts the other. Coin frequency and Midas timing remain unknown.
The provider warns that Buy Feature may not be available in all markets. Its absence at one operator does not contradict the global page; its presence elsewhere does not confirm New Zealand availability. The live control and operator terms provide the deployment evidence.
Active RTP and maximum exposure
The short HTML overview omits numerical RTP and maximum exposure; its linked official sheet supplies reference fields discussed below. The active operator values still need matching help, and third-party listings should not be silently substituted for that verification.
When recording RTP, capture the game ID, version, operator, date and mode. A purchased feature may have a separately displayed configuration, and the review should not assume that one percentage covers every route.
Likewise, the 500× Coin denomination is not maximum exposure. Multiple Coin additions, repeated Midas collections, line wins and retriggers can interact, so the largest printed Coin cannot serve as a cap.
Mobile and interface checks
On mobile, all five reels, the Coin Stack and the remaining-spin counter should be readable at the same time. The Midas collector’s fifth-reel restriction should remain visually clear in portrait or landscape orientation.
With sound disabled, the interface still needs to distinguish a Coin joining the stack from Midas paying it. Persistent stack value should be text, not colour alone. The purchase confirmation requires an accessible cancel control and a clear total debit.
After backgrounding the browser, verify that the game restores the same round, stack and spin counter. Report any mismatch with device, browser, orientation and version rather than generalising a single display fault.
Who may prefer this structure
Midas Coins may suit readers who like a visible accumulator and a simple collector condition. The stack provides a state that can be followed from spin to spin, while Midas creates distinct payment moments.
It may be frustrating for anyone who treats a large unpaid stack as money already won. The displayed accumulator does not guarantee that Midas will appear again before the feature ends. Session limits should not be raised in response to a growing stack.
The game remains chance-based despite the clear bookkeeping. No sequence of Coin denominations predicts the next collector landing.
Final source audit
Before publication, verify every number against the official page or live help: 5×3 layout, 25 lines, fourteen Coin values, fifth-reel Midas, Marigold exclusions, 12 starting spins, 3× opening stack, retrigger table and 50× purchase. Keep each value attached to its correct mechanic.
Remove any unsupported RTP, stake range, maximum, probability or New Zealand availability statement. Confirm that the artwork caption says it is editorial. A complete review explains the stack and payment sequence precisely without pretending that missing commercial data is known.
Troubleshooting a stack discrepancy
If the displayed Coin Stack does not match the recorded additions, return to the round history before playing again. Compare the opening stack, every Coin denomination on the disputed spin and the closing value. Check whether the screen showed a base-game collection or a Free Spins accumulator, because the two use related imagery but different persistent state.
When Midas lands, separate the amount paid from the stack left on screen. A balance increase can be correct even though the accumulator remains unchanged, because the published rule allows the same growing stack to be collected repeatedly. Conversely, a rising stack without Midas is not yet evidence of a missing balance credit.
Send support the round ID, stake, opening and closing stack, Coin positions, Midas position, remaining spins and before-and-after balance. Do not send a seed phrase, password or authentication code. Ask for the server event log and the versioned rule applied to that round.
Comparing Midas Coins with other collect games
Use mechanics rather than theme when comparing titles. The relevant questions are where value symbols can land, where the collector can land, whether collected value resets, how the accumulator starts, how retriggers work and whether an uncollected total is paid at feature end.
Midas Coins has a specifically published non-reset rule after Midas awards the stack. That fact should not be transferred to another coin-collect title, and another game’s end-of-feature collection rule should not be imported here. Similar gold artwork does not imply a shared mathematical model.
This comparison method keeps the review useful without claiming that one game is more generous. Long-run value requires verified RTP and probability data that the readable Midas Coins page does not provide.
Coin values and Wild substitution
The official page lists Coin values of 1×, 2×, 3×, 4×, 5×, 7×, 10×, 15×, 20×, 30×, 50×, 100×, 200× and 500× bet. The Marigold Wild substitutes for other symbols except the Satyr Scatter and Midas.
Do not treat the highest Coin value as a typical result. The public page does not publish the distribution, base-game RTP or maximum exposure.
All Is Golden Free Spins
Three or more Satyr Scatters award 12 Free Spins, and the Satyr pays 2×. During the feature, every Coin landing is added to the Coin Stack. The stack begins at 3× bet. When Midas lands on reel five, it awards the current stack; the stack is not emptied and can be awarded again.
Additional Satyrs add spins: one adds one, two add two and three add five.
Purchase and territorial checks
Quickspin lists a 50×-bet purchase for 12 Free Spins triggered with three Satyrs. The page says this feature may not be available in all markets. It does not confirm New Zealand operator access.
Frequently asked questions
What is the layout? Five reels, three rows and 25 lines.
Where can Midas land? Only on the last reel.
How does the Coin Stack start? At 3× bet during Free Spins.
How many Free Spins are awarded? Three or more Satyrs award 12.
Is New Zealand availability confirmed? No.
Reference fields, including a rounding discrepancy
The linked official Midas Coins sheet identifies midascoins, supplier volatility 3.5 on a one-to-five scale and euro reference stakes of 0.25 minimum, 100 maximum and 1 default. It prints 96.02% total RTP and a 5,000-times-bet maximum field. That maximum is not labelled as a billion-spin sample, unlike some older supplier sheets; it still describes the reference model, not a verified current operator deployment.
The printed components are 47.11% Base Game, 23.26% Base Feature and 25.64% Free Spins. They add to 96.01%, one hundredth of a percentage point below the displayed total. Keep both the printed total and that arithmetic difference rather than altering a component to make the table balance. Rounded component fields are not a separately established conditional return for a purchased feature.
These reference values clarify the earlier short-HTML omissions, but they do not supply Coin landing probabilities or the exact within-spin order of growth and collection. The highest 500-times Coin denomination remains a symbol value, not the reference maximum or a likely result. Versioned help must connect any model field to the game actually being inspected.
Why repeated collections weight earlier Coins more often
Here is an invented sequence of confirmed feature events, measured in bet units. Assume the round history establishes each addition before the next collection; no unresolved simultaneous Coin-and-Midas event is used to infer settlement order. Start with the published three-unit stack, add a two-unit and a five-unit Coin, and confirm a Midas collection of the resulting ten. The stack remains ten after payment.
Next add twenty without a collector. Add seven later, then confirm a collection at thirty-seven. Another documented Midas event with no intervening Coin awards thirty-seven again. Finally add one hundred, but suppose the feature ends with no further collection and no separate terminal-payment rule established.
| Confirmed phase | New Coin units | Stack afterward | Midas credit |
|---|---|---|---|
| First addition, then collection | 2 + 5 | 10 | 10 |
| Growth without collection | 20 | 30 | 0 |
| Later growth, then collection | 7 | 37 | 37 |
| Another collection without growth | 0 | 37 | 37 |
| Final uncollected addition | 100 | 137 | 0 |
The documented collection total is 10 + 37 + 37 = 84, not the closing stack of 137 and not the sum of every displayed stack. Adding the stack rows would give 251 and repeatedly mistake an accumulator snapshot for a new payment. Eighty-four covers only these collector payments; verified line wins and Satyr credits belong in separate award rows, so it is not presented as the entire feature payout.
There is another way to reproduce the eighty-four. The opening three units participate in three collections, contributing nine. The early seven new units also participate three times, contributing twenty-one. The later twenty and seven each participate in two collections, contributing forty and fourteen. The final hundred participates in none. Thus 9 + 21 + 40 + 14 = 84.
This weighted sum explains the non-reset mechanic without suggesting that earlier Coins are more likely, that a collector is due, or that a player can arrange the events. Each weight is counted retrospectively from the recorded collections, not predicted in advance. A large final accumulator can coexist with a smaller paid total. Keep that unpaid display out of balance reconciliation unless the active rules and account history establish another actual credit.
Official source
Bottom line: the important states are current Coin Stack, Midas landing and retrigger count—not the gold theme alone.
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 Quickspin, 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.
Primary source and correction path
This guide separates documented product information from market availability. Check the official source and the game help inside the exact version offered before making a decision.
