commit 764fcfabb87242a24a9be648cc942e0cf46590b5
parent 6ade610d3205176f67892b58e514d6ea7520b342
Author: MS <ms@taler.net>
Date: Tue, 14 Nov 2023 14:22:02 +0100
ebics fetch: debugging hints
Diffstat:
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git 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 customers to convert their currency to the currency whose the EBICS subscriber bank account is tied 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. 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 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 bank account is tied to.
Its options are as follows:
