Hi Rummy App: Lobby Structure, Bonus-Wallet Terms and Cashier Record

Inside the 13-card client: tables, controls and the drop price

The core format is thirteen cards per player, a closed deck, an open discard pile and a meld requirement. A valid declaration needs two sequences, at least one without a joker. Points are counted on the cards still in hand, which is why the drop decision is made before the hand is complete instead of after.

The drop control ends a hand early at a fixed penalty. A first drop before the first draw is the cheapest; a middle drop costs more; a full drop after the hand is under way costs most. The button is deliberately prominent, because the penalty is lower than a badly timed declaration.

The table list is organised by format and entry band, with a practice section that does not touch the cashier. Sorting is by activity or stake, and the filter persists between sessions. The lobby is where the format decision is made, before any card is dealt.

• 13-card points: meld 13 cards into sets and sequences; points counted on unmelded cards
• Pool 101 / 201: elimination pool where the running score decides who leaves the table
• Deals: fixed number of deals, best-of-three or best-of-five scoring
• Practice: virtual-chip tables with no cashier entry

The bonus wallet, the cash wallet and the gap between them

The wallet screen presents one total and two ledgers. Cash is what a payout request can draw on; promotional credit is confined to the lobby. The cashier applies that distinction silently, which is why the amount available is often lower than the amount displayed.

Mobile OTP binding, daily check-in, VIP tier rebates and referral commissions are the four entry points that appear repeatedly in this category. Their conditions differ, and the pattern does not confirm what this build exposes.

When a listing says “bind your number to unlock the offer”, the binding is doing account-identity work, not just marketing. The number becomes the recovery channel and the payout reference. Changing it after a credit is issued usually triggers a fresh review.

Bonus abuse controls are the least visible part of the wallet. Device identifiers, installed-app lists and payment metadata are combined to spot linked accounts; when the rule trips, the usual outcome is a hold on all balances instead of a warning.

• Advertised amount: the headline figure, with no published schedule.
• Source: a listing page, with no operator term sheet.
• Release: turnover and expiry decide whether the credit moves.
• Forfeiture: unconverted credit can vanish at withdrawal.

Cashier screen: UPI, IMPS and the gates that hold a payout

Every client in this index presents the cashier as a pair of tabs. One moves money in, one moves money out. The outbound tab is the one this section documents: destination fields, a stated floor, and a status line that is usually the only feedback a user receives.

Statements are where payout terms become checkable. Without one, a user cannot prove what was requested or what was deducted. This record notes whether a statement surface is described in the listing; most listings do not mention one at all.

One request at a time is the rule that keeps a payout traceable. Multiple simultaneous requests create ambiguity about which one is being reviewed, and the operator’s reconciliation may take longer than the original review would have.

Variant naming: what the number after the brand means

A family name is not a publisher. The Yono/777 cluster contains unrelated packages that reuse a lobby design, which is why the same query returns several apps that look alike and behave differently at the cashier.

Family queries dominate this category. Users search the shared name, land on a variant page, and assume they have found the product. The page’s job is to separate the family label from the build in front of them.

What the file record can and cannot tell you

Permissions are the part of a manifest a user can actually audit. A rummy client needs network access; it does not need to read messages or draw over other apps. Accessibility and device-admin grants are the two that most often appear in repackaged builds.