FinCERT in StopList Service

TIP

Description of ASOI FinCERT and integration of the BrainySoft StopList service with ASOI FinCERT:

"User Instructions" → "Operational Activities" → "Admin" → "FinCERT".

To access the StopList service via the web interface, navigate to the "Admin" section. In the menu, find the "Other" section and select "Applications (beta)".

A list of available beta applications will open, where you need to find and select the "StopList" service.

"Status" Section

The "Status" section provides the time of the last successful import.

If there are failures in requests to FinCERT, the section displays a message "Import overdue" indicating the data type and time of the last import attempt.

"Import Status" Section

The "Import Status" section displays detailed information about the current loading state of various data types from the FinCERT system.

Table Structure:

• List - list of all data categories received by the system from FinCERT.

• Last Import - date and time of the last successful load for each category.

• Status - current state of the import process:

  • ✅ "on schedule" - import completed successfully according to schedule.
  • ❌ "overdue" - import was not completed on time (failure in requests to FinCERT).

• Records - number of records in each list.

Under normal system operation, all imports have the status "on schedule". The "overdue" status indicates problems with receiving data from FinCERT and requires administrator attention.

"Import History" Section

The "Import History" section provides detailed archival information about all data import operations. The section is divided into two main blocks:

1. "Summary by Types" - overview of recent imports by various data types indicating the date, time, number of records, and names of imported files.
2. "Last 90 Imports" - chronological list of the last 90 import operations with the same columns as in the summary table.

Table Structure:

• Check Type - data categories (account numbers, card numbers, electronic wallets, FPS numbers, TIN, passport hashes, phone numbers, SNILS hashes, SWIFT codes).

• Records - number of records imported for each category.

• Last Import to DB - date and time of the last successful data load to the database.

• Last Checksum Match - date and time of the last data integrity verification.

• File - name of the file from which data was imported.

• Feed ID - unique identifier of the data feed.

Checksum Update Mechanism:

When loading a feed, the system checks the file's checksum. If the checksum has changed - the data is updated in the DB and the "Last Import to DB" date is updated.

If the checksum matches the previous one, this means the data has not changed, and the file is not written to the database again. In this case, the date in the "Last Import to DB" column remains the same, while the "Last Checksum Match" column shows the time of the last check when it was confirmed that the feed in the database is current.

This allows analyzing update frequency and tracking import sequences.