This guide explains how to integrate Ondorse into your existing prospects and clients management workflows. It covers integrations with:

CRMs such as Salesforce and HubSpot
Back-office operations management systems
Customer-facing web and mobile applications

ℹ️
Our approach to integration
We don't provide native integrations with CRMs like Salesforce or HubSpot.
Indeed, we've learned that every organisation has unique compliance workflows and CRM configurations and that one-size-fits-all native integrations always and inevitably fall short because they can't address specific needs.
Instead, we encourage and assist you in building the exact integration you need. No developer resources are required: you can use very popular no-code tools on the market (like Zapier, that your team is maybe already using) or use the ones already included in your CRM (Salesforce MuleSoft).
Our team works closely with you throughout the integration process, providing guidance. We can also put you in contact with experienced Ondorse partners that will build the integration for you.

Ondorse functional overview

Ondorse is a platform that orchestrates the verification process (KYC) of your client (businesses or natural persons) in order to:

complete a client compliance profile
make a compliance decision wether to onboard this client or not

The client is deemed verified from a compliance perspective when a compliance decision is output.

In this process, elements can be prompted from the client using a white-labeled client-facing interface provided by Ondorse, called a portal.

In Ondorse, a client record corresponds to case. The case holds the whole compliance profile of the client which includes documents, attributes, verification points, risk profile and more.

Data model

Object in Ondorse	Description	Reference
Case	The case holds the whole compliance profile of the client which includes: fields and custom fields: name, registration number, etc.. documents risks and risk level treatment status and decision It corresponds to a Client record in your system.	Also called "Application"
Portal	For a given case, a hosted customer-facing web page to collect data from the client.
Relationships: persons and business	For a given case, represents natural and legal persons related to this case. It holds their information and their relationships between each other.
Workflow and tasks	Tasks are units of verification performed on a case. Workflow is a set of task that should be performed a case before a decision is made on the case.	Tasks

Integration outline

Integration types

In our experience, we've encountered 5 types of integration of Ondorse:

Integration	Description	Best for	Integration time required
No integration	Ondorse works without any integration. Cases are created by sales or ops team and decision are reported manually.	Simple use-cases, with low volume, proof-of-concept phase..	0
CRM integration	Ondorse is integrated in the workflow of a CRM (eg. Salesforce). The collect of client information for compliance is achieved using portal.	Sales teams already using a CRM, white-glove or managed onboarding [1]	1 week - 3 weeks
In-app integration	You have a customer-facing application and Ondorse is integrated in this application: portal is part of the customer's onboarding flow.	Fintechs with an in-app self-serve onboarding	1 week - 3 week
Headless integration	You have a customer-facing application. The compliance onboarding is fully managed in this application. You use Ondorse only as a compliance backoffice (case manager).	Teams with developer resources available. ⚠️ we don't recommend this integration	Unknown
CSV import	You use Ondorse import and remediations features to verify an existing clients base.	One-off projects like remediation project, migration or stock recovery. [2]	1 week - 3 week.

[1]: managed onboarding = a dedicated person guides the client through the process.

[2]: We provide dedicated assistance for such projects, please reach out.

Common integration touchpoints

Most integration points and related questions center around these 3 areas:

Input: How does a client record from your system enters Ondorse as a case?
Output: How does a case decision and some parts of the client profile are reported back into your system?
Client prompting: How to integrate portal into your client flow? How does your client access the portal?

ℹ️
Portal or not portal: prompting information from your client during a KYC is inevitable. Ondorse strongly recommends using its portal feature to do so because it makes this process convenient for the client and efficient for your ops team.

With a user-facing web application

In this example integration, the account is created before the KYB verification. Until the KYB verification is done and approved, the account is kept inactive and has limited access to your application (example: wire transfers are disabled).

This design choice have several advantages:

While the KYB verification is pending, the user has already access to your application. You can already build engagement: complete the setup, train the user, etc.
With an account creation as first step of the process, you have more means to contact and re-engage the user in case of drip out.
You can pass down specific information to the KYB case such as: internal references (ex: account_id) or risk data (ex: acquisition channel).

Implementation guidelines

Use the endpoint POST /api/portals (reference) to create a Portal link:
- use the param default_custom_fields to pass custom case data such as account_id etc..
- use the param redirect_url to redirect the user after the submission of the Portal
Use the webhook event application.submitted to be notified when a case is submitted via Portal
- in the payload, you have access to the application_id and custom_fields values (especially the ones coming from default_custom_fields)
Use the endpoint GET /api/applications/{application_id} (reference) to get access to case content
- use the field status_review to know the decision status
- use the fields risk_score and risk_level to get information about the risk scoring
Use the webhook event application.review_updated to be notified when a case gets an update on its status_review
Use the webhook event collect.opened to be notified when a case needs an information from the customer
- Use payload data.object.portals.link to access the link to the collect Portal that you can send to the customer.

With a CRM (e.g., Salesforce)

In this example, we present an integration with Salesforce.