Copy the reference from the signed-in wallet or transaction screen. Match it to the PHP amount and time. Then record what the destination account shows. Hide unrelated balances, names and transactions before sharing evidence.
Where to find the useful number
Open the completed or pending transaction inside the app that sent the money. Look for a field labelled reference, transaction ID, order ID or receipt number. A screenshot notification can be helpful, but the signed-in history is the better record.
Build a four-line timeline
- Action: payment, cash-in or withdrawal request.
- Wallet side: amount, exact time, current status and reference.
- Platform side: matching transaction entry or "no entry found."
- Current problem: pending, reversed, completed but not reflected, or wrong destination.
Crop screenshots safely
- Keep the relevant reference, amount, time and status visible.
- Hide unrelated transactions and balances.
- Hide full phone numbers, email addresses and document numbers where not needed.
- Never include an OTP, MPIN, password, recovery code or QR that can authorize access.
Do not mix different identifiers
A wallet reference and a platform order number can be different. Save both and label which system produced each one. Do not rename them or assume one should replace the other.
Follow up without creating duplicates
Reply on the same support ticket and quote the same transaction reference. Opening many tickets can split the evidence across agents. If the status changes, add the new time and state rather than repeating the original story.
Choose the matching checklist
Use the GCash pending guide, Maya pending guide or withdrawal account guide for the next step.
Why this matters
Official GCash and Maya support routes both begin with the actual transaction record. PinoyDesk keeps this guide provider-neutral so it remains useful when field names change.