> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choosing Your Integration

> Compare iDenfy API, SDK, iFrame, redirect, and no-code integration methods side by side to find the best approach for your use case.

## Integration Methods at a Glance

| Method         | Best for                | Time to integrate | UI control                | Platform                 |
| -------------- | ----------------------- | ----------------- | ------------------------- | ------------------------ |
| **Redirect**   | Fastest setup           | \~1 hour          | iDenfy-hosted             | Web                      |
| **iFrame**     | Embedded web experience | \~2 hours         | Embedded, limited styling | Web                      |
| **Mobile SDK** | Native mobile apps      | \~1 day           | Full UI customization     | iOS, Android             |
| **Direct API** | Full custom flows       | \~1 week          | Complete control          | Any                      |
| **No-code**    | Non-technical teams     | \~15 minutes      | Plugin-configured         | Shopify, WordPress, etc. |

***

## Decision Tree

<Steps>
  <Step title="Do you have a mobile app?">
    **Yes** → Use the [Mobile SDK](/sdks/overview). It provides native performance, camera access, and liveness detection optimized for mobile.

    **No** → Continue to Step 2.
  </Step>

  <Step title="Do you need custom verification UI?">
    **Yes** → Use the [Direct API](/kyc/direct-processing). You control every screen and interaction. Most complex, but maximum flexibility.

    **No** → Continue to Step 3.
  </Step>

  <Step title="Should verification stay in your site?">
    **Yes** → Use the [iFrame](/kyc/iframe-redirect). Embeds the verification flow in your page. Users never leave your domain.

    **No** → Use the [Redirect](/kyc/iframe-redirect). Simplest option — redirect users to iDenfy's hosted verification page and get results via webhook.
  </Step>
</Steps>

***

## Detailed Comparison

<Tabs>
  <Tab title="Redirect">
    **How it works:** Create a session → redirect user to `redirectUrl` → receive webhook.

    **Pros:**

    * Fastest to implement (one API call)
    * iDenfy handles all UI, camera, liveness
    * Always up to date — no SDK version management
    * Works on any device/browser

    **Cons:**

    * User leaves your site during verification
    * No UI customization
    * Less seamless user experience

    [Redirect documentation →](/kyc/iframe-redirect)
  </Tab>

  <Tab title="iFrame">
    **How it works:** Create a session → embed iFrame with `redirectUrl` → receive webhook.

    **Pros:**

    * User stays on your site
    * Simple implementation
    * Auto-updated UI

    **Cons:**

    * Limited styling (CSS overrides only)
    * Camera permissions can be tricky in iFrames
    * Some browsers restrict third-party iFrame features

    [iFrame documentation →](/kyc/iframe-redirect)
  </Tab>

  <Tab title="Mobile SDK">
    **How it works:** Create session → pass `authToken` to SDK → receive callback + webhook.

    **Pros:**

    * Native camera and NFC access
    * Full UI customization (colors, fonts, screens)
    * Optimized liveness detection
    * Offline capability for some steps

    **Cons:**

    * Requires SDK version management
    * Separate Android/iOS implementations
    * Larger app size (\~15-30MB)

    [Android SDK →](/sdks/android/quickstart) | [iOS SDK →](/sdks/ios/quickstart)
  </Tab>

  <Tab title="Direct API">
    **How it works:** Your app handles document capture → send images via API → receive webhook.

    **Pros:**

    * Complete UI/UX control
    * Works on any platform
    * Can integrate into existing flows

    **Cons:**

    * Most development effort
    * You handle camera, image quality, UX
    * Must implement error handling for all edge cases

    [Direct processing →](/kyc/direct-processing)
  </Tab>

  <Tab title="No-Code">
    **How it works:** Install plugin → configure in admin panel → verification works.

    **Pros:**

    * No coding required
    * Quick setup (minutes)
    * Pre-built for popular platforms

    **Cons:**

    * Limited to supported platforms
    * Less customization
    * Plugin update dependency

    [Integrations →](/integrations/overview)
  </Tab>
</Tabs>