Customer authentication

introduction chord supports customer authentication and account management customers can log into their accounts, view their order history, and manage subscriptions and saved addresses chord has integrations with authentication platforms like stytch or magic that handles the login process your developers/agency can choose one of chord’s authentication integrations and build a seamless login experience chord sites use a passwordless login flow, typically with “ magic links ” the customer enters their email address in a login form and receives an email with a magic link when the customer clicks the magic link, they are instantly logged into the site without being prompted for a password passwordless authentication decreases the friction of logging in by removing the need for a password so your customer doesn’t struggle to retrieve a forgotten password customer login customers can access their accounts by clicking the login or account button on the website they will then be redirected to a form with a single field prompting them to enter their email address users do not need to remember their password; there is no separate registration process instead, new and returning users fill out the same login form a customer account is automatically created in the chord oms when a new customer successfully logs in you may want to add language to your site that explains the above after the customer enters their email address, the site displays a prompt that tells the customer to check their email the authentication platform sends them an email that contains a magic link when customers check their email, they see an email with a magic link to click to finish logging in when they click the link, they are redirected back to the site and instantly logged into their account this link will expire after a period because it contains a unique token used to authenticate the customer when the customer clicks the link in the email, they are redirected back to the site in a new tab the exact url that the customer sees is customizable, and might be the account page, the page they were browsing when they started the login process, or some other page if the customer has their email open in the same browser as the original site, clicking the link in the email opens the site in a new tab, which means the customer now has the same site open in two tabs they are now logged in in both tabs, and should have the same browsing experience in both if the customer has their email open in a different browser or device, clicking the link in the email would open the site in that browser or device they are logged in in that browser or device depending on the authentication platform, they may also see the original browser tab automatically refresh and are logged in there, too if the customer has logged in for the first time, the customer account is created in the chord oms as soon as the login process is complete (the customer clicked the magic link in their email and the site loaded) if the customer just logged in for the first time, the site could prompt the customer to fill out additional profile information a registration flow that uses passwords often captures additional profile information as part of the registration form for example, a site might require an email address, password, and first and last name in the same form the passwordless flow decreases the friction of creating an account by only asking for the email address the customer can be prompted to enter additional profile information after completing the login process the customer’s authentication session can be ended by clicking a logout button, or it will expire after a configurable period of time