DEVELOPERS · CHECKID

Process Perform

Perform verification with multipart payload/evidence and process-type-dependent fields.

Talk to an expert Developer quick start

CONTRACTVersioned API / SDK

AUTHOAuth2 / environment

OUTPUTResponse · result code · evidence

SOURCE-DRIVEN REST CONTRACT

Process Perform

Perform the check using a JSON payload plus optional evidence file; conditional fields depend on process_type.

Source contractDigital Trusted Identity Service API And Kafka Specifications · V1.2.260123

PUT/v1/perform/process

Bearer + OAuth2 Client Credentials · multipart/form-data3.6 · Process PerformSource p.21

Perform the check using a JSON payload plus optional evidence file; conditional fields depend on process_type.

Open in API Explorer ↗

Field	Type	Presence	Description
`payload`	Object	M	JSON object sent as multipart text
`evidence`	Byte Array	M/O	File upload when required by process type

REQUEST — redacted sampleNO PRODUCTION SECRET

{
  "payload": {
    "subject_id": "<SUBJECT_ID>",
    "process_id": "<PROCESS_ID>",
    "lang": "en"
  },
  "evidence": "<BINARY_FILE_WHEN_REQUIRED>"
}

RESPONSEDOCUMENTED SHAPE

{
  "status": 0,
  "message": "SUCCESSFULLY",
  "dtis_id": "<DTIS_TRANSACTION_ID>",
  "process_type": "LIVE_FACIAL_MATCHING_EKYC",
  "perform_result": {
    "final_result": {
      "match_result": true,
      "liveness": true,
      "claim_sources": {
        "JWT": "<SIGNED_JWT>"
      }
    }
  }
}

Publication boundaryExamples use explicit placeholders; the website does not send requests to a production environment.

CONDITIONAL PAYLOAD

Fields depend on process_type

Conditional fields are not presented as universally mandatory.

identity_documentM/OPA · live facial · fingerprint · facial matching

evidence_upload_typeM/OKYC · LIVENESS · VERIFY · MATCHED; selected face/liveness processes

otpM/OEMAIL_AUTHENTICATION · MOBILE_AUTHENTICATION

framesM/OFace/liveness process types

fingerprintM/OFingerprint matching

left_fingerprints / right_fingerprintsM/OFINGERPRINT_ENROLLING

pa_dataM/OPASSIVE_AUTHENTICATION

os_typeM/OPASSIVE_AUTHENTICATION

reader_snM/OPA on WIN according to source

session_key_dataM/OPASSIVE_AUTHENTICATION

API REFERENCE

Source-backed contract: Perform Process

PUT · /v1/perform/process

Endpoint & purpose

PUT /v1/perform/process. Execute the process with conditional evidence according to process type.

Authentication

Bearer . Do not replace this mechanism with assumptions from legacy documentation.

Publication scope

PARTNER. Source: CheckID API contract V1.2.260123 §2.2.12.

Request shape

{
  "payload": {
    "process_type": "PASSIVE_AUTHENTICATION",
    "operating_system": "WINDOWS"
  },
  "evidence": "<BINARY_EVIDENCE>"
}

Response shape

{
  "process_status": "ACCEPTED",
  "perform_result": {
    "passive_authentication_status": "PARTIAL_VALID"
  },
  "x-billcode-id": "<BILLCODE_ID>"
}

Failure / recovery

Error semantics must use the raw contract/error catalogue; retry/idempotency/timeout behavior is applied only when a corresponding source defines it.