Integration Guide

1. Overview

UR offers a flexible infrastructure designed to bridge the gap between Web3 assets and traditional finance. Whether you are building a consumer fintech app or a native Web3 wallet, UR provides the right integration path for your needs.

We support two primary integration modes:

1. Delegated Mode (API-Driven): A seamless, Web2-style integration where UR manages the complexity of blockchain interactions.

2. External Wallet Access Mode (Self-Custody): A Web3-native integration where users connect their own wallets and retain full control over keys and signing.

This guide will help you understand the differences and choose the mode that best fits your platform's architecture and user experience goals.

Feature	Delegated Mode	External Wallet Access Mode
Integration Style	Web2 / API-First	Web3 / SmartContract-First
User Onboarding and Card Registration UI	Redirect users to UR's webview	Partner to implement all the UIs
Transactions	Operations are API-driven with minimal user interaction. To enable this, users must grant asset allowances to the Delegated Contract during the registration process. This permission can be revoked anytime by logging into the UR application.	User must sign every action via their wallet.
Asset Custody	Assets are held in user's UR Account that are controlled by the user. These are embedded wallets, with the Trusted Execution Environment (TEE) infrastructure provided by Turnkey.	Self-Custody: Assets are held in the user's external wallet.
User Onboarding	Redirects to UR Webview for account creation.	User signs a message with their wallet to mint a URID.
Gas Fees	Handled by UR (via operator wallets).	Typically paid by the user. Gasless option available.
Card Management	User redirect and login a dedicated Webview provided by UR to manage card.	Requires user signature to authorize card creation and settings.
Development Effort	Lower: Standard API integration.	Higher: Requires handling Web3 signatures and wallet connections.

2. Integration Models

2.1 Delegated Mode (Recommended)

In Delegated Mode, your platform interacts with UR primarily through REST APIs. This offers the smoothest user experience, similar to traditional banking apps, by minimizing the need for users to sign every blockchain transaction.

How Delegated Contract Mode Works:

1. Partner calls UR’s REST APIs or SDK.

2. UR validates:

   • Partner authentication

   • User identity & authorization

   • Compliance and risk checks

3. UR executes onchain operations using a secure AWS HSM operator wallet.

4. UR triggers any required off-chain fiat settlement.

5. UR returns:

   • status

   • intent IDs

   • webhooks for completion events

Please refer to this document for details on the Delegated Contract mode.

User Experience

Users authenticate via social login only during onboarding to finalize KYC and authorization. Subsequent interactions are frictionless and require no further logins, with UR managing blockchain complexities (gas fees, signing) via a delegated architecture.

Key Features

• Fastest integration experience

• No blockchain knowledge required

• Webhooks provide full lifecycle tracking

• UR handles all retry logic, error management, and settlement

• UR pays gas for execution

• Best for large consumer apps or exchanges with Web2 stacks

2.2 External Wallet Access Mode

External Wallet Access Mode is designed for platforms where users expect to bring their own wallet (e.g., MetaMask, Rabby, etc.) and maintain full self-custody of their keys.

Note: UR will not provision an additional wallet for these users; the URID and fiat balances (tokenized deposits) are managed directly within the user’s external wallet.

How External Wallet Access Mode Works:

Please refer to this document for details on the External Wallet Access mode.

User Experience

The experience is Web3-native. Users must connect their wallet and sign messages or transactions to approve actions. Your platform acts as a facilitator, relaying these signatures to UR or guiding the user to interact with smart contracts directly.

Key Features

• Self-Custodial: Users retain full control of their private keys and assets.

• Web3 Native: Fits naturally into existing dApp workflows.

• Trustless: Critical actions are authorized cryptographically by the user.

Which mode should you choose?

Regardless of the integration mode, it is the partner's responsibilities to map and maintain the relationship between the users' unique identifier on the partner's platform and their corresponding UR ID. This allows the partner platform to accurately reflect user states based on UR-provided APIs and webhooks.

Choose Delegated Mode if:

• You prefer simplicity

• You want UR to orchestrate settlement and compliance

• You want automatic mapping between your users and UR wallets

Choose External Wallet Access Mode if:

• You are building a Web3-native product

• You prefer fully onchain, transparent execution

• You have your own infrastructure to track and process onchain events

• You want maximum control over transaction timing and batching