How a withdrawal request is handled
At link jnetoto we separate requests into three processing lanes: automated routing for verified accounts, manual review for flagged transactions, and reconciliation for third-party payment rails. Automated routing covers most standard withdrawals to DANA, e-wallet, mobile banking, local payment, online payment and bank accounts with an existing, matched beneficiary record. Manual review is reserved for cases that require identity confirmation, unusual activity checks, or tournament prize adjudication from scheduled events such as Liga 1 or Piala AFF.
Segregating routing lanes reduces review time and makes audit trails clearer for both bank transfers and e-wallet settlements.
For players based in major cities — from Jakarta through Surabaya and Bandung — the visible difference is the number of verification steps requested when a new beneficiary is recorded. We request matching name fields, account number formats, and occasionally a short selfie verification if a profile is incomplete. For tournament settlements tied to MPL or scheduled slot leaderboards, we keep a separate audit trail to reconcile placements and prize tiers before release.
Standard steps for submitting a withdrawal
- Open the withdrawal form and confirm the destination (e-wallet or bank).
- Confirm beneficiary details exactly as registered — small mismatches trigger manual review.
- Upload or confirm identity details if requested; these are only asked once per new beneficiary.
- Submit the request and monitor the request status in your account history.
- If the request is routed to manual review, respond to the support ticket with the requested documents.
We publish a concise audit entry for every state change in a withdrawal request. Those entries include timestamps, the processing lane, and the last-agent note when a human reviewer is involved. For bank rails such as mobile banking, local payment, online payment, e-wallet we capture beneficiary bank code and account number format to speed reconciliation. For mobile banking and wallet rails we record the receiving identifier used at the time of submission.
Common flags and why they matter
A few triggers send a request to manual review: new beneficiary details, a recent change to KYC documents, or withdrawal patterns that do not match recent deposit rails. We also flag requests associated with tournament adjustments — for example a scheduled weekly slot tournament payout where finishing positions require cross-checking with the leaderboard. For such cases our team annotates the request with the tournament ID and scoring snapshot.
Verification documentation
We only request documents necessary to match account records; submitting clear copies of matching bank or e-wallet registration speeds the review.
For assistance we provide in-app messages and ticketed support. If you prefer a quick confirmation for a transaction tied to a MotoGP or Liga 1 promotional schedule, reference the event name and the withdrawal ID when you open a ticket. We log that reference on both sides of the review to maintain a clean reconciled record.
We maintain this guide to reduce repeated tickets and to make the withdrawal flow more transparent for players using local payment, online payment, e-wallet, mobile banking and bank rails.
Support channels
We operate multiple support channels to match the issue type. Live chat is optimised for transactional questions — status checks, confirmation of beneficiary formats, and quick document submissions. Email is reserved for detailed correspondence that requires attachments or a formal record, such as documents related to KYC, notarised prize confirmations, or complex dispute evidence. The in-app help centre is organised by topic and includes the common steps for submitting a withdrawal, updating a beneficiary, and reading request history.
When choosing the channel, use live chat for short clarifications on a single request ID. Use email when an issue requires multiple documents or when you need a persistent thread. For tournament-payout questions, include the tournament name (for example Liga 1 or Piala AFF) and the result snapshot in your first message so the case manager can reconcile against the prize ledger. We try to route each inquiry to a subject-matter reviewer: payments desk for rail-specific problems, compliance for verification issues, and operations for reconciliations between game results and wallet credits.
Common request categories
Withdrawal requests typically fall into a few categories. First, standard withdrawals from a verified account to a registered beneficiary — the most straightforward category. Second, withdrawal review where beneficiary details mismatch or a newly added bank or e-wallet requires identity confirmation. Third, tournament-related payouts where finishing positions are verified against scheduled event logs for slot and esports tournaments. Fourth, technical issues such as form submission failures or payment-provider callbacks failing to confirm a settlement.
Login and KYC problems are also frequent. A user who has changed name fields at the payment provider layer may need to provide supplemental documentation; when that happens we list the exact files we require. For tournament and leaderboard disputes, the request should reference the event name and the snapshot ID so the adjudication team can replay results and confirm placement before releasing funds.
Response window expectations
Response windows vary by processing lane. Automated routing produces an immediate ledger entry and a queued settlement attempt; manual reviews require agent interaction and a documented response. We do not publish fixed minutes for settlement, because payment-provider callbacks and bank batch cycles differ across rails. Instead, we publish typical stages: request logged, beneficiary matched, verification requested, review completed, and settlement attempted. Each stage has a visible timestamp on the request history so you can see where a request stands.
For larger or tournament-linked withdrawals the review step may involve a reconciliation window with partner platforms — for instance when cross-checking a weekly slot leaderboard or an MPL match result. When that happens we annotate the expected next checkpoint in the ticket so you know which stage is pending: compliance, partner reconciliation, or payment-provider confirmation.
Escalation flow
Escalation happens when a ticket lacks required documentation after an initial review, when a settlement discrepancy is identified between our audit and a payment provider, or when a user requests an administrative review for a tournament result. We escalate to a senior reviewer who can request additional logs, open a partner query with the payment provider, or convene a short adjudication for prize disputes. To speed escalation, include the withdrawal ID, beneficiary details, any screenshot of the payment provider response, and the relevant event or game identifier (for example Mahjong Ways leaderboard ID).
Our escalation notes are chronological and visible to the case owner. That means the person handling the ticket can see why the case moved from standard review to escalation, what evidence was requested, and which partner teams have been engaged. If further steps are needed on your side, the escalated case will list the minimal required items to resolve the issue.