> For the complete documentation index, see [llms.txt](https://devcenter.unico.io/you/Ol1H6eGO4sQvPYB1Nmyl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devcenter.unico.io/you/Ol1H6eGO4sQvPYB1Nmyl/introduction.md).

# Introduction

You is the trusted digital wallet that centralizes a consumer's verified data and payment methods, allowing them to be shared via consent across different services without the need for repeated data collection and validation.

For the consumer, this means less friction: opening an account, making a purchase, or accessing a service now requires just a single confirmation, rather than re-registering.

For businesses, this translates into conversion: lower drop-off rates, less friction, and more users reaching the end of the journey.

Based on this wallet, various use cases can be built, such as onboarding, authentication, payments, physical access, or service authorization.

### What you build

You create a **process** describing what you need; Unico runs the hosted user journey and hands you the verified result.

On the backend, the API surface is small: `POST /api/public/v1/process` creates the process and `GET /api/public/v1/process/{id}` retrieves the verified result. Webhooks can push status changes to you instead of polling.

On the frontend, you present the hosted flow to the user. On the web, the You SDK renders it inside your page; in native apps, you redirect the user to the process `link` and handle the return via URL scheme.

```mermaid
sequenceDiagram
    box Your application
    participant F as Your frontend
    participant B as Your backend
    end
    box Unico
    participant Y as You API
    participant H as You experience
    end

    F->>B: user starts the journey
    B->>Y: POST /process (scopes)
    Y-->>B: id + token + link
    B-->>F: token (web) or link (native)
    F->>H: SDK open(token), or redirect to link
    Note over H: User completes the journey
    H-->>F: onFinish / redirectUrl
    B->>Y: GET /process/{id}
    Y-->>B: verified data or payment result
    Note over B,Y: or receive the status change via webhook
```

### Where to start

| You want to...                                   | Read                                                          |
| ------------------------------------------------ | ------------------------------------------------------------- |
| Understand the basics and make your first call   | Getting Started                                               |
| Collect verified personal data (onboarding, KYC) | Identity Data Collection                                      |
| Charge a PIX payment                             | PIX Payment Flow                                              |
| Charge a card payment                            | Card Payment Flow                                             |
| Integrate the frontend on your platform          | SDK section (Web, Android, iOS, React Native, Flutter, Ionic) |
| Get credentials                                  | Authentication                                                |
| Receive status updates automatically             | Webhooks                                                      |
| Hand the integration to an AI coding assistant   | Build with LLM                                                |

### Before you start

You will need:

* An **access key** (`x-unico-accesskey`) — see Authentication.
* For web integrations, your **HTTPS domains allowed for the SDK** — the SDK only renders on approved domains. You register them yourself, through the You Console or via API (the Build with LLM prompt handles this step).

UAT and Production use separate keys and base URLs — see Getting Started.