Signup Process with Governmental ID verification Answered
Hi all, Has anyone had any experience using ID verification within the signup process to the extent that the user cannot sign up until the verification has occurred? We have the verification working via an API via Zapier etc but are looking at how best to integrate it into the signup process. For context, one of the plans is only for verified members, and we don't want users to be able to sign up unless they have been verified.
Any help is much appreciated!
When I refer to ID, I mean some form of governmental ID, such as a passport, residence card etc.
Comments
1 comment
Ed Katzler, in that case what you can do is, instead of using the native feature, I believe you must have setup a verification flow in Zapier, i.e. which takes care of the verification process of the government ID.
So, when a user signs up on the website, make sure you don't add any plans to the user by default and then probably when the zap of verification executes and the user is verified, just add the specific plan which provides the user with content access.
This should work the same as email verification feature, but its just that you are having a custom use-case in between for verification.
So, a user signs up on the website, but since no plan is added to the user via memberstack, they won't have access to any content. You can setup login redirect for such members as well which takes them to a page which explains why they don't have access yet.
Once they verify, you can add a plan to that member and whenever they login, they will be able to access the content.
Let me know if this helps.
Please sign in to leave a comment.