Skip to main content

Sending the profile for verification

Check method​

You should use this method to send a beneficiary questionnaire to Bank 131 for identification.

Request API v2 allows you to send profiles of individuals, residents and non-residents of the Russian Federation, for verification. Request API v1 allows you to submit profiles only for residents of the Russian Federation for verification.

The response includes the request ID by which you can learn the verification result.

Endpoint​

For testing​

POST https://kyc-stage.bank131.ru/api/v2/check

When testing, no real ID verification is performed, and answer will be emulated. Do not take these results to verify your customers' IDs.

For live testing​

POST https://kyc.bank131.ru/api/v2/check

Request​

Non-resident individuals can sign their requests using RSA Keys. To enable this functionality, contact your manager in Bank 131.

Request parameters (recipient details)​

NameMandatoryTypeDescription
type+stringRecipient type. Possible values:
FL_RESIDENT — resident individual;
FL_NONRESIDENT — non-resident individual
last_name+stringLast name
first_name+stringFirst Name
patronymic-stringPatronymic name (if the individual has no patronymic, do not pass this parameter)
birthday+stringDate of birth as DD.MM.YYYY. Must be 18 years old or older
birthplace+stringPlace of birth
citizenship+stringCitizenship in ISO 3166-1 alpha-2 format
inn+stringTaxpayer identification number (INN in Russia), 6 to 14 characters
phone_number+stringPhone number (any format)
e-mail+stringValid email address
documents+arrayMandatory documents. The set of mandatory documents may vary depending on the beneficiary type and their citizenship according to the following rules:
for individuals residents of the Russian Federation — only a Russian passport PASSPORT_RF is required;
for individuals non-residents of the Russian Federation — a foreign passport FOREIGN_PASSPORT and any other type of document other than the Russian passport PASSPORT_RF is required;
for citizens of the Republic of Belarus — only a foreign passport FOREIGN_PASSPORT is required
  type+stringDocument type. Possible values:
PASSPORT_RF — Russian passport;
FOREIGN_PASSPORT — non-Russian passport;
MIGRATION_CARD — migration card;
RESIDENT_CARD — resident card;
REFUGEE_CERTIFICATE — refugee certificate;
VISA — visa;
ARRIVAL_NOTICE — arrival notice;
TEMPORARY_RESIDENCE_PERMIT — temporary residence permit;
PATENT — patent
  number+ (not mandatory only for ARRIVAL_NOTICE)stringDocument number. The minimum number of characters for the type FOREIGN_PASSPORT — 2, and the maximum — 10. There are no restrictions for other types. If there is a series, it should be transmitted together with the number in the SERIESNUMBER format
  issuer_code- (mandatory only for PASSPORT_RF)stringIssuing division code
  issuer- (mandatory only fo PASSPORT_RF and FOREIGN_PASSPORT)stringIssuing division
  expire_date+ (not mandatory only for PASSPORT_RF and FOREIGN_PASSPORT)stringExpiration date of the document. The specified date must be strictly greater than the current date. The difference between the issue date and the expiration date must not exceed a certain period, depending on the type:
MIGRATION_CARD — 1 year;
RESIDENT_CARD — 10 years;
REFUGEE_CERTIFICATE — 3 years;
VISA — 3 years;
ARRIVAL_NOTICE — 180 days;
TEMPORARY_RESIDENCE_PERMIT — 3 years;
PATENT — 1 year
  issuer_date+stringIssuing date as DD.MM.YYYY
postcode-stringZIP Code
address+stringAddress
agent_contract_number+stringAgency Agreement No.
agent_contract_date+stringAgency Agreement Date
beneficial_owners+stringAlways: No BO
public_officials+stringAlways: No
Response examples 
curl -X POST \
https://kyc.bank131.ru/api/v2/check/ \
-H 'x-partner-project: test-partner-project' \
-H 'Content-Type: application/json' \
-H 'accept: application/json' \
-d '{
  "payload": {
    "type": "FL_RESIDENT",
    "last_name": "Dmitriev",
    "first_name": "Ivan",
    "patronymic": "Ivanovich",
    "birthday": "01.01.1970",
    "birthplace": "Novgorod",
    "citizenship": "RU",
    "inn": "065553161159",
    "phone_number": "+79000000000",
    "email": "name@email.com",
    "documents": [
      {
        "type": "PASSPORT_RF ",
        "number": "0234567890",
        "issuer": "UFMS Russia",
        "issuer_date": "01.01.2010",
        "issuer_code": "123-000"
      }
    ],
    "address": "Novgorod, Pribrezhnaya str., 53",
    "postcode": "365826",
    "agent_contract_number": "123456789-0",
    "agent_contract_date": "01.01.2020",
    "beneficial_owners": "No BO",
    "public_officials": "No"
  },
  "signature": "dkQzYwTExRc0RFWk1CY0dBMVVFQnd3UTBMTXVJTkNjMEw3Ug0NCmd..."
}'

Response​

For testing, the value of the status field sent in the response strictly depends on the last digit in ID number of the passport_number field sent in the request.

Last digit of passport_number fieldstatus field value
Even, including 0ok
Unevenerror

Response parameters​

NameMandatoryTypeDescription
status+stringIdentification status. Possible options: ok, error
data-DataResponse details object
  id-numberCheck request ID
  description-stringRequest status description
error-ErrorError details object
  code+stringError code
  description+stringError description
Response examples 
{
  "status": "ok",
  "data": {
    "id": "7",
    "description": "request added to queue"
  }
}