Verification and Identity Flowchart Updated February 14, 2023 23:35 The flowchart and steps below walk you through a simplified version of the process behind running a verification through the Connect widget, as well as the process of using the Identity call in conjunction with verification on the Platform and Nexus APIs. For more information on each step, including the specific endpoints and API calls, follow the link attached to the step. Does User Exist? If no, proceed to step 4. If yes, proceed to step 2. Does this User Already have Members? If no, proceed to step 5. If yes, proceed to step 3. Has this Member already Verified their account? If No, Proceed to step 5. If Yes, Proceed to step 6. New Member/Connection Create User. Create Connect Widget URL. Use this helpful Connect Widget Generator. Listen For Post Messages. All other steps are handled by the MX Widget UI. Call API to Get verification Data. Existing User/Member/Verification Ran Run Identity. Poll Member. Poll MBR every 3 to 5 seconds. Identity is successful when the member connection_status is CONNECTED and the is_being_aggregating field changes from true to false. If `CHALLENGED` or `REJECTED` or `IMPEDED` or any other user actionable connection status, Obtain connect widget url as done in step 5 to surface to user. Set the `current_member_guid` option to a member in an error state. Connect will load in the error view so the end user can resolve the error. Continue Polling Member status until successful as noted above. Call API to get Identification Data. For more information on each step, including the specific endpoints and API calls, follow the link attached to the step. Does User Exist? If no, proceed to step 4. If yes, proceed to step 2. Does this User Already have Members? If no, proceed to step 5. If yes, proceed to step 3. Has this Member already Verified their account? If No, Proceed to step 5. If Yes, Proceed to step 6. New Member/Connection Create User. Create Connect Widget URL. Use this helpful Connect Widget Generator. Listen For Post Messages. All other steps are handled by the MX Widget UI. Call API to Get verification Data. Existing User/Member/Verification Ran Run Identity. Poll Member. Poll MBR every 3 to 5 seconds. Identity is successful when the member connection_status is CONNECTED and the is_being_aggregating field changes from true to false. If `CHALLENGED` or `REJECTED` or `IMPEDED` or any other user actionable connection status, Obtain connect widget url as done in step 5 to surface to user. Set the `current_member_guid` option to a member in an error state. Connect will load in the error view so the end user can resolve the error. Continue Polling Member status until successful as noted above. Call API to get Identification Data. Click, drag, and zoom into the flowchart below to follow the steps. You can also open the flowchart in a new tab by hovering over the chart, then clicking the open button in the upper left. Alternatively, you can view a fullscreen version of the chart with the expand button in the upper right of the flowchart. Was this article helpful? 0 out of 0 found this helpful Yes No