# Mobile Number as customer Identity **URL:** \ **Category:** Questions\ **Created:** [January 14, 2022, 5:37am UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910 "2022-01-14T05:37:57Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![gvnavin](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@gvnavin](https://devforum.okta.com/u/gvnavin)\ **Post date:** [January 14, 2022, 5:37am UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/1 "2022-01-14T05:37:57Z")
We are thinking of using OKTA for our B2C customers One of our use case is to allow users to create account using mobile number and sign-in using mobile number and OTP. When I explored with my OKTA developer account, I couldn’t set mobile number for user identity. Does OKTA supports the mobile number identity ? ---
**Author:** ![phi1ipp](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@phi1ipp](https://devforum.okta.com/u/phi1ipp)\ **Post date:** [January 15, 2022, 9:02pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/2 "2022-01-15T21:02:19Z")
Do you have a constraint on `login` attribute to be in the format of email address? If so, just relax this restriction and you should be able to create users with only numbers in `login` attribute ---
**Author:** ![gvnavin](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@gvnavin](https://devforum.okta.com/u/gvnavin)\ **Post date:** [January 17, 2022, 6:12am UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/3 "2022-01-17T06:12:51Z")
It is not only the format of the login attribute. We want to use proper mobile number for login and we want to send OTP to the mobiles and use the OTP instead of password to login. ---
**Author:** ![phi1ipp](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@phi1ipp](https://devforum.okta.com/u/phi1ipp)\ **Post date:** [January 17, 2022, 1:54pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/4 "2022-01-17T13:54:02Z")
I suggest you to try and open a preview tenant to experiment with your flow. What you are describing looks like OIE use case (though all new tenants should be registered as OIE anyway) ---
**Author:** ![gvnavin](https://avatars.discourse-cdn.com/v4/letter/g/71e660/32.png) [@gvnavin](https://devforum.okta.com/u/gvnavin)\ **Post date:** [January 17, 2022, 4:20pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/5 "2022-01-17T16:20:40Z")
I checked this link - [https://www.okta.com/platform/identity-engine/](https://www.okta.com/platform/identity-engine/), it says email with magic link, but not an email with the OTP or use mobile number to send OTP as SMS. ---
**Author:** ![phi1ipp](https://avatars.discourse-cdn.com/v4/letter/p/85f322/32.png) [@phi1ipp](https://devforum.okta.com/u/phi1ipp)\ **Post date:** [January 17, 2022, 4:33pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/6 "2022-01-17T16:33:20Z")
I don’t think for the registration you can do that, unless you customize onboarding experience with your own onboarding page/solution ---
**Author:** ![abole](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/abole/32/3030_2.png) [@abole](https://devforum.okta.com/u/abole)\ **Post date:** [January 24, 2022, 12:21pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/7 "2022-01-24T12:21:59Z")
In Okta traditional version there’s a an early access feature called Factor Sequencing which can be enabled via Support to create a custom sign-in policy allowing primary authentication with SMS OTP rather than a password. Factor sequencing isn’t progressing to GA as OIE will be doing something similar but better. FS is also not super well supported in my experience due to investment focussing strategically on OIE. At registration time (you’d have to build your own registration app as @phi1ipp mentioned) you can set the username (prefix) to a mobile number (also as @phi1ipp mentioned) and you’d also have to enrol the user in an SMS OTP factor. If a customer ever wanted to change their username / mobile phone you’d need to build an experience to do that (and keep them in sync). ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [February 8, 2024, 9:22pm UTC](https://devforum.okta.com/t/mobile-number-as-customer-identity/18910/8 "2024-02-08T21:22:38Z")