Remote Config SDK
Skip the release process
Easily integrate SMS, Missed Call, or IVR-based two-factor authentication with our powerful SDK, available for both iOS and Android platforms.
Why Choose Remote Config SDK ?
Powerful features designed to give you complete control over your verification flow
Instant 2FA flow updates
Update your verification flow instantly without app store releases or code deployments.
Fraud Protection
Advanced fraud detection and prevention mechanisms to protect your verification process.
Mobile Friendly
Works seamlessly across iOS and Android devices with platform specific optimizations.
Open Source
Transparent, community-driven development with full access to source code and documentation.
Feature-Rich Analytics
Comprehensive analytics and reporting to track verification success rates and user behavior.
Quick Integration
Simple SDK integration that gets you up and running in hours, not days.
Full Control Without App Updates
Take complete control of your verification process with real-time configuration management
Dedicated mobile apps boost user engagement and customer lifetime value, but updating verification flows can be a hassle due to app store reviews and slow client adoption.
CheckMobi's Remote Config SDK solves this by letting you update your mobile number verification, 2FA, and OTP flows instantly—no app update needed, no extra cost, unlimited changes.
Choose your primary OTP method (SMS, Voice, or Missed Call), enable fallbacks, and set retry limits—all from the CheckMobi console. Tailor flows by platform (iOS/Android), country, or mobile operator for maximum flexibility.
Key Benefits
What can I do with Remote Config SDK ?
Discover the powerful capabilities that Remote Config SDK brings to your verification workflow
Change the number verification flow
Change the number verification flow directly from the Checkmobi website, on the fly, without deploying a new version. Our complete suite of verification products (SMS, Voice, Missed Call) creates a variety of flows that you can test instantly.
A/B testing & maximum flexibility
Customize different flows by country, operator or even number and split test to validate improvements. Test multiple verification methods simultaneously to find the optimal conversion rates.
Skip the release process
With our Remote Config SDK you get all of these features directly available on the CheckMobi web console so you can act fast while skipping the lengthy release process.
How to integrate it in my apps?
In order to integrate the Remote Config SDK into your app you need to follow the integration steps found on our Github repositories. Here's how easy it is to do a basic integration:
1// In order to use the SDK you need to set the CheckMobi Secret Key from the web portal.
2// You can do this somewhere before calling any SDK method by calling:
3CheckmobiSdk.getInstance().setApiKey("YOUR_SECRET_KEY_HERE");
4
5// The first thing you need to do before starting the verification process is to
6// check if the user has already verified his number. You can do this like so:
7if(CheckmobiSdk.getInstance().getVerifiedNumber(<context>) != null){
8 // user already verified the number ...
9} else {
10 // start a validation process you should add the following lines of code:
11 startActivityForResult(
12 CheckmobiSdk.getInstance()
13 .createVerificationIntentBuilder()
14 .build(StartActivity.this), VERIFICATION_RC);
15}
16
17// You should also override the onActivityResult method like so:
18@Override
19protected void onActivityResult(int requestCode, int resultCode, Intent data) {
20 super.onActivityResult(requestCode, resultCode, data);
21 if (requestCode == VERIFICATION_RC) {
22 if (resultCode == RESULT_OK) {
23 //The user has verified his phone number successfully
24 } else {
25 //The user canceled the verification process
26 }
27 }
28}1// In order to use the SDK you need to set the CheckMobi Secret Key from the web portal.
2// You can do this somewhere before calling any SDK method by calling:
3CheckMobiManager.shared.apiKey = "YOUR_SECRET_KEY_HERE"
4
5// The first thing you need to do before starting the verification process is to
6// check if the user has already verified his number. You can do this like so:
7if(CheckMobiManager.shared.verifiedPhoneNumber != nil){
8 //user already verified the number ...
9} else {
10 // start the verification process
11 CheckMobiManager.shared.startValidationFrom(viewController: self, delegate: self)
12}
13
14// You should also implement the CheckMobiManagerProtocol methods like so:
15public func checkMobiManagerDidValidate(phoneNumber: String, requestId: String) {}
16public func checkMobiManagerUserDidDismiss() {}
1// In order to use the SDK you need to set the CheckMobi Secret Key from the web portal.
2// You can do this somewhere before calling any SDK method by calling:
3CheckMobiManager.shared.apiKey = @"YOUR_SECRET_KEY_HERE";
4
5// The first thing you need to do before starting the verification process is to
6// check if the user has already verified his number. You can do this like so:
7if(CheckMobiManager.shared.verifiedPhoneNumber != nil)
{
8 //user already verified the number ...
9} else {
10 // start the verification process
11 [CheckMobiManager.shared startValidationFromViewController:self delegate:self];
12}
13
14// You should also implement the CheckMobiManagerProtocol methods like so:
15- (void)checkMobiManagerDidValidateWithPhoneNumber: (NSString *)phoneNumber
16 requestId:(String *)requestId {}
17- (void)checkMobiManagerUserDidDismiss {}