16.67. taler-merchant-depositcheck(1)¶
16.67.1. Name¶
taler-merchant-depositcheck - check if deposits are associated with wire transfers
16.67.2. Synopsis¶
taler-merchant-depositcheck [-c FILENAME | –config=FILENAME] [-e BASE_URL | –exchange=BASE_URL] [-h | –help] [-L LOGLEVEL | –loglevel=LOGLEVEL] [-l FILENAME | –logfile=FILENAME] [-T USEC | –timetravelUSEC] [-t | –test] [-v | –version]
16.67.3. Description¶
taler-merchant-depositcheck is a command-line tool to inquire with exchanges about whether they completed bank transfers in response to deposits made by the merchant backend. This will allow the merchant backend to detect deposit issues, for example if a KYC is blocking a wire transfer.
Its options are as follows:
- -c FILENAME | –config=FILENAME
Use the configuration and other resources for the merchant to operate from FILENAME.
- -e BASE_URL | –exchange=BASE_URL
Base URL of the exchange to monitor. If not given, a worker process will be spawned for each exchange in the configuration (“merchant-exchange-” sections).
- -h | –help
Print short help on options.
- -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.
- -s SECTION | –section=SECTION
Configuration section to use. Default is taler-merchant-depositcheck. Needed if different processes are used to watch multiple bank accounts (for the same instance or different instances).
- -T USEC | –timetravel=USEC
Modify the system time by USEC microseconds. USEC may be prefixed with
+or-(e.g.-T +300). This option is intended for debugging/testing only.- -t | –test
Run in test mode. Only runs until the current list of bank transactions are all imported.
- -v | –version
Print version information.
16.67.4. See Also¶
taler-merchant-httpd(1), taler-merchant.conf(5).
16.67.5. Bugs¶
Report bugs by using https://bugs.taler.net or by sending electronic mail to <taler@gnu.org>.