When it comes to onboarding users, having a flexible sign-up flow that can accommodate different preferences is key. Whether users prefer to sign up with their email, phone number, social media accounts, or directly with a wallet, providing the options that fit your user’s needs can make the onboarding process smoother, more user-friendly, and increase conversion.
That is why we are offering the flexibility to design the sign up screen to suit your needs. You can now choose whether you want users to sign up with their email, phone number, social accounts, or with wallets. You can configure this as needed.
If you then want to generate a wallet for your users when they sign up using
email, social or sms, please refer to the embedded wallets
section after configuring email/social/sms below.
By default, you can use Dynamics credentials to send SMS messages to your users. However, if you want to send beyond US & Canada, you will need to set up your own Twilio account. In order to do this, you toggle off “Use Dynamic’s credentials” and a section will open up for you, where you can enter your own credentials.
SMS & Embedded Wallets
When you enable SMS sign-up, you can also enable embedded wallets for your users. This means that when a user signs up with their phone number, they will also receive a wallet that they can use to interact with your application.
In order to ensure your end users are adequately protected against attacks like sim swaps, we also require a second factor before the wallet is generated. This can be a passkey, or a one time code. We highly recommend using passkeys, which shortens the onboarding flow.
If however, the user loses or deletes their passkey, they will be locked out of their wallet. To prevent this, we recommend prompting users to add an email address to their account. This way, they can recover their wallet if they lose their passkey. When using one time codes, the user will automatically prompted to add their email.
