Which PAGCOR-licensed Philippine casinos actually publish their GCash limits?

GCash's own help centre publishes one ceiling, and it is a wallet limit, not a casino one

PAGCOR's own accreditation register lists four platforms this database tracks under its domestic PIGO licence class, and every one of them shows a GCash icon on its deposit page. None of the four answered a plain fetch attempted for this piece: one blocked the request outright, one geofenced by name, one served an empty page built for a browser rather than a reader, and one never answered at all.

This record cannot currently confirm what any of the four charges or caps on a GCash transaction, because none of their own payment pages loaded. What changed here is smaller than that. A year ago, funding one of these sites through GCash meant tapping an icon inside the GCash app. Since August 2025 it has meant opening the casino's own site directly, and that direct step is exactly what failed four times over.

GCash's own help centre states that a fully verified account can move up to PHP 100,000 within its own wallet and transaction limits. That figure describes the wallet as a whole, not any single merchant, and GCash names no casino inside it. A basic, unverified account sits well below that ceiling and cannot use Express Send to another user at all.

So the one number that is publicly stated and dated belongs to GCash, not to any of the four operators. Whether a casino adds its own lower ceiling on top of it is a question none of their own sites answered this month.

Four PAGCOR-licensed platforms carry the icon. Reading each one directly produced four outcomes

Each of the four brands below sits on PAGCOR's own gaming-system-administrator register, and each record in this database carries that register's own URL and a verification date in August 2026. Reading past the licence, at the site itself, went four separate ways.

747's own domain did not answer at all. The request timed out before any server replied. Nobody said no. The connection simply never completed.

BingoPlus returned an HTTP 403 with a bare message reading only "restrict access." It says nothing else. No reason is stated on the page, and no geography is named.

Ninogaming also returned a 403, but its own page explains why in plain English: the site can only be accessed from a Philippine IP address, and it adds, unprompted, that its games are for players 21 and older.

OKBet answered with a normal HTTP 200 and almost nothing else: 55 characters of text inside 7,300 bytes of markup, an empty shell built for a browser to fill in with JavaScript after it loads. A plain fetch cannot see what that shell would have shown.

One of those four outcomes is an explicit geofence. The other three are not

The obvious objection to calling this an access gap is that a PIGO-licensed site is required to geofence non-Philippine visitors, so a blocked page is proof the licence is real rather than evidence anyone is hiding a payments page. That objection is fair. It fits exactly one of the four outcomes above: Ninogaming's own message names the Philippines and nothing else.

It does not fit the other three. Nothing in BingoPlus's bare 403 names a country, a licence or a reason. An empty JavaScript shell like OKBet's serves the same near-blank markup to a visitor in Manila and a visitor anywhere else; a geofence check runs on the server, and a shell that renders nothing has usually not run one at all. A connection that times out, as 747's did, never reached a server to ask it anything, geofence or otherwise.

So the geofencing defence explains a quarter of what happened here. It does not explain the rest, and treating all four as the same kind of block would be the more comfortable story, not the more accurate one.

The shortcut that used to connect GCash to these sites was cut about a year ago

On 15 August 2025, the Philippine Star reported that the Bangko Sentral ng Pilipinas had ordered e-wallet platforms to remove in-app links to online gambling sites within 48 hours. BSP Deputy Governor Mamerto Tangonan confirmed the order at a Senate inquiry the day before, telling senators the window was meant to let banks delete the icons and to give users time to withdraw funds already sitting inside a gaming account linked to their wallet.

GCash's own GLife feature, and Maya's equivalent Games feature, stopped offering that in-app route at 8pm on 16 August 2025. Before that evening, tapping a casino's icon inside the GCash app opened it directly. Since then, a player has had to leave the wallet app and open the casino's own site or app instead: the exact step that produced four different failures for this piece.

None of the four sites this database tracks mentions the order on any page this run could read, though three of those four pages could not be read at all. Whether any of them changed a payments page, a terms page or a support article as a result of the BSP's directive is not something a blocked or empty page can answer.

What is actually left for a reader to check

Two things are checkable without needing any of the four operators' sites to load. GCash's own limits sit inside the app itself: Profile, then Wallet and Transaction Limits, updated live rather than on a help page that can go stale. PAGCOR's own accreditation register is a second, independent check, and it names the file, the page and the date rather than a badge on a landing page.

What is not checkable from outside is the part a reader most wants: whether any of these four platforms sets its own GCash ceiling below GCash's PHP 100,000, and what it charges, if anything, to move money either way. Three of the four pages that might answer that would not load this month, and the fourth loaded nothing a plain reader could use. That gap is stated here rather than filled with GCash's own wallet figure standing in for an answer none of the four operators has actually given.

PAGCOR reissues its own accreditation files whenever it accredits a new administrator or updates an existing one, which means the register this piece cites will not stay identical for long. The open question is which of these four sites is the first to answer a plain read with an actual payments page. As of this run, none of them is.