UX Guide

Positioning Our Banking Services for Your Users

Introduction

This guide helps partners integrate UR's banking services in a way that accurately represents our product offering and creates the best experience for end users.

UR provides banking infrastructure with comprehensive banking features. The multi-currency card is a valuable spending tool that complements the account, not the primary product.

Following these guidelines ensures your users understand the full value of UR's banking services and helps set appropriate expectations from the start.

What UR Provides

UR offers a bank account that enables users to:

• Hold and manage fiat currency balances

• Deposit funds via bank transfer

• Send funds to external bank accounts

• Convert digital assets to fiat (off-ramp)

• Convert fiat to digital assets (on-ramp)

• Spend their balance using a multi-currency card

The account is the foundation. The card is a convenient way to access and spend the funds held in that account.

What UR Is Not

UR is not primarily a card product or payment card service. While the multi-currency card is a valuable feature, it should be positioned as one of several ways users can utilize their bank account, not as the main offering.

Messaging Hierarchy

Primary Messaging

Your integration should emphasize:

1. Total bank balance

2. Individual currencies balances

3. Deposit, Send, Convert functionality

Secondary Messaging

After establishing the account value:

• Multi-currency spending capability

• Transaction history

• Virtual debit card

• Card management

What to Avoid

Do not position UR primarily as:

• A card product ("Get your Crypto card")

• A payment card service

• A crypto card offering

• Card-first value propositions

Copy Guidelines

Recommended Terminology

Account Opening & Setup

✅ "Open your bank account" ✅ "Start banking with UR" ❌ "Apply for a card" ❌ "Card application"

Feature Descriptions

✅ "Manage your cash balance" ✅ "Deposit cash to your account" ✅ "Send money to any bank account" ✅ "Convert crypto directly into your bank account" ✅ "Spend your balance with a debit card" ❌ "Top up your card" ❌ "Card balance" ❌ "Load your card"

Partner Positioning of UR

Banner/Marketing Placement For Introduction & Acquisition

The partner should position UR as an embedded financial capability rather than an external service.

Key Positioning Principles:

1. Lead with the benefit to the user, such as faster payouts, better rates, more control

2. Mention "Licensed bank account" early for credibility

3. Avoid "Get the UR/Partner card" messaging

4. Position as integrated solution, not external app

5. Use your brand's voice, not UR's

Banner example

Fixed Entry Points for UR Bank Account Access

Beyond the initial banner/introduction, partners should provide persistent access to UR account features through a fixed entry point on the home screen. This ensures users can always access their UR account quickly to check balances and transactions without searching through menus.

Why Fixed Entry Points Matter:

User Benefits:

• Instant access to account balance

• Quick actions without navigation

• Reduces friction for frequent actions

Partner Benefits:

• Increased feature engagement

• Reduced support queries ("where's my account?")

• Better user retention

• Clear value proposition always visible

Example of a fixed entry point

Another example of a fixed entry point

Figma Reference: Fixed Entry Point

Visual Hierarchy

Your integration should follow this visual hierarchy:

1. Account Information (60% prominence)

• Account balance (primary visual element)

• Currency balance

• Recent account activity

1. Core Banking Actions (30% prominence)

• Deposit funds

• Send funds

• Convert

1. Card Features (10% prominence)

• Card management

Bank Account page example

Figma Reference: Bank Account Dashboard

Account Creation

Partner users must establish their UR identity and link it to their partner account before accessing banking features. This process accomplishes two things:

1. Account Creation: Creates on-chain credential representing the UR account and KYC identity

2. Account Linking: Connects partner platform identity to user's UR account

Two Authentication Paths

Google OAuth (Recommended)

• One-tap authentication

• No CAPTCHA or OTP required

• Fastest path

• Leverages Google's existing verification

Email Authentication

• Universal accessibility (no Google account needed)

• Requires CAPTCHA (bot prevention)

• Requires OTP verification (email ownership proof)

• More steps, but more privacy control

Figma Reference: Account Creation

URID

URID (UR Identification) is a unique identifier generated when a user creates a UR account. It serves as the primary account identifier for customer support and internal operations. Technically, the URID is the token ID of the user's Account NFT on-chain — it is the user's on-chain identity in the UR system.

Purpose:

• Unique account identification across all partners

• Customer support account lookup

• Internal operations and troubleshooting

• Cross-reference between partner systems and UR infrastructure

• On-chain account identity via NFT token ID

Technical Background

Each UR user is represented on-chain by an Account NFT. The URID corresponds directly to the token ID of this Account NFT, making it the canonical on-chain identity for the user. This means the URID is not merely a database key — it is a verifiable, immutable identifier rooted in the blockchain.

For more technical details on how Account NFTs are structured and managed, refer to the Account section in Smart Contracts.

Recommended Placement

URID is rarely needed by users in normal operations. However, it needs to be accessible for support scenarios.

Ensure it has low visual priority and doesn't compete with high-priority information or actions.

Example of low-priority but always accessible placement of URID

KYC

The KYC (Know Your Customer) verification process enables users to activate their bank account and unlock full banking functionality. The flow consists of three sequential parts designed to verify user identity, collect required information, and ensure regulatory compliance.

The User Lifecycle

Displaying the UR ID During KYC

UR ID is the user's support identifier. During custom partner KYC flows, users should always be able to read and share this value when they need support.

Where UR ID comes from

Retrieve the UR ID (tokenId) from the Account NFT contract by calling tokenOfOwnerByIndex(userAddress, 0).

https://github.com/mantle-xyz/ur-doc/blob/main/design/developer-resources/smart-contracts.md#account

When to display it

Show UR ID persistently:

• Across the full KYC onboarding flow (all steps)

• On every retry or failure screen

• Until KYC is completed or the user exits the flow

UX recommendations

• Keep it always visible in a fixed area (for example, top bar or sticky footer)

• Provide one-tap copy

• Keep visual priority low so it does not compete with primary KYC actions

Tech writer review required before publish.

Three-Part KYC Structure (5-10mins)

1

Questionnaire

Tool: Sumsub Purpose: Collect user information and assess risk profile Duration: 2-3 minutes

2

Biometric ID Verification

Tool: ReadID App Clip (iOS) or ReadID App (Android) Purpose: Verify identity document authenticity via NFC chip scanning and liveness check Duration: 2-3 minutes

3

Form A Signing

Purpose: Regulatory compliance and consent documentation Duration: 1-2 minutes

Design Principles

Transparent Expectations

Users know what's required before they start: "3 steps: Answer questions → Scan ID → Sign form." Setting expectations reduces anxiety and abandonment.

Platform-Appropriate Tools

Different tools for iOS (App Clip) vs Android (full app) optimize for each platform's capabilities while maintaining functional parity.

Security Through Familiarity

Using established third-party tools (Sumsub, ReadID) leverages user trust in recognised verification providers.

Auto-save progress

If user exits mid-questionnaire, they can resume without restarting

Pre-KYC Entry Point

Delegated Access

After successful UR account creation, users see the KYC prompt. If users dismiss the prompt or stop mid-way, they can proceed with KYC in a 'Bank Account dashboard' or equivalent on the partner's site.

After successful account creation and connection, users see the KYC prompt.

Bank Account dashboard: Black card showing "Verify Your Identity" (Pre-KYC state)

Figma Reference: KYC

Virtual Debit Card Activation

The card activation flow serves as a critical bridge between account verification and spending capability. This document outlines the strategic design decisions, mandatory currency authorization and the security patterns that protect users while enabling frictionless card usage.

Currency Authorization and Enablement

Due to regulatory reasons, users have to authorize currencies for payment. To ensure payment does not fail at point of purchase, it is recommended to add currencies authorization at the card activation flow.

We recommend enabling all currencies by default as it maximizes payment success. For wallet partners, this has to be enabled via EIP-7702 in order to batch transactions.

Integration Type: Delegated Access

Figma Reference: Delegated Access Card Activation

Authentication Requirement

Every View Card action requires re-authentication and it applies to both activated and inactive card. Card details represent highly sensitive information comparable to physical card access. This security pattern:

1. Protects against unauthorised access: If someone gains temporary access to an unlocked phone, they can't view full card numbers and CVV

2. Follows industry standards: Banking apps universally gate card details behind authentication

3. Creates security ritual: Users associate card access with security verification, building trust in the platform's protective measures

While authentication adds friction, the trade-off is acceptable because users expect this security measure for financial data.

Integration Type: Wallet Access

Figma Reference: Wallet Access Card Activation

Authentication Requirement

Every "View Card" action requires wallet authentication and applies to both activated and inactive cards. Card details represent highly sensitive information comparable to physical card access. This security pattern:

1. Protects against unauthorised access: If someone gains temporary access to an unlocked phone, they can't view full card numbers and CVV

2. Follows industry standards: Banking apps universally gate card details behind authentication

3. Creates security ritual: Users associate card access with security verification, building trust in the platform's protective measures

While authentication adds friction, the trade-off is acceptable because users expect this security measure for financial data.

Wallet Authentication Pattern

For viewing card details:

• For external wallet partners: Users must authenticate with their wallet (ie biometric, PIN)

  • Wallet signature proves ownership and intent

• For delegated access partners: Users must authenticate with their UR credentials (Google SSO or Email OTP)

• This applies every time users access "View Card"

For card activation:

• For external wallet partners: Users must authenticate with their wallet signature

  • Currency authorization is recommended to be included as part of the activation flow

• For delegated access partners: Users activate through standard partner authentication flow via UR's webview

  • Currency authorization is included within the activation flow

Viewing sensitive card data (full number, CVV) requires cryptographic proof of wallet ownership.

Card Management

The Card page serves as the central hub for card security and spending preferences.

Users can:

• View card details

• Manage currency authorization

• Monitor spending limits

• Control card security features

Figma Reference: Card Management

Off-Ramp

UR's off-ramp service enables users to convert digital assets into fiat currency and deposit funds directly into their UR bank account. This seamless conversion bridge connects the digital asset ecosystem with traditional banking, allowing users to cash out digital assets at competitive rates with transparent fees.

How It Works

Users initiate off-ramp transactions from their partner platform, selecting:

• Digital asset to convert

• Amount to cash out

• Destination currency

The converted fiat appears in their UR bank account balance within minutes, ready to spend via Mastercard debit card.

Figma Reference: Off-ramp

Bank Transfer

UR's bank transfer service allows users to receive funds from external bank accounts (that are under their own name) into their UR account. User can accept incoming transfers in CHF, EUR, and USD from their personal bank accounts at other financial institutions, providing flexible funding options beyond crypto off-ramping.

How It Works

For security, users are required to authenticate in order to access their IBAN details. They provide these details to their external bank to initiate a transfer. Funds arrive in their UR account within standard banking timeframes.

Figma Reference: Bank Transfer