[taler-docs] branch master updated: nexus man: --debug flag

[gnunet]

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

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 87978f3f nexus man: --debug flag
87978f3f is described below

commit 87978f3fd79ddeb83104b15116c1a1b020971132
Author: MS <ms@taler.net>
AuthorDate: Wed Nov 15 15:55:25 2023 +0100

    nexus man: --debug flag
---
 manpages/libeufin-nexus.1.rst | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/manpages/libeufin-nexus.1.rst b/manpages/libeufin-nexus.1.rst
index b72b499d..8a9ccfc7 100644
--- a/manpages/libeufin-nexus.1.rst
+++ b/manpages/libeufin-nexus.1.rst
@@ -79,7 +79,7 @@ Its options are as follows:
 ebics-submit
 ------------
 
-This subcommand submits any initiated payment that was not already sent to the 
bank.  In the current version, initiated payments may come from a cash-out 
operation or from a bounced incoming payment.  For debugging purposes, it is 
however possible to pass via STDIN a raw pain.001 document; this method turns 
ebics-submit to run in transient mode and it does NOT affect the database.  
ebics-submit is Taler friendly, therefore bounced payments are those that do 
not contain a valid subject to [...]
+This subcommand submits any initiated payment that was not already sent to the 
bank.  In the current version, initiated payments may come from a cash-out 
operation or from a bounced incoming payment.  ebics-submit is Taler friendly, 
therefore bounced payments are those that do not contain a valid subject to 
start a Taler withdrawal.  Cash-out operations come from a tightly integrated 
bank that offers their customers to convert their currency to the currency 
whose the EBICS subscriber ban [...]
 
 Its options are as follows:
 
@@ -89,11 +89,14 @@ Its options are as follows:
    Specifies the configuration file.
 **--transient**
    This flag, enabled by default, causes the command to check the database and 
submit only once, and then return.
+**--debug**
+  With this flag, it is possible to pass via STDIN a raw pain.001 document to 
be submitted to the bank.  This method turns ebics-submit to run in transient 
mode and it does NOT affect the database.
+
 
 ebics-fetch
 -----------
 
-This subcommands download banking records via EBICS.  By default it downloads 
notifications, in the form of ``camt.054``.  It looks for the most recent 
incoming transaction and asks the bank any notification starting from such 
timestamp.  Along the download, ebics-fetch would bounce incoming payments that 
do not have a valid Taler subject, or as well those with an already existing 
valid subject.  Valid incoming payments are then stored in the database so that 
they can trigger Taler withd [...]
+This subcommands download banking records via EBICS.  By default it downloads 
notifications, in the form of ``camt.054``.  It looks for the most recent 
incoming transaction and asks the bank any notification starting from such 
timestamp.  Along the download, ebics-fetch would bounce incoming payments that 
do not have a valid Taler subject, or as well those with an already existing 
valid subject.  Valid incoming payments are then stored in the database so that 
they can trigger Taler withd [...]
 
 **-h** \| **--help**
    Print short help on options.
@@ -111,6 +114,9 @@ This subcommands download banking records via EBICS.  By 
default it downloads no
    It downloads the subscriber activity via EBICS HAC in the form of pain.002 
documents.  It does NOT affect the database.
 **--pinned-start**
   Only supported in --transient mode, this option lets specify the earliest 
timestamp of the downloaded documents.  The latest timestamp is always the 
current time.
+**--debug**
+  With this flag, ebics-fetch accepts XML documents from STDIN.  In this case, 
it prints on the console the result and exits, without affecting the database.  
The results are the stringified objects that the application itself uses to 
represent the business details.
+
 
 
 SEE ALSO

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