The User Lifecycle

A UR user's journey from pre-signup to live.

To access the full spectrum of Core Banking operations, a user is required to hold a URID 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.

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.

Users must perform this step with UR regardless if they have done it before on the Partner platform.

• 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.