# Unico Developer Documentation

> Documentation for the Unico identity verification platform: use cases, capabilities, SDKs, and API reference.

## Docs

- [IDCloud](https://developer.unico.io/index.md): Unico Developer Portal — documentation for IDCloud identity verification APIs, SDKs, and capabilities for web, Android, iOS, and Flutter.
- Build
  - [Sign-up](https://developer.unico.io/products/sign-up.md): Verify the identity of new customers anywhere in the world and ensure secure registration. A set of capabilities in a single journey, tailored to the scenario you need.
    - [Onboarding](https://developer.unico.io/products/sign-up/onboarding/index.md): Identity verification, in any region, with liveness, Biometric Identity Verification, fraud risk assessment and document reuse.
    - [Non-document verification](https://developer.unico.io/products/sign-up/non-document-verification/index.md): Identity verification, in any region, with liveness, Biometric Identity Verification and fraud risk assessment.
    - [Fraud Risk Level Detection](https://developer.unico.io/products/sign-up/fraud-risk-level-detection/index.md): Validates that a real person is performing the registration by combining Liveness with Behavioral Alert — no document capture or government identifier required.
    - [Multi Accounts](https://developer.unico.io/products/sign-up/multi-accounts.md): Validate the One Face, One Contract principle by cross-referencing a user's facial biometrics against your operator's registration base.
  - [Step-up Authentication](https://developer.unico.io/products/step-up-authentication.md): Verify the identity of customers anywhere in the world in transactional flows and ensure a secure process. A set of capabilities in a single journey, tailored to the scenario you need.
    - [Smart revalidation](https://developer.unico.io/products/step-up-authentication/smart-revalidation/index.md): Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.
  - [Regional Solutions](https://developer.unico.io/products/regional-solutions.md): Products designed to address pain points from regional legislation and legal frameworks — identity verification flows adapted to local regulatory requirements.
    - [Age Verification](https://developer.unico.io/products/regional-solutions/age-verification/index.md): Allows proving that the user meets the minimum required age in a 100% biometric way, without document friction.
    - [Data Verification](https://developer.unico.io/products/regional-solutions/data-verification/index.md): Provides the necessary information about a person so that companies can comply with current regulations for financial services and iGaming.
    - [Card Not Present Verification](https://developer.unico.io/products/regional-solutions/card-not-present-verification/index.md): Validate that the person completing a card-not-present transaction is the legitimate credit card holder via facial biometrics and card ownership.
- Capabilities
  - [1:1 Validation](https://developer.unico.io/capabilities/1-1-validation.md): Capability that confirms the current face is the same one used in a reference process. Typical of transactional flows.
  - [Age Verification](https://developer.unico.io/capabilities/age-verification.md): Capability that determines whether the person in front of the camera is of legal age, based on biometric analysis.
  - [Document Reuse and Capture](https://developer.unico.io/capabilities/document-reuse-and-capture.md): Capability that requests, stores, and reuses documents. Reduces friction in journeys with document capture by offering classification, OCR, FaceMatch, and CPF Match.
  - [Human Token](https://developer.unico.io/capabilities/human-token.md): Derives a stable, opaque personId from a selfie — identity is the output of the call, not the input. No identifier is declared by the user.
  - [Identity Verification](https://developer.unico.io/capabilities/identity-verification.md): Capability that verifies the captured face belongs to the holder of the identification document.
  - [Liveness](https://developer.unico.io/capabilities/liveness.md): Capability that verifies the user is real and alive at the moment of selfie capture. The biometric anchor of nearly every IDCloud flow.
  - [Multi Accounts](https://developer.unico.io/capabilities/multi-accounts.md): Performs a 1:N biometric search against the operator's base to detect whether a face is already linked to another active account.
  - [Fraud Risk Classification](https://developer.unico.io/capabilities/fraud-risk-classification.md): Detects behavioral anomalies and identity fraud with network effect by evaluating the transaction in the temporal dimension.
  - [Risk Score](https://developer.unico.io/capabilities/risk-score.md): Capability that generates a probabilistic fraud score, used together with Identity Verification when the result is "inconclusive".
  - [Serpro Similarity Return](https://developer.unico.io/capabilities/serpro-similarity-return.md): Capability specific to payroll loans (INSS) and operations that require comparison against the Serpro database. Returns a similarity score between the captured selfie and the photo on file at Serpro.
  - [Smart Revalidation](https://developer.unico.io/capabilities/smart-revalidation.md): Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.
  - [Cardholder Verification](https://developer.unico.io/capabilities/cardholder-verification.md): Capability that confirms a card belongs to its declared holder by reusing a previously validated process together with the person's CPF and card data.
  - [Available flows](https://developer.unico.io/capabilities/available-flows.md): Full catalog of pre-composed flows on the IDCloud platform — each a ready-made capability combination sent in the `flow` field of POST /v1/process.
- Resources
  - [Glossary](https://developer.unico.io/resources/glossary.md): Glossary of terms used in the IDCloud documentation — biometrics, liveness, processes, tokens, and key concepts.
  - [FAQ](https://developer.unico.io/resources/faq.md): Frequently asked questions about IDCloud — integration, authentication, error codes, and supported platforms.
  - [Backtests](https://developer.unico.io/resources/backtests.md): Run historical simulations to evaluate capability performance against past data.
  - [Reprocessing and Biometric Base Import](https://developer.unico.io/resources/reprocessing.md): Guide for reprocessing biometric records or importing a biometric base into the Unico platform.

## Developers

- [API Reference](https://developer.unico.io/developers/api-reference.md): Reference for the IDCloud APIs — two public contracts (Web & SDK and API).
  - [Authentication](https://developer.unico.io/developers/api-reference/authentication.md): OAuth2 JWT Bearer flow used by all IDCloud contracts. Learn how to obtain credentials, build the JWT assertion, and exchange it for an access token.
  - [Environments](https://developer.unico.io/developers/api-reference/environments.md): Sandbox and production hosts across Web & SDK, API, and Magic Link Mexico contracts.
  - [Web & Native](https://developer.unico.io/developers/api-reference/web-sdk.md): Used when biometric capture is hosted by Unico (iFrame, Redirect, or native SDK).
    - [Create Process](https://developer.unico.io/developers/api-reference/web-sdk/post-process.md): Create a verification process. Returns a journey URL and SDK tokens that hand the user off to the Unico-hosted capture experience.
    - [Get Process](https://developer.unico.io/developers/api-reference/web-sdk/get-process.md): Retrieve the current state and result of a verification process.
    - [Flows](https://developer.unico.io/developers/api-reference/web-sdk/flows.md): Catalog of capability recipes available for the Web SDK, grouped by product, and the result values each one can return.
    - [Set Process Document](https://developer.unico.io/developers/api-reference/web-sdk/post-process-document.md): Set the identification document on a process created without one. Triggers capabilities that require a document.
    - [Get Selfie](https://developer.unico.io/developers/api-reference/web-sdk/get-selfie.md): Retrieve the watermarked selfie captured during the verification journey.
    - [Get Evidence Set](https://developer.unico.io/developers/api-reference/web-sdk/get-evidence-set.md): Retrieve the full capture evidence bundle for a process — used for compliance and regulatory auditing.
  - [API](https://developer.unico.io/developers/api-reference/api.md): TCA / Check.Integration contract — used when the client controls capture and sends the image directly in the request.
    - [Create Process](https://developer.unico.io/developers/api-reference/api/post-processes.md): Create a verification process by sending the captured image directly. Returns a synchronous result.
    - [Get Process](https://developer.unico.io/developers/api-reference/api/get-process.md): Retrieve an existing API-contract process by its identifier. Used for re-queries since results are returned synchronously on creation.
    - [Flows](https://developer.unico.io/developers/api-reference/api/flows.md): Catalog of capability recipes available for the API contract, grouped by product, and the result values each one can return.
    - [Get Reusable Documents](https://developer.unico.io/developers/api-reference/api/get-document.md): Check whether a user already has a reusable document on file before starting a new capture flow.
    - [Create Document Process](https://developer.unico.io/developers/api-reference/api/post-processes-document.md): Capture a new document or reuse a previously captured one linked to a biometric process.
    - [Data Verification](https://developer.unico.io/developers/api-reference/api/get-lists.md): Query registration data, PEP/AML screening and sports relationship for a given CPF.
    - [Age Verification](https://developer.unico.io/developers/api-reference/api/post-processes-age-validation.md): Create an Age Verification process. Optionally combines liveness detection and identity verification in a single request.
  - [SSO / SAML](https://developer.unico.io/developers/api-reference/sso-saml.md): Set up Single Sign-On via SAML so your users authenticate with your company's own identity provider instead of individual Unico credentials.
  - [Error codes](https://developer.unico.io/developers/api-reference/error-codes.md): Consolidated catalog of HTTP and platform error codes across Web & SDK, API, and Magic Link contracts.
  - [Rate limits](https://developer.unico.io/developers/api-reference/rate-limits.md): Per-contract rate limits, the Retry-After header, and patterns for staying within budget.
  - [Postman Collection](https://developer.unico.io/developers/api-reference/postman.md): Ready-to-use Postman collections for the Authentication, Web & SDK, and API contracts.
- [SDKs and Tools](https://developer.unico.io/developers/sdks-and-tools/overview.md): Overview of IDCloud SDKs and integration tools — Web SDK, Android SDK, iOS SDK, Flutter SDK, and REST API.
  - [Android SDK](https://developer.unico.io/developers/sdks-and-tools/android/requirements.md): Minimum Android version, Kotlin version, Gradle/Studio requirements, and permissions needed to integrate the Unico Android SDK.
    - [Installation](https://developer.unico.io/developers/sdks-and-tools/android/installation.md): To configure the SDK in your project, follow these steps:
      - [Specific setup](https://developer.unico.io/developers/sdks-and-tools/android/installation/specific-setup.md): SDK Key
    - [Initialization](https://developer.unico.io/developers/sdks-and-tools/android/initialization.md): Initialize the SDK on application load — typically in the Application class or in the onCreate of your entry Activity. SDK authentication with the backend takes a few seconds, so initializing early avoids lag between the user tapping the capture button and the camera opening. See Best practices for more details.
    - Capture flow
      - Capture types
        - [Liveness (biometric selfie)](https://developer.unico.io/developers/sdks-and-tools/android/capture-flow/capture-types/liveness.md): Biometric selfie capture with embedded liveness verification. The SDK guides the user until a biometrically valid frame is obtained via SmartFrames and returns the image as Base64 + JWT (JSON Web Token — a signed payload sent to your backend to call the REST API).
        - [User Journeys](https://developer.unico.io/developers/sdks-and-tools/android/capture-flow/capture-types/user-journeys.md): Multi-step capture sessions orchestrated by the SDK based on the configured flow, such as selfie, document capture, and signature in a single session.
        - [Silent Revalidation](https://developer.unico.io/developers/sdks-and-tools/android/capture-flow/capture-types/silent-revalidation.md): Uses the Silent Revalidation engine, which analyzes the user's behavioral context within Unico's network effect and delivers the confidence signal for the current transaction. In other words, we deliver the confidence level of being the expected user in the transaction.
      - [Receiving the result](https://developer.unico.io/developers/sdks-and-tools/android/capture-flow/receiving-the-result.md): The SDK returns the capture result through callbacks defined in the listener interface used during the capture session.
    - [Customization](https://developer.unico.io/developers/sdks-and-tools/android/customization.md): These customizations are only available when the capture flow is document-capture or liveness.
    - [Error handling](https://developer.unico.io/developers/sdks-and-tools/android/error-handling.md): All error handling for the Android SDK is centralized in this section. The onErrorAcessoBio callback receives an ErrorBio object with code (Int) and description (String).
    - API Reference
      - [Initialization API](https://developer.unico.io/developers/sdks-and-tools/android/api-reference/initialization-api.md): | Class | Description |
      - [Capture API](https://developer.unico.io/developers/sdks-and-tools/android/api-reference/capture-api.md): Call these methods on the UnicoCheckCamera interface obtained from the SDK builder. After preparation, the CameraListener.onCameraReady(cameraOpener) callback provides the opener to start capture.
      - [Callback / Listener interfaces](https://developer.unico.io/developers/sdks-and-tools/android/api-reference/callback-listener-interfaces.md): Lifecycle callbacks for the SDK session. Pass an implementation to the AcessoBio constructor.
      - [Customization API](https://developer.unico.io/developers/sdks-and-tools/android/api-reference/customization-api.md): Pass your theme implementation to the builder using setTheme():
      - [Enums](https://developer.unico.io/developers/sdks-and-tools/android/api-reference/enums.md): Defines the type of document to be captured. Passed to prepareDocumentCamera to configure the capture session.
    - [Resources](https://developer.unico.io/developers/sdks-and-tools/android/resources.md): Best practices and official sample apps (PoCs) for integrating the Unico Android SDK, covering Liveness and User Journeys flows.
      - [Known issues](https://developer.unico.io/developers/sdks-and-tools/android/resources/known-issues.md): - Release build fails but debug works — likely an obfuscation issue. Review ProGuard/DexGuard rules.
      - [Release Notes](https://developer.unico.io/developers/sdks-and-tools/android/resources/release-notes.md): Changelog for the Unico Android SDK — version history, new features, bug fixes, and upgrade notes.
  - [iOS SDK](https://developer.unico.io/developers/sdks-and-tools/ios/requirements.md): Minimum iOS version, Xcode version, dependency manager, and permissions needed to integrate the Unico iOS SDK.
    - [Installation](https://developer.unico.io/developers/sdks-and-tools/ios/installation.md): Step 1 — Add the SDK dependency
      - [Specific setup](https://developer.unico.io/developers/sdks-and-tools/ios/installation/specific-setup.md): SDK Key
    - [Initialization](https://developer.unico.io/developers/sdks-and-tools/ios/initialization.md): Implement the AcessoBioConfigDataSource protocol in your class:
    - Capture flow
      - Capture types
        - [Liveness (biometric selfie)](https://developer.unico.io/developers/sdks-and-tools/ios/capture-flow/capture-types/liveness.md): Biometric selfie capture with embedded liveness verification, returning the captured frame as Base64 and JWT.
        - [User Journeys](https://developer.unico.io/developers/sdks-and-tools/ios/capture-flow/capture-types/user-journeys.md): Multi-step capture sessions orchestrated by the SDK based on the configured flow, such as selfie, document capture, and signature in a single session.
        - [Silent Revalidation](https://developer.unico.io/developers/sdks-and-tools/ios/capture-flow/capture-types/silent-revalidation.md): Uses the Silent Revalidation engine, which analyzes the user's behavioral context within Unico's network effect and delivers the confidence signal for the current transaction. In other words, we deliver the confidence level of being the expected user in the transaction.
      - [Receiving the result](https://developer.unico.io/developers/sdks-and-tools/ios/capture-flow/receiving-the-result.md): The SDK returns the capture result through callbacks defined in the delegate interfaces used during the capture session.
    - [Customization](https://developer.unico.io/developers/sdks-and-tools/ios/customization.md): These customizations are only available when the capture flow is document-capture or liveness.
    - [Error handling](https://developer.unico.io/developers/sdks-and-tools/ios/error-handling.md): All error handling for the iOS SDK is centralized in this section. The onErrorAcessoBioManager callback receives an ErrorBio object exposing getCode() and getDescription().
    - API Reference
      - [Initialization API](https://developer.unico.io/developers/sdks-and-tools/ios/api-reference/initialization-api.md): | Class | Description |
      - [Capture API](https://developer.unico.io/developers/sdks-and-tools/ios/api-reference/capture-api.md): | Method | Description |
      - [Callback / Listener interfaces](https://developer.unico.io/developers/sdks-and-tools/ios/api-reference/callback-listener-interfaces.md): | Method | Trigger |
      - [Customization API](https://developer.unico.io/developers/sdks-and-tools/ios/api-reference/customization-api.md): | Method | Description |
      - [Enums](https://developer.unico.io/developers/sdks-and-tools/ios/api-reference/enums.md): Defines the type of document to be captured. Passed to openDocument to configure the capture session.
    - [Resources](https://developer.unico.io/developers/sdks-and-tools/ios/resources.md): Best practices and official sample apps (PoCs) for integrating the Unico iOS SDK, covering Liveness and User Journeys flows.
      - [Known issues](https://developer.unico.io/developers/sdks-and-tools/ios/resources/known-issues.md): - Shadow at end of flow — flow control is delegated to the SDK caller. If a shadow appears or the screen does not close after a successful capture, implement a release inside onSuccessSelfie:
      - [Release Notes](https://developer.unico.io/developers/sdks-and-tools/ios/resources/release-notes.md): Changelog for the Unico iOS SDK — version history, new features, bug fixes, and upgrade notes.
  - [Flutter SDK](https://developer.unico.io/developers/sdks-and-tools/flutter/requirements.md): Requirements to integrate the Unico Flutter plugin, including Android/iOS prerequisites, permissions, and supported devices.
    - [Installation](https://developer.unico.io/developers/sdks-and-tools/flutter/installation.md): To set up the Unico SDK for Flutter, follow the steps below:
      - [Specific setup](https://developer.unico.io/developers/sdks-and-tools/flutter/installation/specific-setup.md): SDK Key
    - [Initialization](https://developer.unico.io/developers/sdks-and-tools/flutter/initialization.md): Initialize the SDK on application load — typically in main() or in initState() of your entry widget. See Best practices for details on why you should not initialize on the capture button click.
    - Capture flow
      - Capture types
        - [Liveness (biometric selfie)](https://developer.unico.io/developers/sdks-and-tools/flutter/capture-flow/capture-types/liveness.md): Biometric selfie capture with embedded liveness verification. The SDK guides the user until a biometrically valid frame is obtained via SmartFrames and returns the image as Base64 + JWT.
        - [User Journeys](https://developer.unico.io/developers/sdks-and-tools/flutter/capture-flow/capture-types/user-journeys.md): Multi-step capture sessions orchestrated by the SDK based on the configured flow, such as selfie, document, and signature in a single session.
        - [Silent Revalidation](https://developer.unico.io/developers/sdks-and-tools/flutter/capture-flow/capture-types/silent-revalidation.md): Uses the Silent Revalidation engine, which analyzes the user's behavioral context within Unico's network effect and delivers the confidence signal for the current transaction. In other words, we deliver the confidence level of being the expected user in the transaction.
      - [Receiving the result](https://developer.unico.io/developers/sdks-and-tools/flutter/capture-flow/receiving-the-result.md): The SDK returns the capture result through callbacks defined in the listener interface used during the capture session.
    - [Customization](https://developer.unico.io/developers/sdks-and-tools/flutter/customization.md): These customizations are only available when the capture flow is document-capture or liveness.
    - [Error handling](https://developer.unico.io/developers/sdks-and-tools/flutter/error-handling.md): All error handling for the Flutter SDK is centralized in this section. The onErrorUnico, onErrorSelfie, and onErrorDocument callbacks receive a UnicoError object exposing getCode() and getDescription().
    - API Reference
      - [Initialization API](https://developer.unico.io/developers/sdks-and-tools/flutter/api-reference/initialization-api.md): | Class | Description |
      - [Capture API](https://developer.unico.io/developers/sdks-and-tools/flutter/api-reference/capture-api.md): | Method | Description |
      - [Callback / Listener interfaces](https://developer.unico.io/developers/sdks-and-tools/flutter/api-reference/callback-listener-interfaces.md): | Method | Trigger |
      - [Customization API](https://developer.unico.io/developers/sdks-and-tools/flutter/api-reference/customization-api.md): | Method | Description |
      - [Enums](https://developer.unico.io/developers/sdks-and-tools/flutter/api-reference/enums.md): Defines the type of document to be captured. Passed to openCameraDocument to configure the capture session.
    - [Resources](https://developer.unico.io/developers/sdks-and-tools/flutter/resources.md): Best practices and official sample apps (PoCs) for integrating the Unico Flutter plugin, covering Liveness and User Journeys flows.
      - [Known issues](https://developer.unico.io/developers/sdks-and-tools/flutter/resources/known-issues.md): - Release build fails but debug works — likely an obfuscation issue on the Android side. The native SDKs cannot be obfuscated. Review ProGuard/DexGuard rules.
      - [Release Notes](https://developer.unico.io/developers/sdks-and-tools/flutter/resources/release-notes.md): Changelog for the Unico Flutter SDK — version history, new features, bug fixes, and native Android and iOS SDK updates.
  - [Web Integration](https://developer.unico.io/developers/sdks-and-tools/web.md): Client-side integration options for the Web & SDK contract — redirect flows, iFrame SDK, and the JavaScript capture library.
    - [Web SDK](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/requirements.md): Supported browsers, WebView compatibility, and social media webview requirements for the Unico Web SDK.
      - [Installation](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/installation.md): Configure the CSP, install the Web SDK package, and download the resource files required for liveness capture.
        - [Specific setup](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/installation/specific-setup.md): SDK Key
      - [Initialization](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/initialization.md): Initialize the SDK as early as possible — typically when the page or component containing the capture frame loads. See Best practices for details on why you should not initialize on the capture button click.
      - Capture flow
        - Capture types
          - [Liveness (biometric selfie)](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/capture-flow/capture-types/liveness.md): Biometric selfie capture with embedded liveness verification. The SDK guides the user until a biometrically valid frame is obtained via SmartFrames and returns the image as Base64 + JWT.
          - [Document capture](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/capture-flow/capture-types/document-capture.md): Capture of identity documents. The SDK presents a frame to assist the user in positioning the document; after positioning, the user clicks the button to capture the photo.
        - [Receiving the result](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/capture-flow/receiving-the-result.md): The SDK returns the capture result through the callback object passed to open(). Both success and error handlers are mandatory.
        - [Monitoring Data Collection](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/capture-flow/monitoring-data-collection.md): Optional metadata you can attach to any capture session to identify the user and flow in monitoring and observability tools.
      - [Customization](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/customization.md): The Web SDK supports two dimensions of customization: language and visual theme.
      - [Error handling](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/error-handling.md): All error handling for the Web SDK is centralized in this section. The error callback receives an ErrorBio object exposing getCode() and getDescription().
      - [Accessibility](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/accessibility.md): The SDK implements components prepared with HTML attributes for accessibility — aria-label, tabindex, role, among others — which enable keyboard navigation between elements, activate audio guidance, and are used by screen reader software.
      - API Reference
        - [Initialization API](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/api-reference/initialization-api.md): | Class | Description |
        - [Capture API](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/api-reference/capture-api.md): | Method | Description |
        - [Callback / Listener interfaces](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/api-reference/callback-listener-interfaces.md): The Web SDK uses a single callback object passed to open() instead of platform-specific listener interfaces.
        - [Customization API](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/api-reference/customization-api.md): | Method | Description |
        - [Enums](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/api-reference/enums.md): Defines the camera mode for selfie capture. Passed to prepareSelfieCamera.
      - [Resources](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/resources.md): - Initialize the SDK on page load, not on the capture button click. Authentication with the backend takes a few seconds and, if done together with the camera opening, creates a perception of lag.
        - [Known issues](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/resources/known-issues.md): - CSP blocks SDK loading — without the required CSP directives (worker-src, script-src, etc.), the Web SDK fails to load Web Workers and additional resources. Review the CSP configuration.
        - [Release Notes](https://developer.unico.io/developers/sdks-and-tools/web/web-sdk/resources/release-notes.md): Changelog for the Unico Web SDK — version history, new features, bug fixes, and upgrade notes.
    - [Web App Integration](https://developer.unico.io/developers/sdks-and-tools/web/web-integration.md): How to integrate the Web & SDK contract on the client side — redirect flows and iFrame SDK setup.
      - [Resources](https://developer.unico.io/developers/sdks-and-tools/web/web-integration/resources.md): Best practices and release notes for integrating with the Unico Web App Integration SDK (unico-journey-sdk).
        - [Release Notes](https://developer.unico.io/developers/sdks-and-tools/web/web-integration/resources/release-notes.md): Changelog for the Unico Web App Integration SDK (unico-journey-sdk) — version history, new features, and upgrade notes.
  - [Capture Standard](https://developer.unico.io/developers/sdks-and-tools/capture-standard.md): For optimal performance of the IDCloud platform's capabilities, we recommend using our SDKs (Web, Android, iOS, Flutter). They ensure the best functioning of the product as a whole, both in terms of drop rate and in validating the Liveness.
  - [Best Practices](https://developer.unico.io/developers/sdks-and-tools/best-practices-for-sdk-implementation.md): Guidelines for integrating, updating, testing, and safely rolling out Unico's SDKs, including staging (UAT) security rules.
  - [Update Policy](https://developer.unico.io/developers/sdks-and-tools/update-policy.md): Unico's SDK update policy: why it exists, the minimum timelines clients must meet, and how to stay supported and protected.
- [Webhooks and Events](https://developer.unico.io/developers/webhooks-and-events.md): Introduction to IDCloud webhooks — receive real-time notifications for identity verification process events.
  - [Setup](https://developer.unico.io/developers/webhooks-and-events/setup.md): Step-by-step guide to configuring IDCloud webhooks — portal self-service for Web and SDK, and by-client configuration for API integrations using Check orchestration (Brazil only).
  - [Event types](https://developer.unico.io/developers/webhooks-and-events/event-types.md): Reference for IDCloud webhook event types — process completed, failed, and status change payloads.
  - [Security](https://developer.unico.io/developers/webhooks-and-events/security.md): How to validate and secure IDCloud webhook payloads — signature verification and best practices.
  - [Fallback Strategy](https://developer.unico.io/developers/webhooks-and-events/fallback.md): How to retrieve process results when the webhook service is temporarily unavailable.
- [AI Agent Integration](https://developer.unico.io/developers/llms.md): Read this documentation from AI agents and LLM tools with a Markdown version of every page, a per-language llms.txt index and the page actions bar.
- Regional Solutions
  - [Card Not Present Verification](https://developer.unico.io/developers/regional-solutions/card-not-present-verification.md): Card Not Present Verification REST API documentation — combine shopper identification and credit card holder validation in payment transactions.
    - About Card Not Present Verification
      - [What is Card Not Present Verification](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/about-idpay/unico-id-pay.md): What Card Not Present Verification is and the guarantees it provides for payment transactions: liveness, card holder identity match, and liability protection.
      - [Feature](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/about-idpay/feature.md): Card Not Present Verification's core features: Payment Transactions and Credit Card Onboarding, and how they differ.
      - [Use Cases](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/about-idpay/use-cases.md): Use cases for Card Not Present Verification across checkout, pre-analysis, analysis tooling, sales recovery, and credit card onboarding.
      - [Chargeback](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/about-idpay/chargeback.md): Unico's chargeback liability guarantee for Card Not Present Verification validations: when it applies, prerequisites, and exclusions.
    - [Integration](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/overview.md): Step-by-step integration overview for Card Not Present Verification: authenticate, customize the experience, create a transaction, and handle the webhook notification.
      - [Authentication](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication.md): Card Not Present Verification uses OAuth2 service-account (two-legged) authentication to issue access tokens for the REST API.
        - [Creating a Service Account](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/creating-a-service-account.md): How to request a service account for server-to-server Card Not Present Verification authentication, including key pair generation.
        - [Preparing to make an authenticated request to the API](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/preparing-authenticated-request.md): How to build and sign the JWT, request an access token from the OAuth2 platform, and handle the token response and expiration.
        - [Additional resources](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/additional-resources.md): Supporting resources for Card Not Present Verification authentication: a JavaScript implementation example, authentication error codes, and the Postman collection.
          - [Example in JavaScript](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/additional-resources/example-in-javascript.md): Reference JavaScript implementation for building and signing the JWT and requesting a Card Not Present Verification access token.
          - [Authentication Errors](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/additional-resources/authentication-errors.md): Error codes returned by the Card Not Present Verification OAuth2 authentication platform and how to resolve each one.
          - [Postman Collection](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/authentication/additional-resources/postman-collection.md): Ready-to-use Postman collection for the Card Not Present Verification REST API: payment transactions, chargeback, and credit card onboarding.
      - [APIs](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis.md): All available REST endpoints for the Card Not Present Verification product: API Reference, Errors, and Enumerated values.
        - [API Reference](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference.md): Endpoint reference for the Card Not Present Verification REST API: payment transactions, chargeback, credit card onboarding, and context signals.
          - [Payment transactions](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference/payment-transactions.md): REST API reference for creating payment transactions, checking status, retrieving evidence, and resending notifications in Card Not Present Verification.
          - [Chargeback](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference/chargeback.md): REST API reference for requesting a chargeback review and checking its status in Card Not Present Verification.
          - [Credit card Onboarding](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference/credit-card-onboarding.md): REST API reference for validating a credit card and checking validation status in Card Not Present Verification's Credit card Onboarding feature.
          - [Context signals](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/api-reference/context-signals.md): REST API reference for the fraud risk assessment (self-fraud or social engineering) of a completed credit transaction in Card Not Present Verification.
        - [Errors](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/errors.md): Overview of HTTP status codes and error responses returned by the Card Not Present Verification REST API endpoints.
        - [Enumerated](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/apis/enumerated.md): Enumerations used across the Card Not Present Verification REST API: transaction result codes and chargeback result codes.
      - [Webhook](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/webhook.md): How to configure and receive Card Not Present Verification webhook notifications, including request/response format and important considerations like rate limits and idempotence.
      - [Controlling the experience](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/overview.md): How the Card Not Present Verification SDK integration works — Webview, SDK, and Redirect standards, and the API steps needed before integrating in your application.
        - [Requirements](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/requirements.md): Minimum OS versions and browser/OS compatibility matrix for the Card Not Present Verification SDK capture frame.
        - Mobile
          - [Android](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/mobile/android.md): Managing the Card Not Present Verification capture experience in Android via CustomTabs: dependency, opening the tab, manifest configuration, and reading the callback.
          - [iOS](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/mobile/ios.md): Two recommended approaches for managing the Card Not Present Verification capture experience on iOS: WKWebView and ASWebAuthenticationSession.
            - [WKWebView](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/mobile/ios/wkwebview.md): How to implement the Card Not Present Verification capture experience on iOS using WKWebView: opening the view, controlling when to close it, and required permissions.
            - [ASWebAuthenticationSession](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/mobile/ios/aswebauthenticationsession.md): How to implement the Card Not Present Verification capture experience on iOS using ASWebAuthenticationSession: authentication controller, session setup, and required permissions.
          - [Flutter](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/mobile/flutter.md): Managing the Card Not Present Verification capture experience in Flutter via inappwebview: opening the webview, monitoring URL changes, and camera permission.
        - Web
          - [SDK](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/web/sdk.md): How to implement the Unico SDK for web: installation, init/open methods, full-screen guidance, and the iFrame + auth token security model.
          - [Redirect (deprecated)](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/controlling-the-experience/web/redirect-deprecated.md): Deprecated web integration models for Card Not Present Verification: window.open() and full-page redirect. Prefer the SDK for better conversion.
      - [Customizations](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/customizations.md): Logo, button color, and shape customization options for the Card Not Present Verification experience, with accessibility contrast recommendations.
      - [Silent Verification](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/integration/silent-verification.md): Enable background verification for returning users in Card Not Present Verification, using signals and recurrence to approve transactions silently.
    - Help & FAQ
      - [Best communication practices](https://developer.unico.io/developers/regional-solutions/card-not-present-verification/help-and-faq/best-communication-practices.md): Tips for communicating Card Not Present Verification's biometric identity validation to your end users, to reduce friction and support tickets.

## Product Guide

- [Product Guide](https://developer.unico.io/product-guide.md): Operating manuals for Unico products — how to use every screen, every field, and every setting, step by step.
- [IDCloud Portal](https://developer.unico.io/product-guide/portal-idcloud.md): Operating guides for the IDCloud Portal — configure your customer's experience, the notifications to your system, and QR Code validation.
  - Settings
    - [Journey Customization](https://developer.unico.io/product-guide/portal-idcloud/settings/journey-customization.md): Configure the journey's visual identity — logo, colors, background, and button shape — directly in the IDCloud Portal, with a real-time preview.
    - [Webhook](https://developer.unico.io/product-guide/portal-idcloud/settings/webhook.md): Configure where IDCloud notifies your system when a journey changes state, how it authenticates against your API, and what happens when your API doesn't respond.
    - [QR Code](https://developer.unico.io/product-guide/portal-idcloud/settings/qr-code.md): Enable QR Code display in the validation journey so your customer can start on desktop and continue on mobile, directly from the IDCloud Portal.