[taler-docs] branch master updated: ebics fetch: debugging hints

[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 764fcfab ebics fetch: debugging hints
764fcfab is described below

commit 764fcfabb87242a24a9be648cc942e0cf46590b5
Author: MS <ms@taler.net>
AuthorDate: Tue Nov 14 14:22:02 2023 +0100

    ebics fetch: debugging hints
---
 manpages/libeufin-nexus.1.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/manpages/libeufin-nexus.1.rst b/manpages/libeufin-nexus.1.rst
index f21d926e..012aef8f 100644
--- a/manpages/libeufin-nexus.1.rst
+++ b/manpages/libeufin-nexus.1.rst
@@ -79,8 +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 either from a 
cash-out operation or from a bounced incoming payment.  There is therefore 
**no** way to manually initiate a payment at this moment.  This tool 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 [...]
-
+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 [...]
 
 Its options are as follows:
 

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