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

# Become Digital

> Verify your customers' identity from your bots and conversations, with ID, selfie and liveness check.

**Become Digital** is an identity verification and compliance partner. With this integration you can ask a customer to verify their identity (a photo of their ID and a selfie with a liveness check) without leaving the conversation, and use the result in your bots, in the CRM and in your reports.

<Note>
  You need a contract with Become Digital. What you can use depends on the products it includes.
</Note>

## What you can do

<CardGroup cols={2}>
  <Card title="Verify identity" icon="id-card">
    The customer takes a photo of their ID and a selfie. Become checks that they match, that it's a real person and that the ID isn't altered.
  </Card>

  <Card title="Face authentication" icon="face-smile">
    Confirms that whoever is writing is the same person who was already verified, with just a selfie.
  </Card>

  <Card title="Watchlists (AML)" icon="shield-halved">
    Checks whether a person appears on restrictive lists.
  </Card>

  <Card title="National registry and Migration" icon="building-columns">
    Checks the status of a Colombian ID or Migración Colombia documents.
  </Card>
</CardGroup>

## Connect it

Follow the steps in [Integrations](/en/integraciones/integraciones). Become gives you a **username and password** (or Client ID and secret) and a **contract number**. After connecting:

* The details page shows the **notification URL**. Send it to Become support so they set it up on your contract: results then arrive within seconds. Without it they still arrive, with up to a one-minute delay.
* You'll see your contract **quota** (verifications used and available).

## Verify a customer

### From a bot

Add the **Verify identity** step to your bot. The bot sends a button with the link, waits for the result and continues through the matching exit: **Approved**, **Human review**, **Rejected**, **Didn't finish** or **Error**.

In the step you can configure:

* The **accepted documents** and country.
* The **decision rules**: from which face match it's approved, and what to do if the ID is altered or expired, if the person is on a watchlist or if another verification with the same face already exists (reject, send to review or ignore).
* The **messages while waiting**: the reminder with the link, the "we're reviewing it" notice when the customer finishes, and the reply if they write while it's being reviewed.
* **If already verified, don't ask again**: the bot continues through "Approved" without using quota.

<Tip>
  Become takes a few minutes to review. The "we're reviewing it" notice (on by default) reassures the customer while they wait.
</Tip>

### From the conversation or the contact profile

On the **Identity verification** card of the profile, press **Request verification** (or **Request face authentication**). In the inbox, the link is placed in your message so you can review and send it; in the CRM it's copied.

## The page your customer sees

The link opens a secure page where your customer completes the verification from their phone. You can customize it on the integration details page with **Customize page**: your logo, a color, titles and texts, the final message and the link to your data privacy policy. Anything left empty uses the default text in the customer's language.

## Results

* **On the contact:** their status shows as **Identity verified**, **Under review** or **Rejected**, next to the name and in the contact list (with column and filter). The card shows the history with name, ID (last 4 digits only), face match and reasons.
* **Human review:** when a verification ends up **Under review**, an agent can **approve or reject it** from the card, giving a reason. Who did it is recorded.
* **In segments and bots:** use the **Identity status** rule in your segments and the `{{contact_identity_status}}` and `{{contact_identity_verified_at}}` variables in your bots and automations.
* **Automations:** the **Identity verification completed** trigger starts an automation when a verification finishes (you can filter by outcome and type).
* **Webhooks:** the `kyc.completed` event notifies your systems when a verification finishes.
* **Report:** in **Analytics → Identity verifications** you see the funnel (sent, opened, finished, with result), outcomes, review and rejection reasons, who requested them, and you can export it to CSV.

## Data and privacy

* ApyConnect stores only the **summary and decision** of each verification. From the ID, only the last 4 digits; never images or biometric data.
* **Retention:** on the integration details page you choose how long that data is kept (1, 2, 5 or 10 years; 5 by default). When it expires it's deleted automatically, keeping the decision and dates for the figures. If it was the contact's current verification, they go back to "Not verified".

<Warning>
  Regulated entities often have record-keeping obligations (for example, SARLAFT in Colombia). Confirm the right period with your legal team.
</Warning>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.