What the data for this category looks like
List screening data has three primary sources: official public sanctions lists, risk warning lists released by regulatory authorities, and suspicious entity lists shared across the industry. Updates follow no fixed schedule. Emergency updates are pushed when regulatory policies change suddenly. Routine updates occur once per week to once per month. Most documents are structured tables in CSV format. They include fields such as list ID, entity name, alias list, registered address/nationality, sanctions basis, effective date, and expiration date. Date fields use the YYYY-MM-DD format. Entity name is a string type. Alias list is a multi-value string array.
What constraints these characteristics impose on deployment and upgrade
Multiple data sources require configuring multi-channel pull adaptation logic during deployment. This avoids incomplete verification coverage caused by a single data source. No fixed update rhythm requires supporting trigger-based update mechanisms during upgrade. This ensures timely synchronization of the latest list content. The structured CSV document format requires enabling a dedicated structured parsing template during deployment. General unstructured parsing configuration cannot be used directly. Multi-field and alias matching logic requires reserving field mapping and alias processing extension interfaces during upgrade. This adapts to field differences across different data sources. Single batch verification data volume must match hardware performance. This avoids service timeouts caused by excessive data volume.
How to configure the parameters
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
LIST_SCREENING_SOURCE_TYPE | Multi-source Pull | Adapts to list data sources from multiple channels such as regulatory authorities and industry sharing |
LIST_UPDATE_FREQUENCY | Triggered update (default 1-hour polling) | Matches the feature of no fixed update cycle for lists, synchronizes latest data on demand |
PARSE_STRUCTURED_DATA_MODE | CSV structured parsing | Adapts to the mainstream CSV format document structure of list data |
ALIAS_MATCH_THRESHOLD | 0.85–0.9 | Balances alias matching precision and recall, avoids missed or false judgments |
MAX_SCREENING_BATCH_SIZE | 50 items per batch | Controls single processing data volume, avoids exceeding service processing limits |
SCREENING_TIMEOUT | 600 seconds | Reserves sufficient processing time for batch verification tasks, prevents mid-task interruptions |
The parameter values provided on this page are common recommendations used as a starting point for configuration. Actual values are affected by material form, data volume and business rules. Specific issues require specific analysis, and it is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Phenomenon: Frontend page is inaccessible after deployment, with
connection refusedprompt. Cause: Container ports were not correctly mapped to the host machine during deployment, or a firewall blocked the external service port. - Phenomenon: List screening task execution fails, returning
400 Bad Request. Cause: ThePARSE_STRUCTURED_DATA_MODEparameter was not configured, causing non-standard list files to fail to be read correctly. - Phenomenon:
ETIMEDOUTerror occurs when calling an external API. Cause: A reasonableSCREENING_TIMEOUTparameter was not set, and the single processing data volume exceeded the API response time limit.
How to confirm proper configuration
- Upload a standard-compliant list test file, confirm that the extracted fields after parsing match the configured mapping rules.
- Trigger a manual update task, check whether the system log shows that the data source was pulled successfully and the number of entries meets expectations.
- Submit a KYC verification request containing entities from the test list, confirm that the system returns matching results.
- Check the service running log, confirm that all configuration parameters have been loaded correctly, and there are no unrecognized configuration item errors.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.