TALER-MERCHANT-DEPOSITCHECK(1)
πΈ NAME πΈ
taler-merchant-depositcheck β bestie, this is the little detective that goes and checks the status of deposits with exchange. That's it, that's the job. (And hey, you're reading the TALER-MERCHANT-DEPOSITCHECK(1) page from the GNU Taler fam, welcome π)
β¨ 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]
quick heads up π«Ά β the synopsis up there literally says--timetravelUSECwhile the options list below says--timetravel=USEC. That's just how the page is written, so it's staying exactly like that. iykyk.
π DESCRIPTION π
okay so picture this: taler-merchant-depositcheck is a command-line tool that goes and inquires with exchanges about whether they actually completed the bank transfers in response to deposits the merchant backend made. like, "hey exchange, did the money move or are we ghosted?" π
and the whole point is that it lets the merchant backend detect deposit issues β for example, if a KYC is blocking a wire transfer. so it's giving main character energy for catching problems before they spiral. π₯
its options are as follows, and yes, we're doing all of them:
-c FILENAME,--config=FILENAMEβ use the configuration and other resources for the merchant to operate fromFILENAME. your whole setup lives in there, so point it somewhere real β¨-e BASE_URL,--exchange=BASE_URLβ base URL of the exchange to monitor. and here's the cute part: if you don't give it one, a worker process will be spawned for each exchange in the configuration (the"merchant-exchange-"sections). so it'll just go do the rounds itself, no cap π§-h,--helpβ print short help on options. the classic "what does anything do" button π-L LOGLEVEL,--loglevel=LOGLEVELβ specifies the log level to use. accepted values are:DEBUG,INFO,WARNING,ERROR. pick your verbosity vibe π-l FILENAME,--logfile=FILENAMEβ send logging output toFILENAME. like, put the receipts in a file instead of screaming into the terminal π-s SECTION,--section=SECTIONβ configuration section to use. default istaler-merchant-depositcheck. needed if different processes are used to watch multiple bank accounts (for the same instance or different instances). so if you're juggling accounts, this is the one keeping everyone straight π-T USEC,--timetravel=USECβ modify the system time byUSECmicroseconds.USECmay be prefixed with+or-(e.g.-T +300). this option is intended for debugging/testing only. β οΈ literally only for debugging/testing, do not make it your whole personality-t,--testβ run in test mode. only runs until the current list of bank transactions are all imported. short and sweet, in-and-out π-v,βversionβ print version information. (yes that dash is exactly how the page has it, we don't fix, we don't editorialize, we respect the dash π)
π SEE ALSO π
go read those next, bestie, they're connected fr fr π¦
π BUGS π
report bugs by using https://bugs.taler.net or by sending electronic mail to <taler@gnu.org>. the maintainers wanna hear it, don't suffer in silence π
π AUTHOR π
GNU Taler contributors β legends, all of them.
β COPYRIGHT β
2014-2025 Taler Systems SA (GPLv3+ or GFDL 1.3+)
and that's the page! π this was version 1.0, dated Dec 22, 2025, from the GNU Taler source β ok bye, go check some deposits, slay π«Άβ¨
π¦ where this page comes from
- nixos 26.05: taler-merchant 1.3.0
- nixpkgs unstable: taler-merchant 1.3.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms