# The User Lifecycle

To access the full spectrum of Core Banking operations, a user is required to hold a [URID](/concepts/what-is-ur.md#urid-ur-identity) in the 'Live' state. The entire process—transitioning a URID from its initial creation to its fully activated 'Live' status—is defined within the UR ecosystem as **User Onboarding**.

The User Onboarding process is a two-stage, "progressive KYC" journey designed to maximize conversion. For an overview of what UR verifies during KYC and the methods used (NFC scan, GPS check, document upload, AML screening), see [KYC & Compliance](/concepts/kyc-and-compliance.md).

```mermaid
graph LR
    A[New User on Partner App] --> B("Clicks "Activate Account"");
    B --> C{"Stage 1: Create Tourist User<br/>- User Authenticates<br/>- Wallet & NFT Minted (Tourist)<br/>- Completes C1: Questionnaire"};
    C --> D[UR Preliminary Screen];
    D -- Screening Failed --> F[User Status: Blocked];
    D -- Screening OK --> E{User Status: Tourist};
    E --> G["<b>Capabilities:</b><br/>- Receive Partner Off-ramp<br/>- Receive P2P Transfers"];
    E --> H("User attempts Restricted Action<br/>e.g., External Payout");
    H --> I{"Stage 2: Upgrade to Full User<br/>- Completes C2: PoA<br/>- Completes C3: NFC Scan<br/>- Completes C4: Form A Signing"};
    I --> J[UR Full Compliance Review];
    J -- Review Failed --> F;
    J -- Review OK --> K{User Status: Live};
    K --> L["<b>Capabilities:</b><br/>- All Tourist Capabilities<br/>- External Deposits (IBAN)<br/>- External Payouts<br/>- Send P2P Transfers"];

```

#### **Stage 1: Tourist User (Status: `Tourist`)**

1. This is a fast, low-friction flow to get users onboarded with an account.
2. The user authenticates, gets an wallet address and a UR NFT (in `Tourist` state), and completes the basic KYC screening, which includes users' age, nationality, and residential country.
3. After a preliminary screening, their status becomes `Tourist`.
4. At this point, you can **immediately issue a "restricted bank account"** and **get partner authorization**.
5. A `Tourist` user can receive funds (up to 250 USD), but cannot move funds externally.

#### **Stage 2: Full User (Status: `Live`)**

1. When a `Tourist` user wants to unlock full features (like external withdrawals or viewing their IBAN), your app prompts them to upgrade.
2. This triggers the "Full KYC" flow, where they complete the remaining components (Questionnaire, PoA, Passport/ID NFC Scan and Signing of Agreement).
3. Once approved, their status changes to `Live`, and all bank account restrictions are automatically lifted.

### **UR KYC Components**

**Component 1: UR Questionnaire.** These are questions that we ask about a user, such as screening questions, source of income, monthly income, etc.

* For a lightweight integration, UR’s questionnaire can be shown to user for completion via webview/iFrame pointing to UR webapp (get.ur.app). Here, user must be signed in, i.e. his previous logged in session must persist.

\
**Component 2: Proof of Address.** UR uses the GPS method to collect this information.

* UR’s Proof of Address process can be shown to user for completion via webview/iFrame pointing to UR webapp (get.ur.app). Here, user must be signed in, i.e. his previous logged in session must persist.

\
**Component 3: Proof of Identity via Passport/ National ID NFC scan.**

{% hint style="info" %}
Users must perform this step with UR regardless if they have done it before on the Partner platform.
{% endhint %}

{% hint style="warning" %}
**NFC scanning is only available via a mobile app.** If your platform uses the Sumsub SDK directly (External Wallet Access Mode), the NFC scan step is only supported in the **Sumsub mobile SDK** (iOS/Android) — it is not available in the Sumsub web SDK. You must expose this step through your **mobile app**. Web-only platforms cannot complete this step via the Sumsub SDK. If your platform does not have a mobile app, contact us to discuss alternatives.
{% endhint %}

* Scenario A1: For users on iOS, UR will return a QR Code + Link to our NFC Scanning Provider. When clicked by users, an iOS App Clip will appear, following which users will be able to continue with the NFC scan. After the user is done with the scan, he will be asked to return to the Partner app.
* Scenario A2: For users on Android, UR will return a QR Code + Link to our NFC Scanning Provider. Unlike iOS, Android users will have to download a separate app to perform the NFC scan. After the user is done with the scan, he will be asked to return to the Partner app.

\
**Component 4: Agreement (Form A) Signing**

This is an agreement that contains all of users’ information filled during the KYC process. This means that the user must have completed Component 1 and 2, and the data must exist in our database, before we can generate this form for users. **Users have to sign this with the Turnkey Wallet that holds their UR NFT.**

> Reference: <https://docs.fiat24.com/developer/integration-guide/part-3-client-onboarding#form-a-message-to-sign>

UR’s Form A can be shown to user for completion via webview pointing to UR webapp (get.ur.app). Here, user must be signed in, i.e. his previous logged in session must persist.


---

# Agent Instructions: 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:

```
GET https://docs.ur.app/concepts/overview-the-user-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.