This is the last version that supports Android 4.x and 5.0. The minimum supported Android version will be increased to 5.1 (API level 22) in the next SDK version 3.6.0.
- New Singapore datacenter compatibility [Netverify/Fastfill, Authentication, Document Verification, BAM Checkout]
- Support for dynamic library modules to reduce the initial download size of the app [Netverify/Fastfill, Authentication, Document Verification, BAM Checkout]
- Advanced document checks on the back of IDs to increase user conversion - for paper documents [Netverify]
- Aligned confirmation view design with Netverify [Document Verification]
- Added fallback handling for device cameras without auto-focus [Netverify/Fastfill]
- Fixed handling of credit card masking [BAM checkout]
- Fixed problems with Belgium ID card backside scanning [Netverify/Fastfill]
- Various smaller bug fixes/improvements [Netverify/Fastfill, Authentication, Document Verification]
The requirements for the SDK are:
- Android 4.4 (API level 19) or higher
- ARMv7 processor with Neon, ARM64-v8a
- Internet connection
Required permissions are linked automatically by the SDK.
The following permissions are optional:
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-feature android:name="android.hardware.camera" android:required="false"/>
Note: On devices running Android Marshmallow (6.0) and above, you need to acquire android.permissions.CAMERA dynamically before initializing the SDK.
Use getRequiredPermissions to get a list of all required permissions.
public static String[] getRequiredPermissions();
Proguard settings are applied automatically as they are defined as consumer proguard rules within the SDK. The current rules can also be found in the Sample app.
Use the SDK in your application by including the Maven repositories with the following build.gradle configuration in Android Studio:
repositories {
google()
jcenter()
maven { url 'https://mobile-sdk.jumio.com' }
}
Check the Android Studio sample projects to learn the most common use.
You can filter which architecture to use by specifying the abiFilters.
Note: The abiFilters command in the ndk closure affects the Google Play Store filtering.
defaultConfig {
ndk {
abiFilters armeabi-v7a","arm64-v8a","x86","x86_64"
}
}
The apk can be split based on the architecture if multiple apks should be uploaded to the Google Play Store. Google Play Store manages to deliver the appropriate apk for the device.
splits {
abi {
enable true
reset()
include armeabi-v7a","arm64-v8a","x86","x86_64"
universalApk false
}
}
Note: You get an UnsatisfiedLinkError, if the app and the CPU architecture do not match.
Our SDK supports the default Android localization features for different languages and cultures.
All label texts and button titles in the SDK can be changed and localized by adding the required Strings you want to change in a strings.xml file in a values directory for the language and culture preference that you want to support. You can check out strings that are modifiable at .../src/main/res/values/strings-jumio-sdk.xml within our Sample application.
For our products Netverify & Fastfill, Authentication & Document Verification we are providing eight individual languages for your convenience:
- Chinese (Simplified)
- Dutch
- English
- French
- German
- Italian
- Portuguese
- Spanish
Our SDK supports accessibility features. Visually impaired users can now enable TalkBack or change the font size on their device. The accessibility-strings that are used by TalkBack contain accessibility_ in their key and can be also modified in the strings.xml.
- Integration Netverify & Fastfill SDK
- Integration Authentication SDK
- Integration Document Verification SDK
- Integration BAM Checkout SDK
The previous release version 3.4.1 of the Jumio Mobile SDK is supported until 2020-05-01.
In case the support period is expired, no bug fixes and technical support are provided anymore (bugs are typically fixed in the upcoming versions). Older SDK versions will keep functioning with our server until further notice, but we highly recommend to always update to the latest version to benefit from SDK improvements and bug fixes.
If you want to enable two-factor authentication for your Jumio customer portal please contact us at https://support.jumio.com. Once enabled, users will be guided through the setup upon their first login to obtain a security code using the "Google Authenticator" app.
The software contains third-party open source software. For more information, please see licenses.
This software is based in part on the work of the Independent JPEG Group.
If you have any questions regarding our implementation guide please contact Jumio Customer Service at support@jumio.com or https://support.jumio.com. The Jumio online helpdesk contains a wealth of information regarding our service including demo videos, product descriptions, FAQs and other things that may help to get you started with Jumio. Check it out at: https://support.jumio.com.
© Jumio Corp. 268 Lambert Avenue, Palo Alto, CA 94306
The source code and software available on this website (“Software”) is provided by Jumio Corp. or its affiliated group companies (“Jumio”) "as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall Jumio be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including but not limited to procurement of substitute goods or services, loss of use, data, profits, or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this Software, even if advised of the possibility of such damage. In any case, your use of this Software is subject to the terms and conditions that apply to your contractual relationship with Jumio. As regards Jumio’s privacy practices, please see our privacy notice available here: Privacy Policy.