Separate username and password pages

This approach brings more secure and user friendly login system for the restaurant owners

• It helps the user to understand if the email address they have entered is correct before they proceed to entering a password.
• If you are unsure about what credentials you used to create an account, guessing both the email address and password means you are more likely to be entering one incorrectly, but you don't know which. However, if you enter just the email and it is wrong, then you know it is the email address which is wrong as oppose to wondering if the password is incorrect too.
• The separation could make credential stuffing attacks more cumbersome. It also allows the platform to perform conditional security checks. For example, the site can check if the account has enabled two-factor authentication and, if not, require a CAPTCHA for login.
• The two-page design also makes it harder for bad actors to create phishing sites with look-alike login pages when there is a page redirect involved. However it's probably not worth the additional step unless you also have the SSO use case.

Two factor authentication validation

2FA will validate restaurant owner login and secure his account