Phone Sign-In and Registration with a Code

Signing in by phone number instead of a password

The customer enters a number, gets a code and is in the store - no password, no e-mail with a link, no registration form. If there is no such customer yet, the account is created by the same action. The store decides which methods to keep: phone, e-mail or both.

What the customer sees

The sign-in form shows as many tabs as there are allowed methods: with a single method there are no tabs at all. The customer enters the number, presses "Get the code" and types four digits - that is enough both to sign in and to register.

The sign-in form: tabs by phone and by e-mail, the customer enters a number.

The code has been sent: four digits left to type.

The store sets the sign-in methods

The "Available sign-in methods" setting decides what the customer sees. The set of tabs used to be tied to the e-mail field of the registration form, and an unwanted method could not be removed - in 3.3 these are two independent settings.

• •  By phone and e-mail - two tabs on the form, the order comes from the "Default authorization method" setting.
• •  By phone only - no tabs, sign-in and registration go by the number.
• •  By e-mail only - the code is sent by mail and the store needs no SMS gateway at all.
• •  The customer e-mail field now controls only the field itself in the registration form and the profile: forbidden, required or optional.
• •  The chosen method is validated on the server as well: signing in by a method the store has closed does not work.

The second tab: signing in by the e-mail address.

Settings: the type of authorization, the available sign-in methods and the customer e-mail field.

Registration and phone verification

• •  Phone verification at registration can be switched off - the number then stays an ordinary profile field and the customer registers with no code.
• •  A unified registration and sign-in form: a known number signs in, a new one registers.
• •  The call request and other store forms can be guarded by phone verification too.
• •  A guest order is placed with or without phone verification, as the setting says.
• •  A generated e-mail for the customers who left the field empty: the account gets a service address and the order is not lost.

Registration: the phone is confirmed by a code, the e-mail is up to the customer.

The customer profile in the admin panel: the add-on marks the confirmed number.

Where the code comes from

SMS are sent by the "SMS services" add-on: the operator is chosen there and its credentials are entered there. The sign-in add-on shows the state of that channel right in its own settings - whether the services add-on is installed and a gateway is chosen.

• •  The code to the e-mail is sent by the add-on itself, by a store e-mail, with no SMS gateway.
• •  The lifetime of the code, resending and the number of entry attempts are configurable.
• •  A hint with the last digits of the number tells the customer where the code has gone.
• •  The SMS and e-mail texts are store language variables, the administrator edits them.

Code settings: the lifetime, the resend pause and the number of attempts.

Marketplace and several storefronts

• •  Multi-Vendor. Signing in by a code works for marketplace customers as well, and phone verification is available on the vendor forms.
• •  Several storefronts. The sign-in methods, the e-mail field, phone verification and the code settings are defined per storefront.
• •  Themes. The sign-in form and the phone field are drawn by the add-on templates; UniTheme2 has templates of its own.

The add-on in the list of add-ons of the admin panel.

What is new in version 3.3

• •  The sign-in methods are chosen by a setting: by phone and e-mail, by phone only or by e-mail only. Tabs appear on the form only when there are two methods.
• •  Phone verification at registration can be switched off - the number stays a profile field.
• •  The add-on works without the "SMS services" add-on: in the e-mail mode the code is sent by mail, and the state of the SMS channel is shown in the settings.
• •  The "Authorization by e-mail" setting is renamed to "Customer e-mail field" and controls only the field in the registration form and the profile.
• •  The "Place order" button works for a customer with an unverified phone when verification is not required.
• •  The cart collected before the sign-in survives the code confirmation at checkout.
• •  In stores with old e-mail templates the message with the code is sent again.

Frequently asked questions