Yono Rummy APK: Tile Grid, Shared Wallet and Payout Notes

Quick rounds and card tables under one balance

The lobby presents module tiles on one dashboard, with no single table list. Card formats, quick rounds and arcade formats sit side by side, and each tile opens its own rules screen. The shared balance is the only thing that ties them together.

7 Up Down rolls two dice and resolves on the total: above seven, below seven, or exactly seven. The exact-seven outcome carries the longest odds and the highest stated return. The module is a dice comparison, and the result feed shows the last totals.

The VIP panel aggregates activity from every tile. One level, one progress bar, and a rebate that rises with tier. The design intent is to move a player between modules without losing the sense of progress, and it is the main reason the grid is sticky.

• Category tiles: card, quick-round and arcade groups share one dashboard.
• Shared wallet: every tile draws on the same balance.
• Result feed: quick rounds publish a rolling feed of outcomes.
• VIP progress: one level bar spans every module.

The file record for this listing reads package com.ptccg.zn3633.jqthpmwv, version 6.8.7, 83.4 MB. The card above carries the evidence state for each field; a missing value is marked instead of guessed.

Promo codes, campaign credit and why the same label differs between listings

The first thing the balance screen hides is the difference between cash and credit. A withdrawable balance and a promotional wallet are displayed together, often under a single total. The cashier reads only the first, and the second usually disappears on withdrawal instead of converting.

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.

Turnover conditions convert a credit into an obligation. The balance shows the credit; the terms attach a multiple; the cashier applies the multiple before release. When the multiple is not shown in-app, the only reliable source is the operator’s published terms, which many of these listings do not carry.

A single app can carry several advertised amounts at once. The differences usually track the listing’s age or the affiliate’s campaign, not a change in the product. Treat every one of them as a claim.

Payout friction: what the withdraw tab shows and what it withholds

The cashier divides into funding and payout. Funding is where a payment is authorised; payout is where a balance is requested back. The two share a header and little else, and only the payout side is documented here.

Bank payout collects an account number, an IFSC and sometimes a branch name. The rail underneath can be IMPS, NEFT or an internal transfer to a pooled account. The receipt rarely names the rail, which makes a delayed credit hard to trace.

The stated floor in this category is usually ₹100 †. It applies to the withdrawable balance only, so a user holding a large bonus wallet and a small cash balance can still sit below the threshold. The screen shows the floor; it does not show which part of the balance qualifies.

• Request: the amount is accepted and queued.
• Review: turnover, KYC or a risk check runs.
• Transfer: IMPS or NEFT carries the money.
• Posting: the bank credits the account.

One family, many packages: how to tell variants apart

A suffix like 777 is a marketing token. It does not map to a version, a release channel or a feature set. Two builds with the same suffix can be months apart in code.

Different package, different account. A family variant does not share a wallet or a login with its siblings unless the operator backs them with one account service. Most do not, which is why a balance does not follow a user between variants.

The install side: file, format and the platform claims

A file delivered outside Google Play is installed through the system package installer. Android requires the installing app to hold permission to install unknown apps, and that permission is granted per source, not globally. After installation the source permission can be revoked without affecting the app.