For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
Product GuidesEnforcer GuidesMobile SDKAPI ReferenceCustomer support
  • Getting Started
    • Overview
    • Best practices
  • Sightline Cyberfraud Defense
    • About Sightline Cyberfraud Defense
    • Getting Started
    • What's different in Sightline Cyberfraud Defense
    • Sensor changelog
    • About the Overview Dashboard
    • Glossary
  • AgenticTrust
    • Getting started with AgenticTrust
    • AI Agents Monitoring Dashboard
    • AI Visitors Overview Dashboard
    • Manage AI Agent Permissions
    • Agentic Activity Priority
    • Agent Trust Levels
  • Account Defender
    • Account Defender Overview
    • Use Cases
    • Prerequisites
    • Getting Started with Account Defender
    • Optimizing Account Defender Detection
    • Validating Account Defender Integration
    • Risk Triggers
    • About Network Events
    • Troubleshooting
  • Bot Defender
    • Bot Defender Overview
    • Detection
    • Bot Defender Policy Settings
      • Human Challenge - Integration Testing Process
      • Mobile Enforcement Verification
    • Footprint
  • Credential Intelligence
    • Credential Intelligence Overview
    • How to Access the Breached Flag
    • Credential Intelligence FAQ
    • Credential Intelligence Dashboard
  • Code Defender
    • Code Defender Introduction
    • Getting Started with Code Defender
    • Code Defender Glossary
    • Website Risk Analyzer
  • Platform
    • Account settings
    • Manage users
    • Role permissions
    • Enforcer configurations
    • Page Type Mapping
  • Client-Side Integration
    • JavaScript tag
    • Improving first page performance
    • Use of cookies & web storage
    • Advanced client integration
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • Using the Testing (Native Mobile) tab
  • Extracting Visitor ID (VID)
  • Simulating the Captcha Response
  • Clear
Bot DefenderValidating Integration

Mobile Enforcement Verification

Was this page helpful?
Previous

Footprint

Next
Built with

Using the Testing (Native Mobile) tab

The Testing (Native Mobile) tab (Product Settings -> Challenge Settings -> Testing (Native Mobile) allows you to verify that your installed SDK is running correctly and monitoring and blocking traffic as intended.
Users with Admin, Developer and Dev Tools credentials have access to the Testing (Native Mobile).
Enforcement verification is applicable to both Android and iOS

Extracting Visitor ID (VID)

HUMAN servers assign a unique visitor ID (VID) to every user. In order to use the verification tool, you need to extract the VID assigned to the device being used for testing.

  1. Access the application being tested with the device.
  2. Click Find your VID to open the VID Extractor window.
  3. Enter the device IP address and click Search
    • Note: This may take a few minutes*
  4. Locate your device based on the device, app and carrier attributes listed in the table, and click Select. The required parameters are automatically inserted in the relevant fields.

Simulating the Captcha Response

To verify that the app is blocking correctly:

  1. Click the Start testing button to flag all traffic from your device as a possible bot.
  2. Move the app to the background and then to the foreground to refresh the SDK token. The first request sent to your mobile app’s server will receive a 403 response with a Captcha challenge in the response body.
  3. By calling PXManager.handleResponse a Captcha page is displayed.
  4. To clear your VID, you can either solve the Captcha, or click the Stop testing button.
When testing with a mobile emulator

As some of our detections may block mobile emulator based solving, make sure to pass the x-px-captcha-testing header to the request. You can find our testing recommendations here.

Configuring an Android Emulator to use Charles Proxy

To configure your Android Emulator:

  1. Set the HTTP proxy settings in the Wi-Fi menu.
  2. In the Wi-Fi menu long press the connected network, select Modify Network, and fill in the proxy settings. If you are running Charles Proxy on your local machine then use the local IP (not the loopback).
  3. To intercept HTTPS requests follow the guidelines at:

https://www.charlesproxy.com/documentation/using-charles/ssl-certificates/..

In Android Nougat special permissions are required to use a certificate added to the trust store.

Clear

Click the Stop Testing button at any point to remove the simulated mode assigned to your device. After restarting your application all traffic between your device and the server should pass.