Skip to main content
Version: 🚧 Next

FSP Definitions

Overview​

This page gives an overview of all FSP Definitions in the organization.

Creating a definition​

See Settings for more information on how to configure a newly created FSP definition.

Import a definition​

Imports a definition from a JSON file.

Bulk delete definitions​

Deletes multiple definitions at once using database identifiers. Use with caution, as this action cannot be undone.

Settings​

Is Back Office​

Determines whether the FSP operates as a back-office rather than as a client-facing front-office. A back office is a very specific setup that can only handle dossiers from linked front-offices that are being sent to the back-office.

See also Financial Service Provider.

Other settings​

Settings Configuration

Examples

Modules​

See Modules for more information.

Dossier Configurations​

A list of all linked Dossier Definitions.

Configuration​

Dossier questionnaires​

This list contains the dossier questionnaires that are available for this FSP definition.

To add forms as dossier questionnaires, you have to export the FSP definition and add your form definition identifiers in the fspDefinitionQuestionnaires array:

{
  "fspDefinitionQuestionnaires": [
    {
      "partyType": "INDIVIDUAL",
      "dossierStatuses": [
        "OPEN"
      ],
      "formDefinitionIdentifier": "questionnaire_1"
    },
    {
      "partyType": "COMPANY",
      "dossierStatuses": [
        "OPEN"
      ],
      "formDefinitionIdentifier": "questionnaire_2"
    }
  ]
}

Associated party types​

The following types of related persons are taken into account during EDD preconditions, completeness checks and rba scoring.

Products & Commercial products​

For each product you can set a knowledge test threshold and an experience test threshold. They decide whether the product is available to a client, based on the test score of the questions linked to that product:

ThresholdProduct is available when
0Always
Between 0 and 1 (including 1)The test score divided by the number of questions of that test is at least the threshold (e.g. 0.5 requires half of the questions to be passed, 1 requires all of them)
Greater than 1The test score is at least the threshold
EmptyThe test type is not evaluated for this product
  • Only products added here are tested. A product without a threshold, or without questions carrying its ID product, has no test result.
  • If a product has a parent product and the parent is not available, the child is not available either.
  • The result is stored per product and shown in the TEST_RESULTS flow step, split into available and non-available products.

Signing types​

The following signing types can be configured

Signing typeInformation
SIGNATURESigning by drawing a signature on the screen
OTPSigning by confirming an OTP code send via SMS
CONFIRMSigning by simply pressing a confirmation button
AUTO_CONFIRMThe system signs without further user input
CONFIRM_SIGNED_CONTRACTSimilar to CONFIRM, with with extra information referring to a signed contract
PROVIDERSigning by using an external signing provider

An additional checkbox can be configured by the acceptTerms field. This ensures the user must check this checkbox thereby confirming additional terms. These "accept terms" are sometimes referred to as "opt-in".

Notes:

  • CONFIRM_SIGNED_CONTRACT with accept terms will automatically be used for the flow option SIGNED_CONTRACT_V2, regardless of configuration.
  • For the PROVIDER signing type to work, a signing provider must be configured and PDF generation should not be disabled.
  • If none are configured, SIGNATURE and OTP (both without "accept terms"-requirement) will be selected as default.
  • The global settings on FSP definition can be overridden at flow definition level, see flow definition signature settings.

By default, a submission can always be rejected. This can be disabled in flow definition signature settings (by setting the rejectAllowed field to false).

Dossier Lifecycle​

Dossier Status Transition Definition​

This provides a visual representation of all automations configured for the FSP Definition for a given dossier status transition definition.

Status Transition Diagram

Select a Dossier Status Transition Definition from the dropdown to view a flowchart of all possible status transitions. Each transition displays:

  • Validations that must pass before the transition
  • Actions that execute after the transition
  • Color-coded by source (System, FSP, Transition)

Click on any validation or action in the diagram to navigate to its configuration.

Validation Sources

Validations are categorized by their source:

  • Default: Built-in default validations that affect status transitions
  • FSP-wide: Validations configured at the FSP definition level
  • Transition-specific: Validations from status transition definitions

Validations​

See Validations.

Actions​

See Actions.

Automation Overview​

This automation overview provides a table of all automations configured for the FSP Definition.

Reference​

The import envelope of an FSP definition. This is the shape of the JSON file that Import a definition accepts and that exporting a definition produces.

FspDefinitionExportDTO​

Settings Configuration

Examples