Oz Demo Kit
How to work with Oz Forensics applications for iOS and Android.
Last updated
Was this helpful?
How to work with Oz Forensics applications for iOS and Android.
Last updated
Was this helpful?
To test Oz Forensics Mobile SDK, use this demo kit. With it, you can check how accurate it is in case of face recognizing and liveness detection. Contact us to get your credentials and let’s begin.
To start working with Oz Forensics application, download it for your OS. The application is available for iOS and Android.
For iOS, you’ll need the TestFlight application. Download it from App Store: . When download completes, get Oz Forensics iOS demo application here: . Tap the Oz Liveness icon.
Upon the first login, you’ll be prompted to enter the credentials you’ve received from us. Check the API Address field – it should contain the following record: “https://sandbox.ohio.ozforensics.com/”. Once entered, tap the LOGIN button. You’ll be redirected to the Scenarios screen.
For Android, download the latest version of the application here: . Make sure you don’t have the previous version installed. You also might need to enable installation of apps from unknown sources. Once downloaded, tap the package to process it and complete the installation. Launch the app and you’ll see the Scenarios screen.
Tap the Profile icon in the top-right corner. In the new screen, enter your credentials. Check the API Address field – it should contain the following record: “https://api.sandbox.ohio.ozforensics.com”. After you log in, you’ll get back to the Scenarios screen.
For both systems, if you entered wrong credentials and need to change the user, hit the Profile icon on the top right. You’ll see your username and API server address. Tap Change User (iOS) / LOGOUT (Android) and repeat the login process with the correct credentials.
In your profile, you also can:
Switch to another documents check method
Choose between server-based and on-device analyzes (below, we’ll describe the difference)
Check the current version of the application and SDK
Within the app, you can follow one of the three scenarios.
Biometric check: a client makes a selfie, and the system compares their selfie with images from a database. This scenario is for transaction confirmations, self check-ins, access management, etc.
Liveness: a client takes a short selfie video to confirm they are a living person acting in good faith. This is a spoofing-protection scenario.
Below, we’ll explain how to manage each of the scenarios.
Please note: for testing purposes, you choose a photo to compare selfie with from your phone library or take it with your camera. Later on, at the production stage, you’ll be able to create either blacklist or whitelist which will be used as a database.
In the Biometric check section, tap Select Photo to specify an image for comparison. You can either take a photo or select it from your gallery. Confirm the choice. The photo will appear on your screen. Tap Do Check and follow the instructions.
If the faces match, you’ll get the “Authentication successful” message. If they don’t match, the warning message will appear.
In the Liveness section, you need to pick one of the gestures that will be used to confirm that you’re a real living person. They are:
One shot
Selfie
Scan
Blink
Smile
Tilt up
Slope down
Turn your head left
Turn your head right
Combo – a combination of several gestures from above
If the Liveness check is successful, you’ll get the “Authentication successful” message. If not, the warning message will appear.
*There is also a way to perform analyzes locally on your device. To enable this option, proceed to the Profile and change the Analysis type in the Settings section from Server based to On device. In this case, all checks will be performed on your device, no data is sent to the server. This is a faster and safer way of analyzing. However, the server check is more accurate and the information is stored for further needs.
Should you have any questions, please contact us.
All photos and videos you take can be found in the Web console*. You can find documentation on the console usage here: .