KYB Mandate with E-Signature

This guide walks you through creating a journey that collects signer identity information, verifies their identity document, gathers company details, and generates a mandate PDF for electronic signature — a typical KYB (Know Your Business) workflow with e-signature.

---

What you'll build

An 8-step journey (with conditional branching):

---

Step-by-step setup

1. Create a new journey

1. Go to Journey Builder in the left sidebar.
2. Click "New journey" to create a new journey.
3. Give it a name (e.g. "KYB — Mandate with E-Signature").

2. Configure the Start node

Click the Start node and customise the welcome screen. Explain that users will need:

• A valid identity document (ID card or passport)
• Their company registration details
• If applicable, a list of subsidiaries covered by the mandate

For more details, see Start step.

3. Add an Identity Information step

Add an Identity Information step configured for a natural person. Collect the signer's:

• First name and Last name
• Date of birth
• Nationality
• Email address (used later for the electronic signature)

This step identifies the person who will sign the mandate.

For more details, see Identity Information step.

4. Add an Identity Document Check step

Add an Identity Document Check step to verify the signer's identity.

Configure accepted document types based on your requirements (ID cards, passports, residence permits). The AI will extract data and run fraud checks, then cross-reference with the information provided in the previous step.

For more details, see Identity Document Check step.

5. Add a Custom Form for company information

Add a Custom Form step to collect the signing company's details. Configure the form with the following fields:

• Company name (text)
• Registration number (text — SIREN/SIRET or equivalent)
• Company address (text)
• Mandate scope (choices enumeration) — with the following options:
  • Single company
  • Multiple subsidiaries

The Mandate scope field determines whether the user needs to provide subsidiary details in the next step.

For more details, see Custom Form step.

6. Add a Condition node

Add a Condition node to branch the journey based on the mandate scope selection.

Configure the condition:

• Field: Mandate scope (from the previous Custom Form step)
• Operator: equals
• Value: Multiple subsidiaries

This creates two branches:

• TRUE branch → the user provides subsidiary details (next step)
• FALSE branch → skip directly to PDF generation

For more details, see Condition step.

7. Add a Custom Form for subsidiaries (TRUE branch)

On the TRUE branch of the condition, add a second Custom Form step. Configure it with a table input that allows the user to add multiple rows. Each row should capture:

• Subsidiary name (text)
• Registration number (text)
• Country (text)
• Address (text)

Enable the option to add multiple rows so that all subsidiaries covered by the mandate can be listed.

For more details, see Custom Form step.

8. Add a PDF Generation step

After both branches converge, add a PDF Generation step. Configure it with an HTML template that includes fields from the previous steps:

• Signer details: first name, last name, date of birth, nationality
• Company details: company name, registration number, address
• Mandate scope: single company or multiple subsidiaries
• Subsidiaries table (if applicable): rendered as a table listing each subsidiary's name, registration number, country, and address

Design the HTML template to produce a professional mandate document ready for signature.

For more details, see PDF Generation step.

9. Add an Electronic Signature step

Add an Electronic Signature step linked to the PDF generated in the previous step. The signer will receive the mandate document and sign it electronically.

For more details, see Electronic Signature step.

10. Configure the End step, Save and Test

Configure the End node with a confirmation message, then click "Save and test" to test the journey.

You can also test it by creating a session from Analysis → By session.

For more details, see End step.

---

What happens next

Once a user completes the journey:

• The signer's identity and document verification results are available in the back office
• The signed mandate PDF is stored and accessible for download
• If subsidiaries were provided, they appear in the mandate document as a detailed table
• You can review each step individually and approve or reject the session

See Journey Sessions (Back Office) and Analytics for details on reviewing results.