Passport-to-INN Match Check

Request to check whether an individual's passport data matches their INN.

The data includes information about the individual for whom the passport-to-INN match request is generated, including:

• the individual's full name
• information about the individual's identity document
• the individual's INN

As well as information about the result of the request based on Unified State Register of Taxpayers (EGRN) data:

• "Data matches" or
• "Data does not match"

The following request headers must be passed in all requests:

Name	Type	Required	Description
X-Api-Key	string	Yes	Unique shop identifier
X-Signature	string	Yes	Request signature

The signature is generated using secret_key — the secret key found in the merchant's shop settings.

Verification request

Method: POST

• Production: https://api.baas.kvell.group/v1/smev3/fns/pasp-inn
• Stage: https://api.baas.stage.kvell.group/v1/smev3/fns/pasp-inn

Request parameters (JSON)

Name	Data type	Required	Description
last_name	string (up to 60 characters)	Yes	Last name
first_name	string (up to 60 characters)	Yes	First name
middle_name	string (up to 60 characters)	Yes, if present	Middle name
inn	string ([0-9]{1}[1-9]{1}|[1-9]{1}[0-9]{1})[0-9]{10} format)	Yes	Individual's INN
doc_type_id	string enum	No (defaults to 21 – passport)	Identity document type code
doc_num	string (1-25 characters)	Yes	Document series and number
issue_date	string (YYYY-MM-DD format)	No	Document issue date
issuer_name	string (up to 255 characters)	No	Name of the authority that issued the document
issuer_code	string (7 characters)	No	Code of the department that issued the document

The allowed values for doc_type_id and the corresponding doc_num format can be found here.

Do not transliterate personal data

Enter the personal details exactly as recorded in the identity document; do not translate or transliterate them unless the API explicitly requires it.

{
  "inn": "520205004556",
  "last_name": "ЧАХЛОВ",
  "first_name": "ПЕТР",
  "middle_name": "АЛЕКСЕЕВИЧ",
  "doc_num": "22 02 919928",
  "issue_date": "2002-11-16",
  "issuer_code": "000-000",
  "issuer_name": "АРОВД"
}

Building the signature

The X-Signature signature is generated by concatenating X-Api-Key, json <request body>, and secret_key. A sha256 hash is computed from the resulting string:

sha256({x-api-key}{json <request body>}{secret_key})

Request response

{
  "request_id": "b48c09bc-6efb-4da4-95aa-4a85ff923425"
}

request_id — request identifier, used to retrieve the result.

Retrieving the verification result

Method: GET

• Production: https://api.baas.kvell.group/v1/smev3/fns/pasp-inn/{request_id}
• Stage: https://api.baas.stage.kvell.group/v1/smev3/fns/pasp-inn/{request_id}

URL request parameters

Name	Data type	Required	Description
request_id	string	Yes	Request identifier

GET /v1/smev3/fns/pasp-inn/b48c09bc-6efb-4da4-95aa-4a85ff923425

Building the signature

The X-Signature signature is generated by concatenating X-Api-Key, request_id, and secret_key. A sha256 hash is computed from the resulting string:

sha256({x-api-key}{request_id}{secret_key})

Request response

Example 1Example 2Example 3Example 4 (HTTP 404)

{
  "state": "in_progress",
  "request_id": "befe8815-24b0-446b-925c-ea128f39667c",
  "response_id": null
}

{
  "state": "finished",
  "request_id": "befe8815-24b0-446b-925c-ea128f39667c",
  "response_id": "df65dc1c-fc66-41cd-abbd-87218127fbeb",
  "result":
  {
    "conf_code": "1"
  }
}

{
  "state": "finished",
  "request_id": "6ed9f77b-c150-4cdb-adcf-9d70d167f6ab",
  "response_id": null,
  "error": {
    "code": "internal",
    "desc": "Error connecting to SMEV"
  }
}

{
  "error": "request not found"
}

• state — request status
  • in_progress — being processed
  • finished — completed
• request_id — request identifier assigned for SMEV3 (optional)
• response_id — response identifier in the SMEV3 system, if a response was received from the department's information system (FNS)
• result — processing result (required if state = finished and error = null)
  • conf_code — passport-to-INN match code, possible values:
    • 1 — data matches
    • 2 — data does not match
  • message — match message (optional)
• error — error from the internal service, SMEV, or the department's information system (required if state = finished and result = null)
  • code — error code (required)
  • desc — error description (required)
  • status_code — SMEV3 status HTTP code (optional)
  • destname — request field containing the error from SMEV (optional)