RouteurStable

Has valid compliance check?

Determines whether a company or contact has a sufficiently recent, still-valid compliance check according to an explicit resolution policy.

Company / contact

Has valid compliance check?

Companies & contacts

Typed result

Vue d’ensemble

Determines whether a company or contact has a sufficiently recent, still-valid compliance check according to an explicit resolution policy.

Exemple

Reuse a KYC completed less than three months ago and rerun the provider only when no acceptable check exists.

Decision routes

valid

Valable

The selected strategy concludes that an eligible passed check is sufficient.

Recommended actionContinue the process while retaining the returned Compliance Check as evidence for the decision.

not_valid

Non valable

No eligible check satisfies the strategy, or the decisive check is not passed.

Recommended actionRun the required check or route to the appropriate business review according to the returned Compliance Check.

Parameters 5

subjectRequisCompany

Company or contact whose compliance checks must be evaluated.

check_typeRequisstring

Business nature of the requested check, for example kyc, kyb, aml, or liveness.

max_ageRequisduration

Maximum accepted freshness, expressed as an ISO 8601 duration; P3M means three calendar months.

scopeOptionnelstring

Optional compliance scope. When omitted, all scopes matching the subject and check type are considered.

selection_strategyOptionnelenum

Policy used when several eligible checks coexist: most_favorable, latest, or most_conservative.

Outputs 3

selected_routeenum

Business route chosen by the node according to the search or check result.

is_validboolean

Whether the configured strategy considers that a valid check justifies the valid route.

compliance_checkCompliance check

Compliance Check actually selected by the strategy to justify the route. It is absent only when no eligible check exists.

Behavior

The node first filters checks by subject, type, optional scope, maximum freshness, and valid_until. It then applies the configured strategy. most_favorable selects the most recent eligible passed check when one exists; latest uses the most recent eligible check; most_conservative selects the most recent non-passed check when one exists. The returned check is always the one that actually justifies the route.

Limits and responsibilities

The node does not create, renew, or revoke any Compliance Check.
A failed, error, manual_review, or pending result does not universally cancel another producer: the strategy chosen by the process defines how concurrent assertions are interpreted.
Maximum process freshness and the producer's valid_until are separate constraints and both must be satisfied.