Concedus giving KYC Reliance and Sharing

CONCEDUS identifies the respective customer prior to and for the purpose of establishing a CONCEDUS contract in accordance with the provisions §§ 10 Abs. 1 Nr. 1, 11 Abs. 4 Nr. 1, 12 Abs. 1 Satz 1 Nr. 1, 13 Abs. 1 Nr. 2 of the German Money Laundering Act (Geldwäschegesetz - GWG). The identification of the respective customer takes place within the framework of a recognised video identification procedure operated by a third party ("Videoident provider"). The identification of customers is not carried out using simplified due diligence obligations within the meaning of § 14 Abs. 1 GwG.

It's important to emphasize that access to the Concedus Claudia API is not universally available. Our policy ensures that only "Authorized" institutions can utilize this service, maintaining the highest level of data integrity and security. This exclusivity is part of our commitment to upholding stringent compliance standards and protecting sensitive information.

CONCEDUS makes identification data records of Reliance customers available to other partners subject to anti-money laundering obligations by agreement in accordance with § 17 Abs. 3a GwG.

Authentication

Authenticate

POST https://demo2.api.concedus.com/v2/auth/token

Request Body

Name
Type
Description

username*

String

password*

String

{
    "accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjbGllbnQiOiJvcGVuZGF0YVRpbWVsZXNzU3RhZ2luZyIsInhwX3Rva2VuIjoiXHUwMDAwSztcIkdcblpIPiVcdTAwMThcdTAwMWRcdTAwMTQtcWtoXGZ7XHUwMDAyXHUwMD...xmweP18-zD91MW-QY",
    "exp": 1646842318
}

Authenticate

POST https://demo2.api.concedus.com/v2/auth/token

Request Body

Name
Type
Description

username*

String

0Hc5FHRDTYUg

password*

String

ucKHnZ9khhxN

The confirmed bearer token has a validity of 4 minutes and should be renewed automatically with every interaction.

KYC Reliance of a natural person

To retrieve a person record, the person key (identifying characteristic) must be specified in the URL.

Each retrieval may be subject to a charge. Check the conditions of your contract.

Get KYC data set (Reliance)

GET https://demo2.api.concedus.com/v2/reliance/persons/person-key

Path Parameters

Name
Type
Description

person-key*

String

person-key

Headers

Name
Type
Description

Authorization*

String

Bearer token

{
    "type": "RELIANCE",
    "foreName": "Kora",
    "surName": "Müller",
    "address": {
        "zip": "60439",
        "country": "DE",
        "city": "Frankfurt am Main",
        "street": "Am Alten Schloss 12"
    },
    "birthDate": "1988-04-12",
    "birthPlace": "Frankfurt",
    "pepCheck": "keine",
    "nationality": "DE",
    "idDocumentNumber": "LG2YZ5P09",
    "pepCheckAt": "2022-05-06T00:00:00",
    "files": [
        {
            "fileName": "c13b119cd5db4354ba4b6498749324da-7cf5022aa601ed105bb1b54d84a5beba.pdf",
            "data": ""
        }
    ],
    "relianceEventKey": "cmVsaWFuY2VfZGM5YjBmMzE1OGVlNDFmMDgxMTUyNDEzYTlmZmJkYTg="
}

Get KYC data set (Reliance)

GET https://demo2.api.concedus.com/v2/reliance/persons/person-key

Path Parameters

Name
Type
Description

person-key*

String

9OSvPIggTJfl

Headers

Name
Type
Description

Authorization*

String

aUxF2pTMnW9J

If the ident is not ready. Please make sure the client has been onboarded before

{
    "type": "RELIANCE",
    "requestIds": [
        "eb8586bc77644d3e9cde70c889f80d0d"
    ]
}

Reliance Information
Path
Value
Note

type

type

[RELIANCE ,SHARING]

Depending on the API function / plan. Here it is always "RELIANCE"

forename

foreName

<string>

surname

surName

<string>

zip

address.zip

<string>

country

address.country

<string>

iso country code of the natural persons registration address

city

address.city

<string>

street

address.street

<string>

street and housenumber

nationality

nationality

<string>

iso country code

ID of document

idDocumentNumber

<string>

The ID of the document used for legitimation during the Ident session

birthdate

birthDate

YYYY-MM-DD

birthplace

birthPlace

<string>

Ident-PDF

files[].data

<base64>

PDF file (original) of the Video-Ident-Session.

relianceEventKey

relianceEventKey

<string>

Event-Key to request the Concedus Reliance PDF document.

Part of the reliance data set is the customer-person data - as well as all documents attached to the KYC procedure. Depending on the KYC provider, this is usually a PDF.

The reliance data set also contains an event-key. This event-key ("relianceEventKey") can be used to download the reliance document.

Download Reliance Document

GET https://demo2.api.concedus.com/v2/reliance/files/event-key

Path Parameters

Name
Type
Description

event-key*

String

relianceEventKey

Headers

Name
Type
Description

Authorization*

String

Bearer token

KYC Reliance of a legal entity

POST https://demo2.api.concedus.com/v2/reliance/persons/person-key

To retrieve a person record, the person key (identifying characteristic) must be specified in the URL.

Headers

Name
Value

Content-Type

application/json

Authorization

Bearer <token>

Body

Name
Type
Description

person-key*

string

person-key

Response

{
   
}

Download Reliance Document (PDF)

It's important to note that in addition to the original report provided by the identity verification provider, Concedus offers its own Reliance PDF. This document is an essential tool for institutions requiring comprehensive and compliant KYC data. The Concedus Reliance PDF can be accessed through a specific API function designed for this purpose.

To ensure the seamless retrieval of the Reliance PDF, it's critical to acknowledge the processing time involved in generating this document. Once a request is made, the system may take a few seconds to compile and prepare the PDF. To accommodate this, we recommend allowing a buffer period of approximately 30 seconds before proceeding with the retrieval function. This precaution ensures that the document is fully prepared and accessible, minimizing any potential delays or complications in accessing the PDF.

GET https://demo2.api.concedus.com/v2/reliance/files/event-key

Path Parameters

Name
Type
Description

event-key*

String

45zATTdbPeTx

Headers

Name
Type
Description

Authorization*

String

WDluuia9e3aQ

Response

[PDF]

KYC Sharing

To retrieve a person record, the person key (identifying characteristic) must be specified in the URL.

Each retrieval may be subject to a charge. Check the conditions of your contract.

Get KYC data set (Sharing)

GET https://demo2.api.concedus.com/v2/sharing/persons/person-key

Path Parameters

Name
Type
Description

person-key*

String

person-key

Headers

Name
Type
Description

Authorization*

String

Bearer token

{
  "type": "SHARING",
  "foreName": "Kora",
  "surName": "Müller",
  "address": {
    "zip": "60439",
    "country": "DE",
    "city": "Frankfurt am Main",
    "street": "Am Alten Schloss 12"
  },
  "birthDate": "1988-04-12",
  "birthPlace": "Frankfurt",
  "pepCheck": "keine",
  "nationality": "DE",
  "idDocumentNumber": "LG2YZ5P09",
  "pepCheckAt": "2022-05-06T00:00:00",
  "files": [
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da-7cf5022aa601ed105bb1b54d84a5beba.mp4",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da-1cee3724c5e68f35bb9d260f3245e768.pdf",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_idbackside-3615a0bd0d3c6ffd05e85aad687fca0d.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_idfrontside-452046f9ae404d717ccf5a6d19ecc319.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_security1-d73ddd07a6c7fd0e96a8e40597f4203b.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_security2-64ed0fe994bf2cfffd6ec9820ca54e7c.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_security3-d73ddd07a6c7fd0e96a8e40597f4203b.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_security_covered-d73ddd07a6c7fd0e96a8e40597f4203b.jpg",
      "data": ""
    },
    {
      "fileName": "c13b119cd5db4354ba4b6498749324da_userface-8aa50f3dcc57d4498bcc2816f3b8884c.jpg",
      "data": ""
    }
  ]
}

Get KYC data set (Sharing)

GET https://demo2.api.concedus.com/v2/sharing/persons/person-key

Path Parameters

Name
Type
Description

person-key*

String

J9ImbLIxCdJB

Headers

Name
Type
Description

Authorization*

String

P7LppDOWD07b

Part of the Sharing data set is the customer-person data - as well as all documents attached to the KYC procedure. Depending on the KYC provider, these are usually a PDF including a report and additional JPG images for ID documents.

Download of Video (ZIP) files.

POST https://demo2.api.concedus.com/v2/kyc/files/person-key

In the "Retrieval of Video Material" section, we delve into a specialized feature of our API that catifies to exceptional circumstances where a comprehensive archive of video identification materials is required for an individual or a business entity. This capability is particularly crucial for in-depth verification processes or in scenarios where enhanced due diligence is necessary.

Overview: The retrieval of video material function is designed to provide authorized institutions with direct access to a complete archive of video identification sessions. These sessions could include recorded video interactions, verification processes, or any other relevant video material associated with the KYC verification of a person or a business.

Asynchronous Nature of the Process: The retrieval of video material is an asynchronous process, reflecting its computationally intensive nature. Due to the extensive data involved and the need for thorough compliance and security checks, the process is designed to run in the background, allowing the system to manage resources efficiently and ensure the integrity of the data.

Initial Response and EventKey: Upon initiating a request for video material, institutions will immediately receive a response with a status code of 200, accompanied by an eventKey. This key is essential as it represents the specific request and is used to track the progress of the archive's preparation.

Timeframe: The entire process of verifying the request, compiling the video material, and making it accessible can take up to 60 seconds. This duration accounts for the meticulous attention to detail and the stringent security measures in place to protect sensitive information.

Headers

Name
Value

Content-Type

application/json

Authorization

Bearer <token>

Body

Name
Type
Description

person-key*

string

person-key

Response

{
    "eventKey": "a3ljX2Zp...0ZDhkYWU0Mw=="
}

To download the Zip archive, reuse the "Download" function and use the eventKey of this response.

You will get then as answer to the Request the binary zip archive.

PreviousRequest Ident LinkNextConcedus using Reliance

Last updated