A delayed credit, a wrong recipient and an account takeover require different responses. Organise the evidence for the Indonesian payment provider first, then use the appropriate official escalation route while protecting access to your phone and email.
Use the provider-first complaint sequence
The Bank Indonesia complaint guidance sets out a provider response followed, where necessary, by BI education, consultation or facilitation. Retain both the original complaint and the written response. Check the current documentary requirements rather than assuming that a social-media post opens a formal case. State whether the issue concerns the payment status, a charge, the recipient or account access. Do not attach unrelated financial records merely to make the file larger. A clear transaction reference and concise chronology are usually more useful than repeated descriptions of frustration.
Keep fraud reporting and technical recovery connected
If the facts indicate a fraudulent transfer, the IASC route serves a different function from ordinary troubleshooting. If you have lost control of the registered mobile number, also follow the operator’s official recovery process. The OVO security information warns about SIM swapping; the Telkomsel eSIM page explains the sensitivity of activation information. Restoring a number does not by itself resolve a disputed debit, so keep the financial case open until the provider confirms its status. Never pay an intermediary who promises to bypass identity verification.
Comparison of evidence and checks
| Question | What the evidence supports | What to verify |
|---|---|---|
| Pending transfer | Check history and provider status | Avoid a duplicate instruction |
| Wrong destination | Ask sending provider about recovery | No automatic reversal promised |
| Unauthorised access | Restrict account and secure mobile/email | Preserve device and transaction facts |
| Unresolved provider response | Review BI escalation requirements | Attach prior complaint and response |
A practical situation to work through
After a mobile-data interruption, a customer sees the same transfer twice in the wallet history. The first step is to compare the references, timestamps and final statuses rather than assume both are completed debits. Send the provider a short chronology: the first instruction, the timeout, the retry and the two records. If there was only one instruction but an unknown transfer also appears, report that difference accurately and ask for an account-security review. If the phone number simultaneously stopped working, notify the operator as well. Keep each institution’s case number in the same private log. When an answer arrives, reconcile it against the statement and ask a focused follow-up if a specific debit or fee remains unexplained.
Build the incident timeline before escalation
Record when the payment was initiated, its reference, the amount, the displayed recipient, the status and when you first contacted the provider. Distinguish what you personally observed from what another person told you. A transfer you authorised to a deceptive seller is different from a debit you did not authorise. Describe the facts accurately instead of selecting a category because it appears more likely to obtain a refund. Keep the original error or confirmation screen and any written answer; these establish the specific issue to be reviewed.
Account recovery checklist
- Use the provider’s official recovery route from a trusted device. Secure the associated email account and ask the mobile operator to protect or replace a compromised SIM.
- Review logged-in devices, saved payees and recently changed contact details. Revoke access you do not recognise, following the provider’s instructions.
- Keep recovery codes offline and never send identity documents to an unsolicited chat contact. A support agent may require verification through a protected channel, but an incoming caller asking for your PIN or one-time password should not be treated as authenticated support.
Track outcomes and close the loop
Ask for the complaint reference, the next expected update and the written explanation of the outcome. An acknowledgement means a case exists; it does not mean liability has been accepted or a refund approved. If you escalate, attach the earlier complaint and response and state the remaining issue. Keep reporting and recovery separate from any promised commercial remedy. Once access is restored, reconcile the final statement, check for later duplicate debits and update any affected recurring payments. The local sources below were checked on 23 October 2026; their current eligibility rules govern subsequent cases.
Frequently asked questions
Does this observatory operate the service?
No. This is independent editorial information. The named organiser, broadcaster, payment institution or public body operates its own service and sets its own conditions. Use the linked primary source for the action you need.
Are these details permanent?
No. The evidence was checked on 23 October 2026. Match schedules, rights, account limits, provider conditions and complaint procedures can change. Confirm the current information before making a payment, travelling or submitting a case.
What should I save for a later enquiry?
Keep the relevant official page or receipt, its date, the reference number and a short description of what occurred. Store personal and payment information privately, and submit it only through the appropriate verified support channel.
Sources and verification
- Consumer protection and complaints — Bank Indonesia — 2026-10-23
- Indonesia Anti-Scam Centre — OJK / IASC — 2026-10-23
- OVO limits and user protection — OVO — 2026-10-23
- Telkomsel eSIM requirements — Telkomsel — 2026-10-23