ZignSec

Other Register Checks

Below you find country-specific KYC-services (Know Your Customer). The goal is to verify the true identity of the end-user.

APIs

POST to https://env.zignsec.com/v2/ekyc/matchpidcpr
POST to https://env.zignsec.com/v2/ekyc/checkdkrofus
where env is api or test.

List of Services

  • Denmark: MatchPidCpr – This call checks if a Danish PID number matches the publicly used CPR number. (PID is the long technical key identifying a person especially in the NemID service.)
  • Denmark: CheckDkRofus – This is our check against Rofus, the Danish self-administered Ludomania registry (Ludomania is another word for problem gambling)

MatchPidCpr API (for Danish Nemid)

This call checks whether the PID (NemId´s technical person identifier returned on every NemID authentication) matches the supplied CPR number.

API

POST to https://env.zignsec.com/v2/ekyc/matchpidcpr
   where env is api or test.

A Real Example

If the below data is sent to the TEST environment the service will return True, since there is a match in the CPR TEST register between PID and CPR, meaning they refer to the same Danish person.
PID: “9208-2002-2-577168596796”
CPR: “1506093330”
Both ids refer to the same Danish person – Tika Klaussen (TIKA144) in the test environment – so the MatchPidCpr call returns True.

Example Request

            POST https://test.zignsec.com/v2/ekyc/MatchPidCpr HTTP/1.1
Content-Type: application/json; charset=UTF-8
Authorization: your_key_here

{
   "Pid":"9208-2002-2-577168596796",
   "Cpr":"2005803511"
}
        

Example Response

            {
  "id":"1a722876-1b11-444d-8105-69e59671c384",
  "errors":[],
  "IsMatch":true
}
        

CheckDkRofus API (Danish Ludomania registry)

API

POST to https://env.zignsec.com/v2/ekyc/checkdkrofus
   where env is api or test.

The call will return either:

  • PersonIsNotRegistered
  • PersonIsRegisteredTemporarily
  • PersonIsRegisteredPermanently

Note 1: We have no specific test persons for this service for the moment, but call with Environment=Mock to return the three main possible answers at random.
Note 2: For production calls an account needs to be signed.

Example Request

            {
   "personalnumber":"2005803522"
}
        

Example Response

            {
  "id": "ef66b096-7dd9-4597-a324-153fd0435673",
  "errors": [],
  "RofusStatus": "PersonIsRegisteredPermanently"
}