Payment incident evidence helps separate what happened to your money from what a message claims happened. If a payment associated with an ABC8 account is missing, duplicated or unfamiliar, protect the financial account first and preserve the original transaction record. A delayed balance alone does not establish fraud, and another payment is not evidence that the first one can be recovered.
Describe the incident before naming its cause
Write down whether you authorised the payment, whether your bank or wallet records a debit, and what the recipient’s service shows. These are separate facts. A message saying “successful” is not the same as a statement entry; a service balance is not a bank statement.
- Unrecognised transaction: you did not initiate or approve the payment. Report that fact promptly to the financial institution.
- Payment induced by deception: you made the transfer after a misleading request. Explain the request and your actions accurately; do not describe it as a payment you never made.
- Missing credit or duplicate debit: record the amounts and reference numbers before assuming a cause.
The distinction matters because the institution needs to investigate the actual sequence. This guide does not confirm the outcome of any individual ABC8 transaction.
Match each question to the record that can answer it
| Record | What it can support | What it cannot prove alone |
|---|---|---|
| Your bank or wallet transaction entry | The amount, reference and status that institution records. | That another service credited the same amount to its internal balance. |
| A destination balance screenshot | What the interface displayed at the captured time. | Whether a transfer failed, was reversed or was posted later. |
| A chat message requesting payment | The wording, sender identifier and timing of that request. | The sender’s authority or the truth of the promised outcome. |
| A complaint acknowledgement | That the stated channel created a case or received a message. | That the investigation is complete or reimbursement approved. |
Organise payment incident evidence by transaction reference, keeping bank entries, destination screenshots and support messages together. Each record answers a different question. Separate “I saw no credit at 14:20” from “the recipient never received anything”. The first is a dated observation; the second requires information you may not have.
Two notifications are not automatically two debits
Consider two fictional alerts, each displaying ₱800. If both refer to the same transaction reference and the account shows one debit, the alerts may describe one transaction. If there are two distinct debit entries, that is a different issue to investigate. Neither conclusion should be based only on the number of notifications.
List each financial entry on its own row. Include any later credit separately rather than erasing the debit from your timeline. A matching ₱800 credit may resolve the amount question, but the institution should explain whether it is a reversal, refund or unrelated incoming payment. Identical amounts do not establish a relationship by themselves.
Build a timeline that survives a change of support agent
Use one time zone throughout, retain the original time zone when a record differs, and distinguish the time of the transaction from the time of your screenshot. A delayed notification should not be silently treated as the transaction time.
Give the records short neutral labels, such as A: bank entry, B: destination screen, and C: payment request. In the complaint, explain which two records disagree and the precise clarification needed. This is easier to follow than a collection of cropped screenshots with no sequence.
Share the necessary evidence, not access to the account
Keep complete originals privately and share a redacted working copy through an independently verified secure channel. Retain the amount, date, status and relevant reference where needed. Remove unrelated transactions and identifiers that are unnecessary for that recipient; ask the institution what it needs if uncertain.
If an account-access problem prevents you from seeing records, the login and password-recovery explanation helps separate access errors from payment questions. If someone asks you to install a new file to inspect the payment, review the app-source and device checks before trusting the request. An installation link is not evidence that a support contact is legitimate.
How to organise payment incident evidence
Keep the original files privately. Prepare a separate copy for a complaint, with unrelated transactions and unnecessary identifiers removed. Useful fields include the date and time with time zone, currency, amount, transaction reference, displayed status and the channel through which the instruction arrived.
Fictional example: “At 14:10 Philippine time, my wallet recorded a ₱800 debit under reference EXAMPLE-01. At 14:20, the destination screen still showed no matching credit. At 14:24, a chat account asked for a second ₱800 transfer.” The first two observations describe a discrepancy. The third is a new request to preserve and verify, not proof that paying again will resolve it.
Keep separate copies of the payment record, the message requesting money and any response to your complaint. Do not edit a screenshot in a way that changes its meaning. Add annotations in a separate note.
Protect codes and credentials during support conversations
A one-time password can authorise access or a transaction. It is not a receipt number. Never give a verification code to someone in a call or chat, and do not approve an unexpected authentication prompt to “cancel” a problem.
The US Federal Trade Commission advises checking a suspicious message through a contact channel found independently, rather than using the link or phone number inside it. For a Philippine bank or wallet, use its established app, statement or independently verified website to locate support.
If you disclosed a password or granted remote access, explain that promptly to the affected institution and follow its security-recovery process. Stop sharing your screen while opening financial accounts. Preserve evidence without continuing the suspicious conversation.
Ask the financial institution a precise question
Ask whether the payment is recorded, what its present status means and which reference should be used for investigation. Request a case number and a written explanation of the next step. A practical request is: “Please investigate the debit under this reference and tell me what additional evidence you require through your secure channel.”
For complaints involving BSP-supervised financial institutions, the Bangko Sentral ng Pilipinas directs consumers to contact the institution first. Its Consumer Assistance Mechanism provides an escalation route for unresolved concerns within that scope. It does not establish that a gaming website is supervised by the BSP or promise reimbursement.
Keep a clear record of what remains unresolved
Keep payment incident evidence alongside a short timeline of each contact, case number and promised response date. Mark a case resolved only after checking the actual financial record, not just a reassuring message. Do not publish full account numbers, identity documents or transaction screenshots in a public comment thread. A complaint can explain the problem without exposing the information needed to misuse your account.
