PAGCOR plans licensed-platform verification app before year-end

A proposal at a budget hearing

The Philippine Amusement and Gaming Corporation said chair and chief executive Alejandro H. Tengco presented an app plan at a House appropriations hearing on 24 August 2026. PAGCOR posted its announcement on 25 August, and GMA News independently reported the announcement that day.[1][2]

PAGCOR said the proposed tool would help online players use authorized and regulated platforms, with launch planned before the end of 2026. That is the regulator’s stated purpose and target window, not confirmation that a product has been delivered or that its effectiveness has been demonstrated.[1][2]

GMA News states that its report is based on PAGCOR’s news release; it does not describe a reporter seeing the app in operation. The two accounts corroborate that a plan was announced. Repeating the same announcement is not an independent test of the app’s functions.[1][2]

The announcement did not provide an app-store listing, download link, version number or public testing route. The accurate status is “PAGCOR plans to launch,” not “the PAGCOR app is available to players.” A later official listing or service notice would be needed to update that status.[1][2]

Stated purpose and existing facility

PAGCOR described two aims: curb illegal online gambling and help players identify platforms licensed and regulated by the agency. Tengco said licensed play provides a process for seeking redress in a dispute. This is the regulator’s description of the existing framework.[1][2]

The regulator said the plan builds on its PAGCOR Guarantee web facility, launched in 2025 to let the public check whether an online gaming provider is licensed. The announcement did not explain how the app relates to that site, whether they will share a list, or whether offline checks will be possible.[1][2]

PAGCOR also cited work with the Department of Information and Communications Technology, the National Telecommunications Commission and the Cybercrime Investigation and Coordination Center against illegal operators and their payment channels. It did not say that the app itself would block sites or payments, so enforcement cooperation should not be conflated with app functionality.[1][2]

The agency links licensed platforms with a route for consumer disputes, but the announcement gives no response times, eligibility rules, complaint steps or outcome data. Readers should distinguish having a process through which to seek redress from a guarantee that a dispute will be resolved.[1][2]

The “around 50%” figure is attributed

Tengco estimated that around 50% of online gaming sites accessed in the Philippines were illegal. PAGCOR and GMA News both attribute the figure to him. The announcement provides no sample, sampling frame, site count or estimation method, so this is not a statistic we can independently reproduce.[1][2]

This report therefore attributes the statement as an estimate by PAGCOR’s chair rather than saying half of all sites are proven illegal. Accessible sites, a license list and a regulator’s legal determinations may use different definitions. Without published methods and data, the claim cannot be recast as an independently verified finding.[1][2]

GMA News explicitly sources the 50% figure to PAGCOR’s release and does not offer a separate estimate. That is an important verification distinction: the report confirms that the regulator made the statement, but supplies no second dataset validating the percentage itself.[1][2]

The claim that the app will help players identify legal platforms is likewise a policy aim, not a measured result. Evaluating impact after launch would require evidence such as list coverage, update frequency, correction procedures, usage data and an independent assessment. None of those measures appeared in the announcement.[1][2]

Product and data questions remain

Neither account explains how the app will identify an authorized platform: by searching an official register, scanning a URL, matching domains, requiring login or using another method. Different mechanisms bring different update and error risks. The product design should not be filled in with speculation.[1][2]

PAGCOR has not specified distribution on iOS or Android, price, supported languages, accessibility features or minimum device requirements. These details affect practical access. The word “app” does not establish that native versions for both platforms exist or that either has cleared a store review.[1][2]

The announcement does not say what device or usage data might be collected, whether an account is required, how long records would be retained, or how users could request correction or deletion. Readers cannot assess privacy impact from the current information. A privacy notice, terms and data-governance documents would be needed.[1][2]

“Before the end of the year” is a target window, not a firm date or milestone schedule. Government projects can change during procurement, development or approval. Until a later official notice appears, coverage should preserve the word “planned” and distinguish a target from a launch.[1][2]

What to verify next

The first verifiable milestone would be an official product page, version number or download link published by PAGCOR. The page should establish who operates the service and confirm its domain; a social post or third-party listing alone would not establish an official launch. The current primary source is still the plan announcement.[1][2]

If the product launches, follow-up reporting should check where its list comes from, how often it changes and what happens when a platform name does not match a domain. Testing should cover brands and URLs under one operator and identify a correction route for errors.[1][2]

A follow-up can compare app results with the existing PAGCOR Guarantee page, recording agreement, discrepancies, update times and reporting options. Such checks assess whether the tool works as presented; they do not establish broader protection outcomes, which require longer-term data and a defined evaluation design.[1][2]

Checked on 14 October 2026, both sources describe a planned release rather than a publicly downloadable product. If PAGCOR later confirms a launch, delay or material change, this report should be substantively revised against a new primary notice and independent coverage, with the revision date recorded.[1][2]

The next verifiable record

If PAGCOR announces an app launch, the next check should locate an official product page, an identifiable publisher and a direct download link, then confirm the date, version and territory. The article status should move from planned to launched only when an official channel connects the service to its publisher.[1][2]

A store listing and a functioning verification list are different things. Follow-up reporting should check how the official list is updated, how similar brand names are distinguished, how stale URLs are handled and whether users can report errors. A download page alone would not establish that verification works.[1][2]

If PAGCOR changes the year-end target, keep the original announcement date and report the new timetable, distinguishing a delay, staged test or change in scope. A revised target can itself be news, but an early estimate cannot tell readers when a usable service will actually be available.[1][2]

Independent coverage that only repeats a new PAGCOR statement can verify that the regulator made another claim; it cannot by itself prove that the app operates. Look for hands-on testing, a verifiable list or another independent record, and describe separately what each type of evidence supports.[1][2]

This report keeps the official estimate, policy aim and unpublished product specifications separate. If a new document adds methods, data handling or test results, identify which open question it answers, add it to the relevant section and record the new verification date.[1][2]