taler-exchange-kyc-tester - tool to test interaction with KYC provider
taler-exchange-kyc-tester [-c FILENAME | –config=FILENAME] [-h | –help] [-L LOGLEVEL | –loglevel=LOGLEVEL] [-l FILENAME | –logfile=FILENAME] [-i SECTION_NAME | –initiate=SECTION_NAME] [-u ID | –user=ID] [-U ID | –legitimization=ID] [-P | –print-payto-hash] [-p HASH | –payto-hash=HASH] [-r NUMBER | –rowid=NUMBER] [-v | –version] [-w | –run-webservice]
taler-exchange-kyc-tester is used to test the interaction between a Taler exchange and a KYC service. The tool can be used to manually trigger the various steps of a KYC process and to observe the interaction with the respective KYC service. It is supposted to help test the configuration of the integration, and not required at all during production.
To use it, you must first provide a configuration file with at least one KYC service configured. Some other exchange-specific options, like the PORT for the HTTP service and the BASE_URL under which the Taler exchange will run are also required. You should be able to use exactly the same configuration file that one would usually give to a Taler exchange. Starting with this, the tool allows the simulation of a KYC process. Note that it will not write any information to the database.
Begin with a first invocation of taler-exchange-kyc-tester using the options -i for an individual or business and use -R to specify a list of checks required from the process. The output will be an URL to visit with the browser, as well as -p, -u, -U options to use in future invocations of the tool.
Next, run taler-exchange-kyc-tester again, but this time using -w (to run the Webserver) and using the -u and -U options output by the previous call, as well as the -p option with the payto hash. Then visit the Web site from the link output by the previous invocation and “pass” (or “fail”) the KYC check.
Report bugs by using https://bugs.taler.net/ or by sending electronic mail to <email@example.com>.