RSID docs
    English
    • English
    • Russian
    • Uzbek
    • Integration Overview
    • Web SDK
      • Usage guide
      • sign-in
        POST
      • refresh
        POST
      • create-session
        POST
      • user-info
        GET
    • Mobile SDK
      • Usage guide
      • sign-in
        POST
      • refresh
        POST
      • create-session
        POST
      • user
        GET
    • Backend with information
      • Usage guide
      • sign-in
        POST
      • refresh
        POST
      • Option 1 — compare photo with passport photo
        POST
      • Option 2 — compare two photos with citizen data
        POST
      • Option 3 — compare two photos without citizen data
        POST
      • Get result
        GET
    • Backend without information
      • Usage guide
      • sign-in
        POST
      • refresh
        POST
      • Option 1 — compare photo with passport photo
        POST
      • Option 2 — compare two photos with citizen data
        POST
      • Option 3 — compare two photos without citizen data
        POST
    • Auth and Qr identification
      • Sign with RS-ID (Oauth2 style)
      • Qr Sign/Identification process
      • Get user info by code
        POST
      • sign-in
        POST
      • refresh
        POST
      • Create a QR token
        POST
      • Get QR token status by qr_id
        GET
      • Get QR token status by external_id
        GET
    • Schemas
      • ErrorResponse
      • AuthCodeRequest
      • ClientCredentials
      • Token
      • UserInfo
      • TokenResponseEnvelope
      • DocumentInfo
      • Signer
      • StringResponseEnvelope
      • ContactInfo
      • CallbackEvent
      • UserProfile
      • QrTokenCreateRequest
      • PhotoItem
      • Address
      • UserProfileResponseEnvelope
      • AdditionalParams
      • WebSessionCreateRequest
      • QrToken
      • UserProfileResponse
      • CompareFaceRequest
      • UserResponseEnvelope
      • CompareImagesWithInfoRequest
      • QrTokenResponseEnvelope
      • CompareImagesRequest
      • SignCallback
      • ComparisonResult
      • MobileSessionCreateRequest
      • ComparisonResultEnvelope

    Integration Overview

    RS-ID — Overview and integration#

    1. What is RS-ID#

    RS-ID is a biometric identity platform for Uzbekistan. It confirms that a real, live person is who they claim to be — by their face and the national identity registry — and lets them sign in and sign documents with a digital signature.
    With RS-ID your product can:
    Identify a person remotely — check a live selfie (anti-spoofing) and compare it with the citizen's passport photo from the state registry.
    Get verified citizen data — full name, PINFL, birth date, document and address, straight from the registry.
    Compare faces — check that two photos show the same person.
    Let users sign in without a password — with the RS-ID mobile app and a QR code.
    Sign documents — with RS-IMZO or E-IMZO digital signatures stored in the RS-ID mobile app.
    You do not build camera, liveness, face-matching or signature logic yourself — RS-ID provides it through ready screens, SDKs and APIs.

    2. How RS-ID works#

    StepWhat happens
    1. LivenessRS-ID checks that the photo shows a live person, not a printed photo, a screen or a mask.
    2. Registry lookupBy PINFL or passport number + birth date, RS-ID gets the citizen's passport photo and data from the state registry.
    3. Face comparisonRS-ID compares the faces and returns a similarity score from 0 to 1.
    4. DecisionThe score is compared with the threshold (default 0.5). Above it — identified.
    5. ResultYour backend receives the result and, depending on the integration, the verified citizen profile.

    3. Integration options#

    IntegrationWhat it isWho shows the screensResult for your backendGuide
    Web SDKIdentification on your websiteRS-ID page (redirect or iFrame)Verified citizen profileIntegration with Web SDK
    Mobile SDKIdentification in your Android / iOS appRS-ID native SDK inside your appVerified citizen profileIntegration with Mobile SDK
    Backend API (with info)Server-to-server face comparisonYour own UI — you send the photosScore + verified citizen profileIntegration with Backend API
    Backend API (without info)Server-to-server face comparisonYour own UI — you send the photosScore only, no personal detailsIntegration with Backend API (without info)
    Sign in with RS-IDPasswordless login (OAuth2)RS-ID auth page with a QR code + RS-ID mobile appUser profile by authorization codeSign in with RS-ID (OAuth2)
    QR signingDigital signature (RS-IMZO / E-IMZO)Your QR code + RS-ID mobile appSigned data (PKCS#7) to your callbackQR signing with digital signature

    Which one to choose#

    rsid-choose-integration.png
    If you need to…Use
    Verify a user on your website, with no camera work on your sideWeb SDK
    Verify a user inside your mobile appMobile SDK
    Verify with photos you already take in your own app, kiosk or branchBackend API
    …and you only need a yes/no match, without storing personal dataBackend API (without info)
    Let users log in to your site by scanning a QR codeSign in with RS-ID
    Get a legally valid digital signature on a documentQR signing
    Integrations can be combined — for example, Web SDK for onboarding, Sign in with RS-ID for later logins, and QR signing for contracts.

    4. Use cases#

    IndustryExamples
    Banking and financeRemote account opening, loan applications, confirming large transfers, signing loan agreements.
    InsuranceOnline policy purchase, claims confirmation.
    TelecomSIM card registration, changing the number owner.
    E-commerce and marketplacesSeller verification, age checks, installment purchases.
    Government and educationAccess to personal accounts, applications and certificates.
    HR and B2BRemote hiring, signing employment contracts and acts between companies.

    5. Getting started#

    1.
    Contact RS-ID and choose the integrations you need.
    2.
    Get credentials — RS-ID registers your project and issues a client_id / client_secret for each integration and environment. For Sign in with RS-ID, also register your redirect_uri.
    3.
    Integrate on stage — follow the guide for your integration and test with the stage environment.
    4.
    Go live — receive production credentials and switch the base URLs to production.
    Each integration has its own credentials. Web SDK credentials do not work for Mobile SDK or Backend API, and the other way round (-1002).
    Modified at 2026-11-09 13:03:10
    Next
    Usage guide
    Built with