Grab the Amount, Reference Number, and Recipient from a Maya Screenshot
Manually transcribing a Maya confirmation takes 2 minutes per screenshot — this pulls the amount, reference number, recipient, and date in 5 seconds. No matter which of Maya's three products (Wallet, Savings, Credit) generated it.
5-10s per screenshot · Up to 99% accuracy on printed text
What You Can Pull from a Maya Screenshot
Every Maya confirmation screen carries the same four core fields, whether the transaction came from your Wallet, Savings, or Credit account. With Custom Column Extraction, define the columns you need — the AI locates each value by understanding what the field means, not where it sits in the layout.
| Amount | Reference No. | Recipient / Store | Date | Status |
|---|---|---|---|---|
| ₱1,500.00 | MRCJ20240714123 | Maria S. / SM Store | Jul 14, 2026 | Successful |
Three Products, One Reference Number — Across Dozens of Layouts
Maya is not a single product — it's three (Wallet, Savings, Credit), each with its own confirmation screen design. On top of that, Send Money, Pay QR, and Bills Payment each render differently. Template-based tools need separate configurations for every combination — which defeats the purpose when you're processing transactions from a single account.
Three Products, Three Visual Languages
A Maya Wallet transfer confirmation, a Maya Savings deposit receipt, and a Maya Credit usage acknowledgement share zero visual DNA. The first uses a mobile-number-based layout, the second a bank-statement-style card, the third a loan-agreement summary. One developer on Reddit noted that "OCR screenshots — too easy to fake" was their failed attempt at solving this.
No CSV Export for Individual Users
Maya's CSV transaction export is available only to business account holders. Individual users — freelancers, sari-sari store owners, online sellers — have no option but to screenshot every confirmation. As one Reddit user put it, the alternative is "manual verification — literally why" after their VA quit over the workload.
GCash + Maya: The Dual-App Reality
Most Filipinos use both GCash and Maya — one for social payments, the other for banking and savings. Reconciliation means pulling data from two completely different app ecosystems. Sellers accepting payments through both platforms need a single unified view of their daily transactions.
Semantic Reading Spans All Products
Define Reference Number once — the AI locates it on Wallet transfers, Savings receipts, and Credit confirmations alike, because it reads the label text, not the pixel coordinate. No per-product, per-type configuration needed.
Batch Processing Fills the Export Gap
Upload 50 Maya screenshots across all transaction types at once. The AI processes every layout variant with a single column definition, and the output lands as one unified Excel sheet — rows sorted, types classified, amounts summed.
Cross-Platform with a Shared Column Set
Because Maya and GCash serve the same fields — Amount, Reference Number, Recipient/Sender, Date — the same column definitions work for both. Add an inferred Source (Maya / GCash) column and the AI classifies each row automatically, giving you a single consolidated sheet from both apps.
From Mixed Maya Screenshots to a Single Spreadsheet
If you're reconciling a day's worth of Maya payments — QR sales mixed with bank transfers, bill payments, and a Maya Credit purchase — here's how they all end up in one table, no per-type sorting required.
Upload the Mixed Batch
Drop any combination of Maya confirmation screenshots — Send Money transfers, Pay QR receipts, Bills Payment acknowledgments, Maya Credit usage confirmations — into a single upload. The tool doesn't need them sorted by type because the AI reads content, not layout.
Name the Columns
Define four column headers: Amount, Reference Number, Recipient / Store, and Date. Add an inferred Transaction Type (Send Money / Pay QR / Bills Payment / Maya Credit) and a Source (Maya / GCash) column if you're mixing both apps. One set of definitions covers every layout.
Export the Consolidated Table
The output lands as a single spreadsheet — one row per screenshot, five columns, every transaction type and product consolidated. Export to Excel, CSV, or push directly into Google Sheets via the add-on. No more flipping between screenshots or manually transcribing reference numbers into a logbook.
When Maya Screenshot Extraction Works Best — and When It Doesn't
When It Works Best
Clear screenshots from the Maya app. Direct confirmations from Send Money, Pay QR, Bills Payment, and Maya Credit screens where text contrast is stable and the reference number is clearly visible alongside the amount and recipient.
Mixed-product batch processing. One column definition handles Wallet transfers, Savings receipts, and Credit confirmations in the same upload — no per-product sorting required.
Daily reconciliation at volume. Processing 20-50 Maya payments per day replaces manual screenshot-by-screenshot transcription with a single export.
When to Be Cautious
Cropped or forwarded screenshots. Messaging apps compress Maya receipt screenshots and may crop the reference number or status area. When possible, capture from the Maya app directly rather than forwarding from a chat.
Pre-rebrand PayMaya screenshots. Old PayMaya-branded screenshots (pre-2022) use a different layout and color scheme. Semantic extraction still reads labels, so accuracy holds — but verify the first few rows when processing legacy screenshots.
Pending transaction screens. A transaction still showing "Processing" may lack finalized field values. Wait for the confirmed status screen before extracting to ensure the reference number and amount are final.
Frequently Asked Questions
Can I extract the reference number from Maya Wallet, Maya Savings, and Maya Credit screenshots?
Yes. The Reference Number is the one identifier that appears on every Maya confirmation screen — Wallet transfers, Savings withdrawals, and Credit usage confirmations all display it. Define a column named Reference Number or Ref No. and the AI locates it by reading the label, not the position, so format variations between products don't affect accuracy.
Why does the "Recipient" field show a person's name on one screenshot and a store name on another?
Maya handles two distinct scenarios. Send Money transfers between users show the recipient's Maya-registered name. Pay QR payments to merchants display the store or business name in the same position. Define a single column as Recipient / Store — the AI returns whatever identifier is visible. Adding the inferred Transaction Type column clarifies which scenario each row belongs to.
How does Maya screenshot extraction differ from GCash?
The fields are nearly identical — Amount, Reference Number, Recipient/Sender, Date — which means the same column definitions work for both apps. The difference is that Maya has three internal products (Wallet, Savings, Credit) with different confirmation screen designs, while GCash has four transaction types with different layouts. Both are handled by the same semantic extraction approach. See the GCash screenshot page for the sibling guide.
Will it work with old PayMaya-branded screenshots?
Yes, but verify the first few rows. Before Maya's 2022 rebrand, PayMaya confirmation screens used a different visual design — different color palette and element positioning. The AI reads semantic labels, so core fields like Amount and Reference Number are still identified correctly, but the field name labels may appear in slightly different positions relative to the values.
Can I batch Maya and GCash screenshots together in a single export?
Yes. Define a unified column set — Amount, Reference Number, Recipient / Sender, Date — and the same definitions apply to both Maya and GCash screenshots in a single batch. Each screenshot becomes one row regardless of which app generated it. Add an inferred Source (Maya / GCash) column to keep track. See the payment screenshots hub for the full list of supported apps.
Sibling comparison: how GCash handles the same multi-layout payment challenge with four transaction types: GCash screenshot extraction
Sibling comparison: bKash (Bangladesh) — another Asian mobile payment system with a similar confirmation screen pattern: bKash screenshot extraction
Back to payment screenshots overview — see all supported payment apps