You need a contract with Become Digital. What you can use depends on the products it includes.
What you can do
Verify identity
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.
Face authentication
Confirms that whoever is writing is the same person who was already verified, with just a selfie.
Watchlists (AML)
Checks whether a person appears on restrictive lists.
National registry and Migration
Checks the status of a Colombian ID or Migración Colombia documents.
Connect it
Follow the steps in Integrations. 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.
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.completedevent 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”.