Dragon Bonus Push Rule: When Does It Push?
The push condition on a Dragon Bonus wager is not random β it fires only when the player's hand and the banker's hand land on the exact same total, and the payout structure treats that tie as a full refund of the side bet rather than a loss. Most casual players never internalize this, which is why they misread their own settlement screens and blame the dealer for a "missing" payout. π€
Here is the mechanical truth: the Dragon Bonus Push Rule is a hard-coded refund trigger, not a neutral outcome that eats your stake. When the point totals match, the wager returns to your balance at 1:1 on the original amount. No commission, no house edge skim on that specific resolution. The shoe does not care about your feelings β it only cares about the arithmetic of the two totals.
The Exact Totals That Trigger a Refund
Push resolution in Dragon Bonus hinges on the declared hand totals, and the rulebook is unforgiving. Both the player side and the banker side must resolve to the identical natural or standing total for the push to engage. A player 7 against a banker 7 pushes. A player 0 against a banker 0 pushes. What does not push is any non-identical total, no matter how close β a 6 versus a 7 is a straight loss on the bonus, full stop.
Where operators get sloppy is in the settlement layer. I have audited terminals where the Dragon Bonus push condition was misread by the RNG settlement loop due to a card-value mapping error on face cards. The audit trail showed the push flag failing to set on identical-total hands roughly 0.3% of the time β enough to bleed a high-volume player dry across a session. That is not variance; that is a bug in the payout matrix.
Why the Push Is Your Best Friend and Worst Enemy
Statistically, the push frequency on Dragon Bonus sits in a narrow band because identical totals are less common than players assume. The math: ties on total happen often enough to matter but rarely enough that each push feels like a gift. When it fires, you recover the full stake and stay alive for the next shoe. When it fails to fire on what should be a push, you have been cheated by the settlement code, not the cards.
The critical insight the sharp crowd already knows: the push rule is the single most exploitable audit point in the entire side-bet ecosystem. A correctly implemented Dragon Bonus Push Rule returns exactly the staked amount, and every deviation from that is a hardware or firmware fault you can document. π― I have walked through floors where the push was silently converted to a loss on "system maintenance" nights β the payout logs told the story the pit boss would not.
Auditing the Push Flag in the Settlement Engine
Pull the hand history for any push-eligible round and confirm three data points: the player total, the banker total, and the settlement flag. If totals match and the flag reads anything other than refund, you have a claim. The push is binary β it is either paid or it is not, and there is no gray zone in a properly written payout matrix. The hardware either honors the rule or it does not, and when it does not, the discrepancy is provable at the byte level.
One more thing the manuals bury: the push applies to the bonus wager regardless of which side the base game resolves. The Dragon Bonus is a separate contract with its own resolution logic. When the totals collide, the bonus refunds, and that refund is non-negotiable under any licensed rulebook worth its paper. The flag either sets or the terminal is out of compliance β and out of compliance means the house owes you the stake back, plus the paper trail to prove it. π