Skip to content

← Writing

engineering

E-Wallets Go Mainstream: The GCash Leap

· Jerwin Arnado

Archive note: this is a backdated post, written years later while rebuilding this site. It’s dated to the moment it covers, but the hindsight is real.

For years, fintech in the Philippines had the same problem: everyone downloaded the apps, almost nobody used them. Cash was king, padala culture ran on remittance counters, and “may GCash ka ba?” was a niche question.

Then the lockdown closed the counters, made handing over cash feel risky, and compressed years of behavior change into a few months. GCash and PayMaya registrations and transaction volumes exploded this year. The sari-sari store nearby now has a GCash number taped to the window, right next to the load signage. That’s adoption no marketing budget could buy.

Why it stuck this time

E-wallet tech barely changed between 2019 and 2020. What changed is that the alternative broke:

  • Remittances had to move without travel and queues. Wallet-to-wallet transfer replaced the padala trip.
  • Government aid and payrolls started flowing through digital channels, onboarding people who’d never used a bank.
  • InstaPay and PESONet quietly mattered most. Interoperable bank-to-wallet rails meant money could move between institutions, not just inside one app’s bubble. Closed ecosystems don’t tip; networks do.
  • QR codes gave small vendors a payment terminal that costs nothing: a printout.

The developer angle

This shift lands directly on those of us building for PH businesses. Things I’m noting from integration work and from watching the ecosystem:

  1. “Cash on delivery” is no longer the only honest default. E-commerce checkouts targeting PH customers now genuinely need e-wallet options, not as an afterthought but as the primary path. Payment gateway choice has become an architecture decision worth real evaluation time.
  2. Webhooks over polling, and trust nothing. Payment confirmation flows are where the money is, literally. Verify signatures, handle duplicate notifications idempotently, log everything. A double-credited wallet top-up is not a bug ticket, it’s an incident.
  3. Design for intermittent connectivity. A payment that times out mid-transaction on a prepaid data connection must resolve to a clear state. “Pending” screens with honest messaging beat optimistic UI that lies.
  4. The unbanked are now your users. Many first-time e-wallet users this year have never had a bank account. Familiar UX assumptions — that users know what a “reference number” is for, that they’ll screenshot receipts — need rechecking against reality.

The bigger picture

The BSP has been pushing toward a cash-lite economy for years; 2020 dragged the timeline forward by force. Habits formed under necessity have a way of surviving the emergency that created them — nobody who’s experienced paying bills from a phone at midnight is going back to queueing at a bayad center.

For PH developers, payments just became the most interesting layer of the stack. The rails are finally carrying real traffic. Time to build things worthy of it.