14.41. taler-exchange-sanctioncheck(1)#
14.41.1. Name#
taler-exchange-sanctioncheck - check existing accounts against a sanctions list
14.41.2. Synopsis#
taler-exchange-sanctioncheck [-c FILENAME | –config=FILENAME] [-h | –help] [-L LOGLEVEL | –loglevel=LOGLEVEL] [-l FILENAME | –logfile=FILENAME] [-n | –norun] [-r | –reset] [-t | –test] [-v | –version]
14.41.3. Description#
taler-exchange-sanctioncheck is a command-line tool to check all existing accounts (and their KYC attributes) against a sanctions list, freezing matches and flagging partial matches for investigation by AML staff.
The actual matching is done by an external tool configured via the “RATER” option in “[exchange-sanctionscheck]”. The default implementation of that tool is provided by robocop.
Its options are as follows:
- -c FILENAME | –config=FILENAME
Use the configuration and other resources for the exchange to operate from FILENAME.
- -I | –ignore-not-found
Do not fail if the bank says that the exchange bank account does not (yet) exist. Keep trying.
- -L LOGLEVEL | –loglevel=LOGLEVEL
Specifies the log level to use. Accepted values are:
DEBUG,INFO,WARNING,ERROR.- -l FILENAME | –logfile=FILENAME
Send logging output to FILENAME.
- -n | –norun
Skips the actual processing of KYC records. Useful only to check the setup or to reset processing to the start in combination with -r.
- -r | –reset
Resets the sanction list processing progress. Useful when a new sanction list is imported to go again over all historic records and check them again.
- -t | –test
Run in test mode. Exits once all records that existed on start have been processed and skips the incremental phase. Sanction list progress is still persisted. Useful in test cases or interactively when waiting for completion.
- -v | –version
Print version information.
14.41.4. See Also#
taler-exchange-httpd(1), taler-exchange.conf(5), robocop(1).
14.41.5. Bugs#
Report bugs by using https://bugs.taler.net/ or by sending electronic mail to <taler@gnu.org>.