Product Walkthrough & Interactive Demo

Discover how the VMATIC Shield Fraud Prevention Platform protects customers against evolving digital frauds. This guided demonstration showcases SDK integration, secure event transmission, real-time threat detection, and comprehensive diagnostics through the centralized administrative dashboard.

Product walkthrough video

Live Demonstration — Verified Test Results

Real-device test of the Vmatic Shield SDK, verified live on the operations dashboard

Overview

Vmatic Shield is a fraud-prevention security library that embeds inside a banking app and continuously detects device-level threats — sideloaded apps, remote-access tools, and digital-arrest attempts (video-call-driven fraud) — reporting them to a real-time operations dashboard.

The complete flow was exercised on an actual Xiaomi (MIUI) device: app installation, permission setup, on-device scanning, live threat detection during a video call, remote-access tool detection, and a server-triggered remote wake-up and re-scan while the app was closed. Every detection was verified live on the dashboard.

Test Environment

Item	Detail
Test Device	Xiaomi (MIUI) — real device
Partner App	Demo banking application with the Vmatic Shield SDK embedded
Dashboard	Real-time alerts, events and device profiles
Backend / API	Receives events, drives the dashboard, sends wake-up triggers
Test control points	Mobile (partner app, WhatsApp, AnyDesk) · Laptop (server wake trigger + live dashboard)

Test Walkthrough

App installation

The partner banking app (with the Vmatic Shield SDK embedded) was installed on the device.

Launch & permission setup — granted in sequence

On first launch the app requested the required permissions, granted in this order: Allow Notifications → Battery: No restrictions → Allow Usage Access.

These enable background monitoring, on-device confirmations, and detection of which app is currently active.

Initial device scan

A full on-device security scan ran automatically and reported the device's risk profile to the dashboard.

Scan covers sideloaded/unknown-source apps, dangerous permissions, root/ADB/developer options, SIM state and more.

Video call detection (WhatsApp)

A WhatsApp video call was started. The SDK detected the live call and raised a real-time "Video call active on WhatsApp" alert on the dashboard.

Detection is based on real camera + microphone state and the active app — not a guess from screen time.

Banking app used during the video call — digital-arrest signal

While the video call was still active, the partner banking app was opened. The SDK detected this and raised a CRITICAL "Banking app in use during an active video call" alert.

This is the flagship differentiator — it mirrors the exact digital-arrest fraud pattern where a victim is kept on a video call and guided to perform banking actions.

Remote-access tool detection (AnyDesk)

AnyDesk was installed on the device. The SDK detected the remote-access tool and raised an alert for remote-access / screen-guided-fraud risk.

Scammers frequently install AnyDesk/TeamViewer to view or control a victim's screen during fraud.

Server-triggered wake-up & re-scan (app closed)

The app was closed from recents. A wake-up trigger was then sent from the laptop (server). The mobile received the trigger, woke up in the background, re-scanned the device, and reported the results to the dashboard in real time — with a visible on-device confirmation notification.

Delivered via Firebase Cloud Messaging (FCM). This demonstrates event-driven monitoring even when the banking app is not open.

Results

Test	Expected outcome	Result
Initial device scan at launch	Device risk profile reported to dashboard	PASS
WhatsApp video call detection	Real-time video-call alert	PASS
Banking app open during video call	CRITICAL digital-arrest alert	PASS
AnyDesk (remote access) detection	Remote-access alert	PASS
Server wake-up (app closed) & re-scan	Device wakes, re-scans, reports	PASS

Key highlight: The digital-arrest pattern — a video call running while the banking app is used — was detected live and flagged as CRITICAL. This, combined with remote-access detection and the server-triggered wake-up, demonstrates end-to-end protection during the exact moment of a fraud attempt.

Permissions Summary

The permissions below were granted during the test. They are minimal and standard for a banking-security application.

Permission	Why it is needed	Status
Allow Notifications	Required by Android for the background monitoring service, and to show the on-device "security check complete" confirmation.	GRANTED
Battery — No restrictions	Keeps the app reachable in the background so monitoring is not killed by the system. Critical for the wake-up feature — it allows the server to wake the device even when the app is closed.	GRANTED
Usage Access	Lets the SDK see which app is currently active. Needed for the advanced signals: which app a video call is on, whether a remote-access tool is actively running, and whether the banking app is open during a call.	GRANTED
Wake-up (FCM / Firebase)	Enables the server to remotely wake the device and run a fresh scan when the app is not launched. Delivered through Firebase Cloud Messaging. Verified working during this test.	WORKING
Background Autostart	An optional extra layer for edge cases only — a user performing a hard "Force-Stop", or after a device reboot. Not required for the normal closed-app case once Battery optimization is exempted.	NOT TAKEN

On the wake-up feature & Autostart: The remote wake-up was tested with the app closed from recents and worked reliably without Autostart, because the Battery-optimization exemption was granted. Autostart is an optional additional safeguard (recommended during onboarding, as leading payment apps do) for the rare force-stop / reboot cases. It was not taken in this test, and the wake-up still functioned correctly.

Conclusion

The complete detection flow was verified live on a real MIUI device — from installation and permission setup through active threat detection and remote wake-up.
Digital-arrest detection (a video call combined with banking-app usage and remote-access tools) works in real time and is flagged as CRITICAL — the platform's key differentiator.
Server-triggered wake-up is functional: the device can be woken and re-scanned remotely even when the banking app is closed, enabling event-driven monitoring.
The required permissions are minimal and standard for a banking-security app. Background Autostart was not taken, and the wake-up feature still worked reliably.