> For the complete documentation index, see [llms.txt](https://docs.vida.id/identity-stack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vida.id/identity-stack/authentication/introduction/use-cases.md).

# Use Cases

VIDA Authentication Services provide secure, risk-based authentication designed for different use cases based on transaction sensitivity.&#x20;

### **Proof of Device - Low-Risk Authentication Use-Cases**

**Authentication Method:** Phone Token

For low-risk transactions, **Proof of Device** provides a reliable, straightforward authentication method. By using the **VIDA Phone Token**, this solution confirms that the transaction originates from a registered and trusted device. It offers a secure foundation for everyday actions and transactions with minimal complexity.

* **Ideal For**: Verifying trusted devices for actions like login, simple transactions, or access to basic services.

***

### **Proof of Presence - Medium-Risk Authentication Use-Cases**

**Authentication Method:** Phone Token + Device Biometrics

For medium-risk scenarios, **Proof of Presence** combines the security of the **VIDA Phone Token** with **Device Biometrics**. This layered approach ensures that not only the device is trusted but that the user is physically present to initiate the transaction. By leveraging both factors, it provides a stronger and more reliable authentication.

* **Ideal For**: Transaction approvals, account settings changes, and other sensitive actions that require a higher level of security than basic device authentication.

***

### **Proof of User Veracity - High-Risk Authentication Use-Cases**

**Authentication Method:** Face Token + Phone Token&#x20;

For high-risk use cases, Proof of User Veracity ensures the highest level of security by leveraging the **VIDA Face Token**. This combines the **VIDA Phone Token** for device authentication, **Liveness Detection** to prevent spoofing, and **VIDA Selfie ID** to verify the user’s identity. Together, these layers ensure that both the user and the device are trusted, making unauthorized access nearly impossible—even if login credentials are compromised.

* **Ideal For**: Secure transactions involving high-value or sensitive actions, such as financial transactions, account recovery, or accessing highly protected data.
