NPCK / COID¶

The overview describes the common field interpretation rules, failure reasons, and full/light file formats.

Parent: npck_result. Face comparison through NPCK and retrieved personal data.

Fields of npck_result.

Fields marked “Required” are always present within this object. Other fields are included when a value is available; null is excluded from the response.

Field	JSON type	Purpose and conditions
`personal_number`	string	IIN used for the check, if determined.
`status`	string, enum	Required. `CREATED` — record created; `PENDING` — request awaiting execution; `COMPARED` — comparison completed; `RETRIEVED` — data retrieved; `FAILED` — error.
`result_json`	JSON	Personal data from the external service. Dynamic JSON, with no closed nested schema in this response.
`prediction`	string	Similarity score, a decimal string stored with 4 decimal places; zero is not excluded.
`prediction_percent`	string	`prediction × 100` rounded to an integer, without `%`; when a score is available.
`result`	boolean	Stored technology result: `true` means accepted, `false` means a negative result. May be absent before calculation; consider the status and the details below.
`failure_reason`	object	Failure reason, if recorded; see the structure.

The NPCK photo and PDF report are outside this contract.

JSON examples¶

Fragments of the root response object, not complete responses. All values and URLs are illustrative. File formats follow the explanations on this page.

{
  "npck_result": {
    "status": "COMPARED",
    "result": true,
    "prediction": "0.9600",
    "prediction_percent": "96"
  }
}