gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: update taler-exchange-kyc-tester man


From: gnunet
Subject: [taler-docs] branch master updated: update taler-exchange-kyc-tester man page
Date: Sat, 20 Jul 2024 16:32:10 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new d25e142d update taler-exchange-kyc-tester man page
d25e142d is described below

commit d25e142db980b0dffbe5ec27d3edd3be02dd4e5a
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sat Jul 20 16:31:55 2024 +0200

    update taler-exchange-kyc-tester man page
---
 manpages/taler-exchange-kyc-tester.1.rst | 36 +++++++++++++++++++++++---------
 1 file changed, 26 insertions(+), 10 deletions(-)

diff --git a/manpages/taler-exchange-kyc-tester.1.rst 
b/manpages/taler-exchange-kyc-tester.1.rst
index 6bfad3b2..e934d9b5 100644
--- a/manpages/taler-exchange-kyc-tester.1.rst
+++ b/manpages/taler-exchange-kyc-tester.1.rst
@@ -17,11 +17,16 @@ Synopsis
 [**-L** *LOGLEVEL* | **--loglevel=**\ ‌\ *LOGLEVEL*]
 [**-l** *FILENAME* | **--logfile=**\ ‌\ *FILENAME*]
 [**-i** *SECTION_NAME* | **--initiate=**\ ‌\ *SECTION_NAME*]
-[**-u** *ID* | **--user=**\ ‌\ *ID*]
-[**-U** *ID* | **--legitimization=**\ ‌\ *ID*]
+[**-M** | **--list-measures**]
+[**-m** *MEASURE_NAME* | **--measure=**\ ‌\ *MEASURE_NAME*]
+[**-o** *OPERATION_TYPE* | **--operation=**\ ‌\ *OPERATION_TYPE*]
 [**-P** | **--print-payto-hash**]
 [**-p** *HASH* | **--payto-hash=**\ ‌\ *HASH*]
+[**-R** *JSON* | **--ruleset=**\ ‌\ *JSON*]
 [**-r** *NUMBER* | **--rowid=**\ ‌\ *NUMBER*]
+[**-t** *AMOUNT* | **--trigger=**\ ‌\ *AMOUNT*]
+[**-u** *ID* | **--user=**\ ‌\ *ID*]
+[**-U** *ID* | **--legitimization=**\ ‌\ *ID*]
 [**-v** | **--version**]
 [**-w** | **--run-webservice**]
 
@@ -55,24 +60,35 @@ Next, run taler-exchange-kyc-tester again, but this time 
using **-w** (to run th
 **-i** *USERTYPE* \| **--initiate=**\ ‌\ *USERTYPE*
    Specifies the type of user for which we are starting a fresh KYC process. 
USERTYPE must be either "individual" or "business".
 
-**-u** *ID* \| **--user=**\ ‌\ *ID*
-   Run the process with ID for the user identifier at the KYC provider. Not 
useful in conjunction with **-i** and **-R** as that option will override 
whatever value is provided here.
+**-M** \| **--list-measures**
+   List possible measures to be given to the **-m** option.
 
-**-U** *ID* \| **--legitimization=**\ ‌\ *ID*
-   Run the process with ID for the legitimization process identifier at the 
KYC provider. Not useful in conjunction with **-R** / **-i** as that option 
will override whatever value is provided here.
+**-m** *MEASURE_NAME* \| **--measure=**\ ‌\ *MEASURE_NAME*
+   Trigger the KYC operation using the given *MEASURE_NAME* among the choices 
of KYC measures.
 
-**-p** *HASH* \| **--payto-hash=**\ ‌\ *HASH*
-   Run the process with HASH as the hash of the payto://-URI that identifies 
the account or wallet triggering the KYC requirement. If not given, a fresh 
random value is used. Rarely useful.
+**-o** *OPERATION_TYPE* \| **--operation=**\ ‌\ *OPERATION_TYPE*
+   Trigger the KYC operation by simulating a trigger of the given 
*OPERATION_TYPE*.
 
 **-P** \| **--print-payto-hash**
    Print the HASH of the payto://-URI used for the KYC simulation this time. 
Useful if the hash is needed for a subsequent use in conjunction with **-p**.
 
-**-r** *NUMBER* \| **--rowid=**\ ‌\ *NUMBER*
-   Run the process with NUMBER as the database row for the legitimization 
operation. Rarely useful, except maybe for debugging. Defaults to 42.
+**-p** *HASH* \| **--payto-hash=**\ ‌\ *HASH*
+   Run the process with HASH as the hash of the payto://-URI that identifies 
the account or wallet triggering the KYC requirement. If not given, a fresh 
random value is used. Rarely useful.
 
 **-R** *CHECKS* \| **--requirements=**\ ‌\ *CHECKS*
    Start a fresh KYC process for the given list of CHECKS. CHECKS must be a 
space-separated list of checks that must be in the configuration under 
*PROVIDED_CHECKS* for some of the providers. The exchange will determine which 
provider to use for KYC based on the CHECKS given.  The tool will output the 
HTTP URL where the user has to begin the KYC process to the command-line. This 
is usually the first thing to do when using this tool. Outputs the KYC-logic 
specific user and legitimization  [...]
 
+**-r** *NUMBER* \| **--rowid=**\ ‌\ *NUMBER*
+   Run the process with NUMBER as the database row for the legitimization 
operation. Rarely useful, except maybe for debugging. Defaults to 42.
+
+**-t** *AMOUNT* \| **--trigger=**\ ‌\ *AMOUNT*
+   Trigger the KYC operation by crossing the specified *AMOUNT* for the given 
**-o** *OPERATION_TYPE*.
+
+**-U** *ID* \| **--legitimization=**\ ‌\ *ID*
+   Run the process with ID for the legitimization process identifier at the 
KYC provider. Not useful in conjunction with **-R** / **-i** as that option 
will override whatever value is provided here.
+
+**-u** *ID* \| **--user=**\ ‌\ *ID*
+   Run the process with ID for the user identifier at the KYC provider. Not 
useful in conjunction with **-i** and **-R** as that option will override 
whatever value is provided here.
 
 **-v** \| **--version**
    Print version information.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]