Fortuna Compliance API

PEP Screening

Use the PEP endpoints to check whether a person is registered as a Politically Exposed Person (PEP) in the Finanstilsynet database. PEP checks are a regulatory requirement for all new customer relationships.

Single check — POST /api/pep/check

Checks one person against the PEP register.

Request body:

Field Type Required Description
audit.externalReference string Yes Your reference for this check (stored in audit log)
audit.context string No Optional context string
firstName string Yes Given/middle names
lastName string Yes Family name/surname
dateOfBirth string Yes Date of birth (YYYY-MM-DD)

Response:

Field Type Description
firstName string First name from the request
lastName string Last name from the request
dateOfBirth string Date of birth from the request
isPep boolean true if the person is registered as a PEP
matchScore number Confidence score between 0.00 and 1.00 — see note below
matchExplanation string Human-readable explanation of the match result, if available

Understanding matchScore

The match score indicates how closely the person matches an entry in the PEP register:

  • 1.00 — Exact match across all fields
  • 0.70–0.99 — Strong match — likely the same person
  • 0.40–0.69 — Partial match — manual review recommended
  • 0.00–0.39 — Low similarity — no meaningful match

When isPep is false, matchScore reflects the closest match found (which did not meet the threshold). When isPep is true, it reflects confidence in the positive match.

Bulk check — POST /api/pep/check-bulk

Checks multiple persons in a single request. Each person gets their own result and a separate audit entry.

Request body:

Field Type Required Description
persons array Yes Array of person objects to check
persons[].audit.externalReference string Yes Your reference for this person (stored in individual audit entry)
persons[].audit.context string No Optional context string
persons[].firstName string Yes Given/middle names
persons[].lastName string Yes Family name/surname
persons[].dateOfBirth string Yes Date of birth (YYYY-MM-DD)

Response:

Field Type Description
results array One result object per person in the request, in the same order

Each result in results has the same shape as the single-check response (firstName, lastName, dateOfBirth, isPep, matchScore, matchExplanation).

Audit: One audit record is created per person — not one for the entire bulk request. This means each individual check is independently traceable by its own externalReference.

Error reference

Status Meaning
400 Missing or invalid required fields
403 PEP checks are not enabled for your account