A better way for cafes and small shops to log GCash, Maya, and bank payments

Short answer: if your shop's current system for a GCash, Maya, Maribank, or bank-transfer payment is a screenshot of the customer's phone, you already have the right habit — capture the payment the moment it happens — pointed at the wrong tool. A camera roll can't total your day, split it by payment method, or find one specific payment two weeks later. A receipt-scanning app can, using the exact same motion you're already doing.

Why the screenshot habit exists

Most small cafes, food stalls, sari-sari stores, and retailers accepting GCash or Maya aren't registered merchants with those apps — that status comes with a real merchant portal that logs every transaction automatically, but it also asks for business registration paperwork most small shops haven't done. Instead, they accept payments on a personal account, usually via a QR code taped to the counter — mobile pay, in effect, but with none of the backend record-keeping a real merchant account would give them.

That means the shop's side of a digital sale generates no record at all on its own. Cash goes in the drawer and gets counted at close; a GCash or Maya payment only leaves a trace on the customer's phone — the "Payment Sent" confirmation screen — so the shop's only copy of that transaction is whatever gets captured in the moment: a photo of the customer's screen, taken specifically so there's something to check against at the end of the day.

It works, in the sense that it's proof the payment happened. It doesn't work as a record you can actually use — those photos pile up in the same camera roll as everything else, with no amount, date, or payment method attached to them beyond what you can see by opening each one, so "does today's sales match" means reopening every screenshot one at a time.

The same habit, filed automatically instead

The fix isn't a new habit — it's the same one-photo moment, aimed at Resiboo instead of the camera app. Snap the confirmation screen the instant the customer shows it to you, the same way you'd already photograph it. From there, three things make it useful:

Category: what was sold, not who paid

Set up categories the way any category system should work for you — around the question you'll actually ask later. For a shop, that's usually "what part of the menu or the store made this sale": Food, Drinks, Retail, or whatever split matches how you think about your own business. Resiboo's categories are fully yours to rename and add to, so the default personal-finance set (groceries, dining, transport) is just a starting point to replace with your own.

Tags: which payment method

Categories answer what; tags answer a second, independent question — in this case, how the customer paid. Add a tag for each channel you accept — gcash, maya, maribank, bank-transfer — and apply it to every scan alongside its category. Because tags are free text and many-to-many, this costs nothing extra: a drink sold and paid via GCash is Category: Drinks, Tag: gcash, and it's filterable by either one independently. That split is exactly what a screenshot pile can't give you — "how much came in through GCash today" is a five-second filter, not a manual recount.

The total: read off the confirmation screen

The same on-device extraction that reads a paper receipt's total reads the amount off a payment confirmation screen just as well — it's text on a screen either way. The field that behaves differently is merchant: on a GCash or Maya screen, that's the payer's name or number, not a business you'd normally search for, so don't worry about getting it "right." What matters for a sales record is the amount, the date and time, the category, and the payment-method tag — correct those four once per scan and you're done.

What end of day looks like

Once a day's payments are captured this way, closing out stops being a manual tally:

• Stats gives you the day's total instantly, plus a breakdown by category — how much was food versus drinks versus retail — the same view any Resiboo user gets for their own spending, just pointed at your shop's sales instead.
• Filter by tag to see the split across GCash, Maya, Maribank, and bank transfer specifically — useful both for your own sense of which channel customers actually use, and as a sanity check against the personal account's own transaction history in each app, the same way you'd count cash against what the drawer should hold.
• Export a CSV at close — see exporting to a spreadsheet for shaping the columns — for a daily or weekly sales log you can hand to whoever does your books, without retyping a single screenshot.

A few things worth setting up once

• Use one device for this. Resiboo stores everything locally on the phone that scanned it, so a shared counter phone (or one staff member's phone at close) keeps a shift's payments in a single place instead of scattered across whoever happened to take the photo.
• Back it up. A counter phone gets dropped, replaced, or handed to a new hire eventually — see backing up your receipts so a phone swap doesn't cost you the day's, or the month's, records.
• Watch for accidental double-scans. Busy hours mean retaking a blurry photo sometimes — Resiboo flags a same-day, same-amount repeat automatically, the same way it would for any duplicate receipt, so a retake doesn't quietly double your reported sales for the day.

What this isn't

Resiboo isn't a point-of-sale system — there's no inventory, no itemized customer-facing invoice, no integration with GCash's or Maya's own settlement APIs. What it replaces specifically is the gap between "I took a screenshot" and "I have a usable record" — the same gap a paper receipt drawer has, solved the same way: capture the moment it happens, and let category, tags, and export turn that pile into a report automatically instead of by hand at the end of the night.

Resiboo reads the amount and date off any payment confirmation screen the moment you scan it, and lets you categorize and tag it by payment method so closing out the day is a Stats screen, not a scroll through a camera roll.