FAQ Upgrading from IDnow AutoIdent to DocIDV.
What does upgrading to DocIDV mean for me?
You’ll switch from AutoIdent to DocIDV for identity verification. The user flow and your integration will stay mostly the same.
I use the AutoIdent SDK (Android/iOS). What do I need to do?
Replace the AutoIdent SDK with the DocIDV SDK. The integration is similar, just update the SDK and imports in your code.
Will the SDK still show a success page after identification?
No. With DocIDV SDK, your app must handle fully the success scenario of identification. You can either display the success screen after a successful identification within the host app or redirect to the page relevant to you. The SDK will still show failure and error screens as well as retry option.
I use the AutoIdent app. What do I need to do?
Update any download links to point to the IDnow Verify app for iOS or Android. If you don’t update the links, users will still be redirected, but switching is recommended.
Please note that Android and iOS apps are called IDnow Verify. However, we named SDKs as DocIDV.
Question 5: I use AutoIdent Web. What do I need to do?
If you use the user data form, no action is needed. If you link directly to AutoIdent Web, update your URLs to DocIDV Web (optional, but recommended).
For webview/ iframe, add the embedded parameter and handle new post messages for redirection.
Will my webhooks, API keys, or endpoints change?
No, these will remain the same.
What will my users experience after upgrading?
SDK/Web: Users will see the DocIDV flow, which works the same as before.
App: Users will download and use the IDnow Verify app instead of AutoIdent.
Further details
For further details, see the DocIDV SDK documentation for Android and iOS, or contact your IDnow representative.