Dynamic SDK Integration
Here is a sequence diagram illustrating the steps to integrate with IDWise Dynamic SDK.
This can be summarized in the following steps:
- User Request: The user initiates identity verification from your app.
- Initialize: Your application should initialize IDWise SDK to proceed to the next step.
- Start Dynamic Journey: By calling the startDynamicJourney method you will start a new onboarding journey and this method will trigger startJourney callback that will return the joruneyId. It is recommended to store this journeyId on your backend to know which journey belongs to which user.
- Start Step: After journeyStarted callback, you can start any step (e.g. ID document step, or Selfie Step).
- Image Submission: The user submits ID or selfie images to IDWise SDK.
- Start Processing: IDWise SDK processes images via IDWise Backend.
- Webhook to Backend: IDWise Backend sends a webhook to your backend upon journey completion.
- Outcome Retrieval: Your backend collects the journey outcome and stores it in a database.
- Image Storage: Your backend saves ID and selfie images from IDWise Backend.
- Profile Update: Your backend informs your app of the profile status change, which is then communicated to the user.
You can find the platform-specific guidance below:
Subscribe to webhooks
When IDWise completes processing a journey, it will trigger the webhook that you have specified to notify you about the journey progress. You can find more details about the available events and the data they contain in the webhooks documentation.
After receiving the notification that the journey is finished, you can use the Result Retrieval APIs to get the result and update the user profile accordingly. You can then inform your user that their account is activated or that they need to provide more information.
Updated 10 months ago