> For the complete documentation index, see [llms.txt](https://ftcoders.first-tech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ftcoders.first-tech.com/first-tech-ttp-sdk/password-recovery.md).
# Password Recovery
**Objective**
This section defines the **minimum requirements** for the password recovery flow, ensuring clarity, security, and accessibility in the process of credential reset by seller users, in accordance with UX best practices and digital security standards.
**Insights**
* This flow must support **limited connectivity scenarios** (e.g., fallback to resend code).
* All messages and visual feedback must be clear, concise, and avoid technical jargon.
* The blue padlock illustration may be adapted to match brand identity, as long as semantic clarity is preserved.
***
## Accessing the Recovery Flow
### 01 - “Forgot your password?” link
Must always be visible on the login screen, placed below the authentication fields
{% hint style="success" %}
**Mandatory:**
When the link is tapped, the user must be redirected to the password recovery screen.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Provide visual feedback on tap (e.g., color change, underline, ripple effect).
{% endhint %}
***
## Password Recovery Screen (Email Input)
### 02 - Email input field
Must allow typing with validation for proper email format (e.g., `example@email.com`)
### 03 - “Send code” button
Must remain disabled until a valid email address is entered
{% hint style="success" %}
**Mandatory:**
Upon submission, the system must send a verification code (2FA) to the provided email.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Display a confirmation message after sending the code (e.g., “Verification code sent successfully to your email”).
{% endhint %}
***
New Password Creation Screen
04 - “Password” and “Repeat password” fields
Must include visibility toggle icons and validate minimum security criteria (e.g., 8 characters, symbol, number, etc)
05 - “Save” button
Must only be enabled when both passwords are valid and match
{% hint style="success" %}
**Mandatory:**
Passwords must be encrypted during storage and transmission, following LGPD and PCI standards.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Display real-time password strength and matching feedback (e.g., “Strong password”, “Passwords do not match”).
{% endhint %}
***
## Mandatory Messages
* When the email is invalid:
> Please enter a valid email address to recover your password.
* After code submission:
> A verification code has been sent to the provided email. Please check your inbox.
* When passwords do not match:
> Passwords do not match. Please review the fields and try again.
***
## Expected Behaviors
* The “Send code” button must be linked to valid email input only.
* The “Save” button must remain disabled until all conditions are met.
* After setting the new password, the user must be redirected to the login screen with a success confirmation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ftcoders.first-tech.com/first-tech-ttp-sdk/password-recovery.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.