{"section":"known-issues","requestedLocale":"en","requestedSlug":"checkout-login-flow-allows-changing-email-but-flow-is-not-supported","locale":"en","slug":"checkout-login-flow-allows-changing-email-but-flow-is-not-supported","path":"docs/en/known-issues/Checkout/checkout-login-flow-allows-changing-email-but-flow-is-not-supported.md","branch":"main","content":"## Summary\n\n\nWhen at checkout with an informed e-mail and masked data, logging in will be necessary if the shopper wants to change any information. In the login box that will open, the email will already be filled with the cart's context, but the interface allows the \"suggested\" email to be modified.\n\nThe suggested e-mail must not be changed. If the client enters another email, the login flow will not work - in the API request, there will be a silent error, and the UI will be stuck in a \"loading\" state.\n\n\n##\n\n## Simulation\n\n\n\n- At checkout, inform an email with a complete profile so that the data is auto-completed and masked;\n- Try to change some information, such as the address (login will be required);\n- In the login box, the e-mail in the cart will already be filled in;\n- Change the email in the login box;\n- Try to move on; it won't be possible.\n\n\n##\n\n## Workaround\n\n\nThe store can make this field read-only for the login flow at checkout."}