Where Do You Find the Official Trace Number Inside Each Philippine App?
Payment gateways reconcile delayed deposits using the exact Reference/Instruction ID generated by GCash, Maya, or BancNet: never an SMS balance preview or cropped crop-out!
During nationwide cellular or payday congestion, 1 in 200 instant webhooks arrives late even though your wallet succeeded. Locate the exact trace identifier inside your app before contacting live chat:
| Wallet / Banking App | Where to Tap Inside App | Exact Reference Format | What Must Show in Screenshot |
|---|---|---|---|
| GCash | Transactions / Inbox > Tap specific Express/QRPh receipt | 13-digit numeric Ref. No. (e.g. 9018XXXXXXXXX) | Amount, Date/Time, Merchant & full 13-digit Ref No. |
| Maya Wallet | Transactions > Tap completed QRPh/Payment item | 12-char alphanumeric Reference ID | Completed green badge, PHP amount & Reference ID |
| BDO / BPI / UnionBank | Transaction History / Email InstaPay Advice | BancNet / Bank Instruction Ref No. | Source last-4 digits, exact timestamp, PHP amount & Ref ID |
| USDT (TRC-20 VIP) | Wallet Send Log > Copy Transaction Hash | 64-char hexadecimal TxID | Plain-text copy of 64-char TxID (verifiable on Tronscan) |
What Three Mistakes Slow Down Manual Deposit Reconciliation?
Sending a second duplicate payment, typing a single wrong digit in the 13-digit Ref No., or cropping the timestamp out of your screenshot slows ticket resolution. Copy-paste the reference string in plain text AND attach the full receipt!
Remember the cardinal security boundary: sharing a **completed 13-digit Reference Number** inside the official HTTPS live chat is 100% safe (it is just a receipt number), whereas nobody legitimate will EVER ask for a **6-digit SMS OTP** or **4-digit MPIN**! Pair receipt habits with clean support ticket logs and fresh QRPh generation.
Sample Clean Escalation Message Format for Delayed Payday Deposits
Instead of sending ten separate "hello??" messages that bump your ticket down the support queue, send one single concise message inside official live chat: state your +63 account ID, exact PHP deposit amount, payment channel (GCash QRPh), exact time paid, paste the 13-digit Reference Number as plain text, and attach one uncropped receipt screenshot. Treasury bots and agents match single-message tickets in minutes.
Related Deposit & Troubleshooting Guides
Explore companion GCash, Maya, BDO/BPI, and support-log guides:
Vertical Silo • /payments/
Related Topic • /payments/gcash-deposit/
Related Topic • /payments/gcash-withdrawal/
Related Topic • /payments/maya-payouts/
PHP Cashier • Instant QRPh
BOFU Access • +63 OTP
Frequently Asked Questions
Is it safe to give official live chat my 13-digit GCash Reference Number?
Yes! A completed 13-digit Reference Number only proves a past transaction occurred so treasury can match the webhook; never share 6-digit OTPs or MPINs.
How long should I wait before submitting a Reference Number check?
Wait 5 full minutes first and refresh your lobby balance once: over 85% of delayed payday webhooks auto-credit within 180 seconds on their own.
Why did support reject an edited or drawn-on screenshot?
Anti-fraud systems automatically flag cropped, blurred, or sticker-covered receipts because Photoshopped deposit slips are a common fraud attempt; send the clean raw receipt.
What if GCash deducted my money and refunded it 10 minutes later?
Occasionally a timed-out QRPh leg auto-reverses inside GCash; check your GCash Transaction History for an automatic reversal credit before opening a ticket.
Can I paste the 13-digit number as text as well as uploading the image?
Yes! Pasting the exact 13 digits as plain text lets the support agent query the payment gateway database in two seconds.