Yono Rani APK: Multi-Game Lobby, Locked Credit and Cashier Record

The tile grid: modules, wallet and VIP track

The interface is a tile grid with category tabs. Rummy and three-card tables sit beside quick-round modules and arcade formats, and the balance is common to all of them. The grid structure is why a user searching for one format lands in a lobby selling six.

A daily spin or promo-code field is a credit surface, not a game. The wheel issues promotional credit from a fixed prize table, and the code field redeems a campaign token. Both land in the bonus wallet and both carry an expiry.

Because all modules draw on one balance, the risk is concentrated. A device flag, a payment query or a turnover shortfall affects the whole grid at once. The interface presents separate tiles; the back office sees a single account.

The file record for this listing reads package com.mohityonorummy.app. 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 balance area of these clients is usually divided in two. One figure is the cash balance the cashier will pay out; the other is promotional credit that exists only inside the app. The interface rarely labels the difference clearly, so the figures look interchangeable until a withdrawal is attempted.

Credit surfaces in this category follow a small set: mobile OTP binding, check-in streaks, VIP rebates and referral codes. Each usually carries an unadvertised release condition, and no figure should be read as a promise.

The check-in panel is a streak counter with a credit attached. Its design encourages a daily open; its terms keep the credit inside the bonus wallet and expire it on a short clock. Neither the streak nor the expiry is normally shown before the first claim.

When a sign-up credit does not appear, the useful evidence is the registration time, the code used and the number bound. Support requests without those three facts tend to receive a generic reply, and the campaign window may close while the ticket is open.

• Turnover multiple: the credit has to be cycled before any part of it is released.
• Expiry window: credit lapses on a date, after inactivity, or when a campaign ends.
• KYC name match: profile, identity record and bank account have to agree.
• One account per device: linked accounts can freeze every balance on the device.

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

The cashier screen separates inbound funding from outbound payout. The outbound tab collects a UPI ID or bank details and displays a minimum; the inbound tab is what converts a game client into an online money game under Indian law. This page documents the interface without describing a route to use it.

Holds usually trace to four conditions: an unfinished turnover requirement, a KYC name mismatch, a device or payment instrument linked to another account, or a payment-rail outage. None of the four is displayed on the withdraw tab, which shows the status but not the cause.

A payout can arrive smaller than requested. The usual reasons are a processing or gateway fee deducted before transfer, and promotional credit that is cancelled when a withdrawal is made. Neither deduction is itemised on the withdraw tab.

• Requested: the amount is accepted and placed in the queue.
• Processing: transfer started or review open; the label does not say which.
• Under Review: a manual check is holding the request.
• Paid / Rejected: final states; a rejection should carry a reason code.

Lobby tabs and quick rounds: the inventory problem

7 Up Down is a two-dice module resolved against seven: above, below or exact. It is the module most often described as an arcade game, and the one whose presence is easiest to check: the tile shows a dice table instead of cards.

Verification is manual. Tabs, tiles, rules screens and table lists are the evidence; a screenshot on a listing page is not. If a search result says a build has six games, the lobby is the only place that claim can be tested.

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.