> 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

In this section, you will find detailed documentation on how the Process Creation endpoint works in You. 

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.

### Integration Best Practices

Ensure high availability and a seamless user experience by following these integration guidelines.

#### The "Graceful Fallback" Strategy in Payments Flow

Your payment flow should never block the user. If the service is unavailable or the transaction cannot be completed, you must seamlessly redirect the user to your standard payment method (e.g., QRCode Pix).

Implement a Fallback Trigger in the following scenarios:

* API Availability: If the Creation API returns a error or times out.
  * eg: Unavailable banks (if you send to us an bank to use), 5XX errors or another erros.
* Transaction Status: If the webhook (or status polling) returns `canceled` or `failed`.
* Device Incompatibility: If the SDK initialization fails (see section below).

#### Optimize the SDK Lifecycle

To avoid creating "ghost invoices" (process that can never be completed because the user's device is unsupported), validate the environment before communicating with the backend.

Recommended Flow:

1. Client-Side Check: Call `sdk.init()` as soon as the checkout page loads.
2. Verify Support:
   * Success: Proceed to call your backend to create the invoice.
   * Error: Immediately trigger the Fallback Strategy mentioned above.
3. Launch: Only after these steps, call `sdk.open()`.

#### Rely on Webhooks for State Management

While polling the `GET` endpoint is possible, Webhooks are the recommended method for receiving transaction updates.

* Reliability: Webhooks ensure you receive the final status (`completed`, `failed`, `canceled`) even if the user closes the browser window prematurely.
* Efficiency: Reduces unnecessary network traffic and polling latency.
* Security: Allows you to validate the transaction server-to-server before releasing the order.