Req 2.16: Allow blocking of in-app purchases or other non-au...

⚙️ Technical Demonstration

IMTLazarus completely satisfies this requirement by integrating application-layer restriction frameworks that mitigate the risk of unauthorized commercial activity on DepEd endpoints. The platform prevents unapproved transactional features, paid add-ons, or in-app purchases by completely cutting off access to the underlying software marketplaces and installation vectors that drive microtransactions:

Window-Title Transaction Blocking: The platform monitors window processes in real time to catch web-based payments or standalone billing interfaces. If a transaction screen, unauthorized app page, or payment engine matching an unallowed phrase list tries to run, the system immediately kills the corresponding window process.

Centralized Application Store Lockouts: In-app purchases rely heavily on native platform marketplaces to authorize payment streams and process credit cards. As demonstrated in 2.16-1.png, the system allows administrators to activate an absolute Microsoft Store Block at the profile level. This control completely restricts user access to the desktop marketplace, blocking the download of paid software, games, and premium microtransaction modules.

Proactive Executable Blocklists: To stop students from bypassing app stores using standalone transactional frameworks or portable payment apps, administrators can target specific system extensions and unapproved binaries. Running local restrictions blocks independent transaction hubs, preventing background billing loops from executing.