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.
Native Mobile Testing lets you validate your mobile SDK installation. After you integrate the SDK, you can navigate here to extract your testing device’s VID and test the Human Challenge.
From your testing device, navigate to Sightline Cyberfraud Defense > Settings > Mitigation > Challenge Settings.
Select the Testing (Native Mobile) tab.
Select Find your VID.
In the VID extractor window, enter the device’s IP address and select Search. It may take up to 10 minutes for results to appear.
Select your device from the table. Any required parameters will be inserted into their fields automatically.
Mobile emulator-based testing
Some of our detections may block mobile emulator-based solving. If you’re using a mobile emulator, we recommend passing the x-px-captcha-testing header to the request.
If you’re using an Android emulator, we also recommend configuring it to use Charles Proxy.
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.
After you’ve located your device, you’re ready to start testing the Human Challenge.
Select Start testing. This flags all traffic from your device as a possible bot.
Move the app you’re testing on to the background, then to the foreground. This refreshes 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.
Call PXManager.handleResponse to display the Challenge page.
Solve the Challenge to confirm it works. This also clears your VID.
Clear simulation mode
Select the Stop testing button to remove the simulated mode from your device at any time. After you restart your application, all traffic between your device and the server will pass.
