ACCOUNT RECORDS
Deposits and Withdrawals: A Guide to Payment Records
A wallet says completed, the account balance looks unchanged, and a support chat asks what happened. The useful next step is to gather the two records and their references. Sending another payment creates another transaction; it does not explain the first one.
Keep payment and game references separate
A payment reference identifies a transfer through a payment service. A game-round ID identifies an event inside a game. An operator account entry may use a third reference to connect the two systems. None should be casually substituted for another.
Write down the amount, currency, date, timezone and status shown in each place. “Completed” on a payment receipt and “credited” in an operator account describe different records. A mismatch needs reconciliation by the services responsible for them.
| Record | Keep |
|---|---|
| Payment service | Reference, amount, currency, timestamp and displayed status. |
| Operator account | Transaction entry or request ID and current status. |
| Game issue | Exact game title, round ID and settled history. |
| Support exchange | Case number, date and the exact question still unanswered. |
Check the terms before there is a transaction
Look for the account holder requirements, currency, available payment route, fees and withdrawal conditions in the verified operator terms. This guide does not confirm that INAGBET accepts GCash, Maya, a particular bank or any specific e-wallet. A familiar payment logo is not enough to establish an available method.
Use Philippine time (UTC+8) when recording a local event and keep any different timezone shown on the original receipt. Retain the actual status even if another record uses a different label. A pending request is not a completed payment or a zero amount.
Use a short timeline instead of repeated screenshots
For example: “14:05, payment service shows PHP 500 completed, reference ending 4821. 14:10, operator transaction list has no matching credit. 14:20, support case opened.” These are invented example events, not a reported incident or a normal processing-time claim.
One clear timeline can show whether the issue is a missing entry, a pending request or a disputed game result. Keep original records privately. Make a redacted copy for any place that does not need the full document.
Ask for reconciliation, not a general promise
A precise private message is: “Please reconcile this payment reference with my account transaction history. The payment service shows the amount and time stated below, but I cannot identify a matching credit. Please provide the account entry or case reference and explain the next step.”
Use the support channel inside the verified operator site. Include only the identifiers that service needs. Do not send a password, one-time code, full payment PIN or remote-access permission. Suspicious messages should be verified independently, rather than through the link in the message.
Do not invent a deadline while the status is unresolved
Withdrawal times depend on the operator, payment route and status of the request. This publication has not measured those times. Check the specific terms and ask which stage the request has reached, including whether an account-verification issue is holding it.
If you suspect an unauthorised transfer, contact the payment provider through its established app or website promptly. Preserve the record and follow its reporting process. For an unresolved operator dispute, consult the relevant regulator's current complaint information; a supplier licence from another jurisdiction is not automatically the right route.
Common questions
Can JILI3 trace or reverse my payment?
No. This publication cannot access account balances, operator transaction systems or payment-service records.
Should I post the receipt in a public group?
Not unredacted. Keep identifiers, personal details and account information private. Use the verified service's private support process.
Should I pay again to unlock a withdrawal?
Do not send additional money in response to an unverified demand. Independently check the request with the operator and payment provider, and preserve the message.
In brief
A useful support case has an exact amount, currency, timestamp, reference and one unresolved question. Keep secrets out of the message, retain the original evidence and avoid creating additional transactions while investigating.