A pending status does not establish its cause. Record the request ID, amount, fee line and status for Yono Rummy. Do not share an OTP, UPI PIN or remote screen access, and do not make a new payment to test a release promise. Check any contact against a source you can independently verify.
The current sources do not establish the former route-specific floor comparison. One Yono Rummy page advertises ₹100 and 10–30 minutes; another gives a ₹100–₹30,000 range. These statements do not diagnose a pending request or guarantee a bank credit.
Current public text and its scope
| Current source context | Claim and limitation |
|---|---|
| yonorummy-apk.com | ₹51 automatic sign-up, ₹100 minimum and 10–30 minutes are advertising. Its KYC text mentions PAN/bank details for a first withdrawal, not the former Aadhaar-at-registration or numeric PAN trigger. |
| yonogames.com.in product detail | A ₹100–₹30,000 withdrawal range is page-supplied, not a tested cashier or named KYC checklist. |
| freemalamaal coupon page | SIGNUP51 is advertised for ₹51. A coupon page is not evidence that an in-app field exists or a code works for the account. |
Preserve the request before another submission
- Save the request ID, exact status, amount and time.
- Record the actual route, fee and wallet label. Do not infer a route floor from a figure on another page or a general coupon FAQ.
- If a document or ownership field is explicitly flagged, record it. The first-withdrawal PAN/bank wording does not prove the cause of this request’s delay.
- After verifying the publisher/contact, ask which check is open and which written rule applies using a masked status reference.
- Do not add a deposit, pay an outside release contact or resubmit while the first outcome is unclear.
Separate the app request from a missing bank credit
Preserve the transaction reference and contact the bank or payment app about an expected credit that did not arrive. If a transfer appears unauthorised or fraudulent, report it promptly through the official fraud route. Do not wait for an invented app deadline or share an OTP, UPI PIN or remote access.
What this record cannot establish
No account-specific floor, KYC result, cancellation flow or payout was tested. The public 10–30 minute statement is not a measured service promise, and a source’s general legal or KYC assertion should not replace current authoritative guidance.
Sources and evidence grades: Yono Rummy — Withdrawal pending / failed
| Claim / source | Link | Checked | Grade |
|---|---|---|---|
| Yono Rummy product page: ₹51 auto sign-up/₹100 minimum/10–30 minutes; first-withdrawal PAN/bank details are untested page claims (checked 4 Nov 2026) | Open source ↗ | 4 Nov 2026 | C — public source, not account/APK verification |
| Yono Rummy detail page: ₹100–₹30,000 withdrawal range; no named KYC checklist in the cited detail (checked 4 Nov 2026) | Open source ↗ | 4 Nov 2026 | C — public source, not account/APK verification |
| Coupon page advertises SIGNUP51 for ₹51; in-app code field and validity not tested (checked 4 Nov 2026) | Open source ↗ | 4 Nov 2026 | C — public source, not account/APK verification |
Related questions
What is the current Yono Rummy minimum?
The cited product pages advertise ₹100 or a range starting at ₹100, without a tested account route. The older route split was not substantiated by the current check.
Does 10–30 minutes guarantee my payment?
No. It is a product-page advertising statement, not a measured transfer or account-specific SLA. Preserve the exact status and request ID.
Why is my withdrawal pending?
No cause was established. Record the actual route and any specifically flagged field and ask for the applicable written rule through a contact you can verify.
Can I cancel or deposit to fix it?
No cancellation flow was tested. Do not deposit to release a request or resubmit while its outcome is unclear; retain any actual cancel confirmation if one exists.
Other apps with a Withdrawal pending / failed answer
Same problem type, different records: Yono Rummy — Withdrawal pending / failed. Each figure is the claim stored in that record, not a shared result.
