ONP Integration

Overview

The Onboarding Platform (ONP) is the module of the Guardline Suite responsible for conducting customer onboarding journeys. Integrating with ONP lets the institution’s system start journeys programmatically, track progress, and receive the final result with score and decision.

Integration Flow

The typical integration flow with ONP follows these steps:

1. The institution’s system requests the creation of an onboarding, providing the customer’s initial data.
2. ONP returns an identifier and a journey URL for the customer.
3. The customer goes through the journey (document capture, biometrics, data entry).
4. ONP triggers the verification providers configured for the journey (document verification, liveness, facematch, background checks, among others).
5. With the verification results, the scoring engine calculates the score and applies the rules defined by the institution.
6. ONP notifies the institution’s system of the completion via webhook.
7. The institution’s system queries the result (status, score, decision).

Journey Types

ONP supports three types of onboarding journey:

• kyc: identity verification for natural persons (adults). Includes personal data collection, document capture, facial biometrics, and risk analysis.
• kyb: business verification for legal entities. Includes corporate structure validation, identification of beneficial owners, and verification of legal representatives.
• kyc_minor: verification for minors (14 to 17 years old) with a legal representative. The minor completes the journey first, and then the legal representative receives a link via SMS or WhatsApp to complete a simplified verification. The final decision takes the data of both into account.

Verifications and Providers

ONP triggers verification providers according to the journey configuration. Each journey can include different combinations of verifications (facial biometrics, document verification, liveness, facematch, device fingerprint, background checks, OCR) according to the institution’s policy.

When a verification fails or the provider is unavailable, the platform applies a fallback mechanism with three levels:

• Automatic retry: the request is resent to the same provider after a configurable interval.
• Alternative provider: if the retry fails, the verification is redirected to a pre-configured equivalent provider.
• Conditional approval: if no provider responds, the onboarding can be referred to the analysis desk with conditional status, avoiding a block in the flow (the journey is not halted).

More details on the connector architecture are on the partners and connectors page.

Notifications

The institution receives webhook notifications about the main events in the lifecycle of an onboarding: journey start, step completion, verification results, final decision, and expiration. Which events to receive is configured during the integration setup.

All notifications include an HMAC signature for authenticity validation, as described in the integration concepts.