# Getting Started

ComplyCube is a complete identity verification and anti-fraud platform that helps businesses of all sizes automate KYC and AML flows and processes. 

This documentation is your starting point. It will guide you from **setting up your account**, to **understanding our products**, selecting the **integration path** that best fits your needs, and finally running your **first identity verification**.

***

### 1. Create an account

Set up a ComplyCube account and start using our verification services right away in a secure test environment.

<a href="https://portal.complycube.com/signup" class="button primary">Create account</a>   <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/" class="button secondary">Explore all products</a>

{% hint style="success" %}

#### Your sandbox environment

When you create an account, your **sandbox (test) environment** is set up automatically and comes preloaded with:  <br>

* **Sample workflows**: Ready-made templates to explore verification flows. &#x20;
* **Test data**: Pre-populated customers and checks so you can experiment safely. &#x20;
* **Full feature access**: The same functionality as Live, but isolated for testing.  <br>

This allows you to explore the platform, understand how workflows and verification checks operate, and gain hands-on experience before going live.
{% endhint %}

***

### 2. Verification modes

ComplyCube supports **two verification modes**, which determine how checks are executed whether you’re using the Web Portal out of the box or integrating via the Hosted solution, SDKs, or APIs.

<table><thead><tr><th valign="top">Workflow orchestration</th><th valign="top">Check-driven</th></tr></thead><tbody><tr><td valign="top">Define customer journeys in the <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/compliance-studio/workflows#designing-workflows">workflow designer</a> and verify customers through the Portal or your app. Flows can be updated or extended without redeploying, making this the <strong>recommended option for most use cases</strong>. <br><br>Customer participation is <strong>required</strong>. The customer must complete the flow to trigger the verification checks.<br></td><td valign="top">Run individual checks (e.g. <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/watchlist-pep-and-adverse-media/aml-screening-check">AML screening</a>) on an <strong>ad-hoc basis</strong> in the Portal or integrate them into your app. Flexible but more code-intensive, best suited for <strong>advanced</strong> integrations, <strong>partner use cases</strong>, or occasional <strong>one-off verifications</strong>.<br><br>Unlike workflows, checks can be run without direct customer involvement.</td></tr><tr><td valign="top"><p><strong>How it works</strong><br></p><ol><li>Select an existing <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/compliance-studio/workflows#creating-workflows">workflow template</a> or create a new one.</li><li>Each run creates a <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/compliance-studio/workflows#workflow-session">workflow session</a> with all data, documents, and results.  </li><li>Results are returned at the <strong>session level</strong> via Portal, API, or webhooks.</li></ol></td><td valign="top"><p><strong>How it works</strong><br></p><ol><li>Trigger individual checks directly (e.g. <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/watchlist-pep-and-adverse-media/aml-screening-check">AML screening</a>, <a href="https://app.gitbook.com/s/KyFKMqftsmT6qln9zo5y/identity-verification/document-check">document verification</a>).  </li><li>You manage onboarding logic and flow changes in your app code.</li><li>Results are returned per check via the Portal, API, or webhooks.</li></ol></td></tr></tbody></table>

{% hint style="info" %}
You can combine **workflow orchestration** and **check-driven** modes, for example, running a workflow for biometric and document verification, but triggering specific extra checks (e.g. AML screening) on demand.
{% endhint %}

{% hint style="info" %}
Both modes are available directly in the Web Portal, so you can start running checks immediately **without writing code**. The [integration paths](#id-3.-integration-paths) below let you embed these same modes into your own systems.
{% endhint %}

***

### 3. Integration paths

All integrations paths below support both [verification modes](#id-2.-verification-modes).

<table data-header-hidden><thead><tr><th width="213.0625">Path</th><th>Description</th></tr></thead><tbody><tr><td><img src="https://content.gitbook.com/content/sw26JqCBnT6AEIbxAYyk/blobs/4XUI1nR8pToYOaeoqzde/web_portal.svg" alt="" data-size="line"> <a href="quick-guides/web-portal-quick-guide"><mark style="color:blue;"><strong>Web Portal</strong></mark></a></td><td>Run checks and flows directly from the Portal without any integration. Easiest entry point and <strong>ideal for low volumes</strong>.</td></tr><tr><td><img src="https://content.gitbook.com/content/sw26JqCBnT6AEIbxAYyk/blobs/8E9yGJJFsDtxNMXoaZXV/icon-verify-blue.svg" alt="" data-size="line"> <a href="quick-guides/hosted-solution-quick-guide"><mark style="color:blue;"><strong>Hosted Solution</strong></mark></a></td><td>A secure and branded hosted KYC page that enables you to verify clients with minimal code. This is the <strong>quickest integration path</strong>.</td></tr><tr><td><img src="https://content.gitbook.com/content/sw26JqCBnT6AEIbxAYyk/blobs/FVKSG17kJTG8rwuvTvFw/identity_check.svg" alt="" data-size="line"> <a href="quick-guides/mobile-sdk-guide"><mark style="color:blue;"><strong>Mobile SDKs</strong></mark></a></td><td>Embed our mobile SDKs with built-in AI features to run KYC flows <strong>natively</strong> directly inside your app.<br><br>You can test the Mobile SDK immediately using the <a href="integration-resources/complycube-mobile-app">ComplyCube Mobile app</a>, without needing to integrate anything.</td></tr><tr><td><img src="https://content.gitbook.com/content/sw26JqCBnT6AEIbxAYyk/blobs/JeSlE8vIUi7dASssfRaO/web_sdk.svg" alt="" data-size="line"> <a href="quick-guides/web-sdk-quick-guide"><mark style="color:blue;"><strong>Web SDK</strong></mark></a></td><td>Drop in our verification flows directly into your <strong>web application</strong>.</td></tr><tr><td><img src="https://content.gitbook.com/content/sw26JqCBnT6AEIbxAYyk/blobs/IP3802v15UjqOEMsjPS8/api.svg" alt="" data-size="line"> <a href="quick-guides/api-quick-guide"><mark style="color:blue;"><strong>Pure API Integration</strong></mark> </a></td><td>Bring your own UI and connect directly to ComplyCube APIs. Offers <strong>the most granular control</strong> and is suited for <strong>advanced use cases</strong> or <strong>partner implementations</strong>.</td></tr></tbody></table>

***

### 4. Build & test

* [Testing data](https://docs.complycube.com/documentation/integration-resources/testing-data) - Use Sandbox triggers to simulate outcomes.&#x20;
* [Configure webhooks](https://docs.complycube.com/documentation/integration-resources/webhooks) - Receive results asynchronously in real-time.
* [Integration checklist ](https://docs.complycube.com/documentation/integration-resources/integration-checklist)- Follow our checklist to ensure your integration is production-ready.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.complycube.com/documentation/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.