100JUDI Disconnect Policy Malaysia

100JUDI Official Site Malaysia provides this disconnect policy to explain, in practical terms, what happens when a player experiences an internet interruption, device crash, app freeze, or sudden session timeout while using the platform. Online gaming can involve fast decisions and real-time transaction states, so every member deserves clear guidance about pending outcomes, temporary balance differences, and how final settlement is confirmed. This page is designed to reduce uncertainty by showing how interrupted game rounds are processed, how records are validated, and what members should do first before contacting support. If you are reading this after an interruption, stay calm and review each section step by step. Most temporary inconsistencies resolve automatically once the game provider returns status updates to the main wallet system.

At a policy level, our approach is simple: preserve fairness, protect account integrity, and resolve unsettled transactions based on verified provider logs rather than guesswork. A disconnection does not automatically mean a loss, a win, or a refund. The correct result depends on the exact game state when interruption happened. Some rounds may have been fully accepted and completed before your screen froze. Some may have been accepted but still pending. Others may not have reached confirmation state at all. Because each state carries a different settlement rule, our process always relies on auditable records from integrated systems. That is why we ask members not to submit duplicate bets while waiting for a pending result to sync. Waiting for confirmation protects your balance from accidental repeated actions.

Purpose and Scope of This Policy

The purpose of this policy is to define a transparent rule set for interruptions across supported categories, including slot, table, live, sportsbook-related interfaces, and selected event-based formats. This document applies whenever account activity is interrupted by unstable data connection, browser failure, operating system crash, battery shutdown, forced app closure, or temporary provider-side latency that prevents your screen from updating in real time. It also covers cases where players reconnect and see a different amount than expected because pending rounds were later settled correctly in the background. By setting expectations in advance, we help members understand what is normal behavior, what requires action, and what timeline is reasonable for final synchronization.

This policy does not replace provider game rules, platform terms, or legal limits. Instead, it works together with those references to establish practical recovery steps during routine disruptions. If any conflict appears between this page and underlying provider transaction rules, settlement follows official system logs and the technical order of confirmed events. We use a consistent principle: whichever status is proven by valid transaction records becomes the authoritative result. That standard protects both players and platform integrity by ensuring identical treatment for similar events. In short, fairness is not based on perception at the moment of disconnect; fairness is based on reproducible data after complete validation.

Common Causes of Disconnection

Most interruptions happen for ordinary reasons that are not unusual in mobile-first usage environments. In Malaysia, many players switch between Wi-Fi and mobile data while moving, and that handover can briefly break active sessions. Weak signal in crowded areas, VPN instability, background application refresh, battery saver restrictions, device overheating, and auto-update restarts are also common causes. Even when the platform itself is stable, external network routing conditions can delay packets and make a game appear frozen. These scenarios are frustrating, but they are manageable when players know that unresolved rounds are tracked with transaction references rather than visual memory alone.

On desktop, interruptions can come from overloaded browser tabs, outdated extensions, ad blocking conflicts, or local firewall settings that intermittently block secure requests. On mobile apps, aggressive memory management may suspend background processes, especially on low-RAM devices. In both environments, a disconnect often appears dramatic to the user even when the back-end has already recorded the bet state accurately. Understanding this gap between what you see and what the system has logged is essential. Policy clarity begins with that distinction: visual interruption is not always transaction failure. The settlement engine continues to determine final status according to accepted request sequence and provider response integrity.

What Happens Immediately After a Disconnect

Right after a disconnection, one of three outcomes usually applies. First, the wager may not have been accepted, in which case no bet is deducted and no round exists for settlement. Second, the wager may be accepted but unresolved, meaning the round status is pending until the game provider confirms completion or cancellation. Third, the wager may already be completed, but your screen disconnected before displaying the result; in this case, balance changes appear once your wallet syncs with confirmed game history. These scenarios look similar from the player side, so checking transaction records is more reliable than assuming what happened in the final visible second.

During this period, members should avoid repeated clicks or rapid re-entry attempts to force results. Duplicate actions can create additional accepted rounds that complicate balance tracking and increase confusion. A safer approach is to reconnect, refresh account history, and allow automatic synchronization to finalize outstanding records. In many cases, sync completes within a short period, especially for standard game types. If status remains pending beyond the normal window, support can escalate by transaction ID. This policy is intentionally structured to make that escalation predictable: identify the session, confirm timestamps, compare wallet movement, and verify provider round data before any manual adjustment decision is made.

Pending Bets, Settled Bets, and Wallet Sync

Pending bets are often the center of concern because players can see a temporary deduction without immediate closure. A pending state means the platform has accepted an action but still waits for final round outcome from the provider. This is a normal technical stage, not an error by default. Once the response is received, the system updates your wallet according to confirmed result. If the round is voided by provider rule, your stake is returned. If the round is completed, payout or loss is applied accordingly. The key point is that wallet movement during interruption may appear incomplete for a short time, then normalize once all records are fully reconciled.

Settlement order can vary by game engine. Some providers confirm instantly; others queue confirmation when network stability returns. For this reason, policy timelines are described as reasonable windows rather than rigid seconds. While waiting, players should use a single trusted access point and avoid simultaneous login attempts from multiple devices, which can create session conflicts. We also recommend capturing simple evidence if delay feels unusual: game name, approximate time, stake amount, and screenshot of history page. These details help support investigate efficiently without relying on memory-only explanations. Our goal is always accurate settlement first, then communication that clearly explains why each outcome was applied.

Fairness Principles Used in Resolution

Every disconnect case is evaluated under fairness principles that prioritize objective proof. First principle: transaction chronology. We examine the exact sequence of accepted requests and responses. Second principle: provider authority on round completion. If the game provider marks a round completed with result data, that record governs settlement. Third principle: wallet integrity. Any adjustment must match validated round state and cannot be made based on estimates. Fourth principle: equal treatment. Similar technical scenarios should produce consistent outcomes across users. Together, these principles reduce disputes and protect confidence, especially during high-traffic periods when manual assumptions would create inconsistent decisions.

Fairness also includes clear communication. Even when final outcome is not what a player hoped, the process should be understandable. Support responses therefore focus on explainable checkpoints: whether bet acceptance occurred, whether provider response arrived, whether result status is completed or void, and whether wallet update has synchronized. If a correction is required, it is applied according to logged evidence rather than discretionary preference. This rule-based approach protects both sides and ensures that disconnection events are managed through stable standards instead of ad hoc handling.

Player Responsibilities During Connectivity Issues

Members also play an important role in faster resolution. Keep your app and browser updated, use stable connectivity where possible, and avoid force-closing active rounds unless the device becomes unresponsive. If you must reconnect, return to history or transaction views before placing new bets. This habit gives you a clean status check and reduces accidental duplication. It is also useful to limit third-party overlays or battery optimization settings that aggressively terminate network sessions in the background. Responsible session management helps prevent confusion and allows settlement systems to complete pending records with less interference.

If an issue repeats frequently, troubleshoot your local environment before assuming system fault. Test another network, restart your device, clear cache when appropriate, and ensure time/date settings are correct. Inconsistent local clock settings can affect token validation and cause unexpected session expiry. These practical steps are often enough to reduce interruptions significantly. Our policy acknowledges that digital access conditions vary, but user-side optimization still matters. Better connection hygiene improves experience quality and lowers the chance of unresolved states that require escalation.

How Support Handles Escalation

When standard sync does not resolve a pending status within reasonable time, support opens a formal review ticket. The review process usually includes session verification, provider query, wallet log comparison, and timestamp reconciliation. A clear ticket contains your account identifier, approximate incident time, affected game, bet amount, and observed discrepancy. These details let the team locate the exact round quickly. Submitting multiple incomplete tickets for the same incident can slow processing, so one complete request is better than repeated short messages. We prioritize accuracy because premature closure can lead to further confusion.

Resolution timelines depend on incident complexity and provider response speed. Straightforward cases can close quickly; complex multi-round interruptions may require additional technical checks. During investigation, temporary display inconsistencies may remain visible, but final adjustments follow confirmed records only. If your case is escalated, keep communication in one channel and avoid changing core account settings until review is done. This helps preserve traceability. Our objective is to deliver a clear final response with outcome reason, not just a status update without explanation.

Category-Specific Notes

Different categories may apply different completion logic during interruption. In reel-based games, round completion often happens server-side even when animation does not finish on your screen. In live formats, the host timeline and provider event logs determine whether participation was confirmed before disconnect. In event-driven interfaces, the acceptance timestamp relative to market closure or state update is critical. These category differences are why support may request exact game names and timing details. A generic statement such as "my game hung" is understandable but not enough for precise log matching in systems with multiple engine types.

Although back-end logic differs, policy consistency remains: accepted rounds settle by confirmed result, unaccepted attempts are not charged, and unresolved states stay pending until official provider status is returned. This framework prevents arbitrary outcomes and keeps dispute handling objective. We recommend that players review category instructions when trying a new format, especially if it includes time-sensitive entries. Better awareness before play reduces stress if interruption occurs later.

Data Integrity, Security, and Audit Trail

Disconnect handling is closely linked to data integrity. Every meaningful event in the transaction path is designed to leave an audit trail: request initiation, acceptance state, provider response, and wallet update. This structure enables post-incident verification and protects players from unsupported assumptions. Security controls also help prevent unauthorized actions from being treated as valid bets. If account anomalies are suspected, additional checks may be required before settlement communication is finalized. These checks are protective, not punitive, and ensure that outcomes reflect legitimate activity tied to verified account sessions.

From a compliance perspective, maintaining clear logs allows the platform to defend fair decisions and correct any rare synchronization errors when evidence supports correction. Transparency is strongest when both sides can rely on the same source of truth. That is why this policy emphasizes records over recollection. Players are encouraged to keep their own notes when an interruption occurs, but final outcomes must always align with auditable system data.

Best Practices to Minimize Future Interruptions

You can reduce disconnect frequency by adopting a few practical habits. Use stable internet with adequate signal strength, close heavy background apps, keep sufficient battery level, and avoid switching rapidly between networks during active rounds. On browsers, maintain current versions and disable unnecessary extensions that interfere with secure content delivery. On mobile, allow essential app permissions and disable aggressive battery restrictions for active sessions. These basic actions improve continuity and reduce the chance that an otherwise normal round appears unresolved.

It is also helpful to pace sessions with short breaks and status checks. If your connection has been unstable, verify history synchronization before continuing. A thirty-second check can prevent multiple unresolved rounds and save time later. Responsible play and technical readiness work together: when players manage both, overall experience becomes smoother, safer, and more predictable.

Related Official Pages for Reference

For wider platform context, members may review our profile at About Us, partner information in the Affiliate Program, and category pages for Card Games, Casino Games, Esports Betting, Fishing Games, Live Casino, Mega888, Mobile App, Slot Games, and Sports Betting. Policy references are available at Privacy Policy, Responsible Gaming, and Terms and Conditions. You can also check support and community resources through FAQs, Promotion, and Chatroom, while advanced users can review RTP details and premium updates via VIP. The canonical policy location remains Disconnect Policy.

Frequently Asked Questions

Will I automatically lose money if my connection drops mid-round?

Not necessarily. A dropped connection does not automatically decide win or loss. Final settlement depends on verified round state in provider records. If your wager was never accepted, no charge applies. If accepted and completed, normal result applies. If pending, it updates after synchronization.

Why does my balance look different right after reconnection?

Temporary differences can happen while pending rounds are waiting for provider confirmation. The wallet may show an interim amount until final status arrives. This usually resolves automatically. If it remains unresolved beyond a reasonable period, contact support with incident details for review.

What should I do first when a game freezes?

Reconnect safely, then check transaction history before placing new bets. Avoid repeated clicks or duplicate entries while status is unclear. Capture basic evidence such as game name, time, and amount if you need escalation. This helps speed up accurate investigation.

Can support manually change a round result on request?

Support cannot arbitrarily override valid provider outcomes. Any adjustment must match verified logs. If an error is proven, correction is applied according to documented records. This protects fairness and ensures consistent handling for all members.

How long does escalation usually take?

Timelines vary by complexity and provider response speed. Simple sync cases may resolve quickly, while multi-event interruptions can take longer due to deeper reconciliation checks. Submitting one complete ticket with clear details usually leads to faster resolution than multiple partial reports.

Does this policy apply to all game categories?

Yes, the core principles apply across categories, though specific completion logic can differ by provider and game type. The same fairness framework remains in place: accepted rounds settle by confirmed logs, unaccepted requests are not charged, and pending rounds update once validated.

This disconnect policy is published to set clear expectations, reduce uncertainty, and protect fair treatment for all members. By combining transparent rules, technical audit trails, and practical user guidance, 100JUDI aims to make interruption handling dependable even when network conditions are not perfect.