#04 - KYC demand - Version 2.0

Callback received in case of status change in the KYC demand

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

the location where data will be sent. Must be network accessible
by the source server

Body Params

JSON Body

string

callback type

string

Status of the KYC demand :

  • Initialized (demand is created for the first time)
  • Pending (demand was created by KYC Provider)
  • Incomplete (demand has at least one diligence received and validated)
  • Complete (demand has all expected diligence and all of them are validated)
  • Rejected (demand was rejected)
  • Fraud Suspicion
  • Awaiting Expertise
  • Being Received (KYB demand has at least one diligence received)
  • Fully Received (KYB demand has all expected diligence received)
  • Archived (demand was archived)
string

User unique identifier

string

the User's KYC level :

  • Medium
  • High
string

Workflow Code associated to the KYC Demand :

  • Electronic_Sign
  • Identity
expectedDiligences
array of objects

the list of expected diligences types. It is not returned in the callback when all expected diligences are received.

expectedDiligences
receivedDiligences
array of objects

The list of diligences types that are received

receivedDiligences
Headers
string
required

Uuid of the sent callback

string
required

Callback Send date

Responses
202

Your server implementation should return this HTTP status code
if the data was received successfully

204

Your server should return this HTTP status code if no longer interested
in further updates

Callback
Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!