taler-docs

commit 7dc8ad3e5d82ab945dc79a9a52c3127ac7928eab
parent 7a3025e0d8ae698994a0d1c51dba15fff78aea1c
Author: MS <ms@taler.net>
Date:   Mon, 23 Oct 2023 11:33:18 +0200

DD 50 Q&A

Diffstat:
M
design-documents/050-libeufin-nexus.rst
 | 
6
++++++

1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
@@ -306,3 +306,9 @@ Discussion / Q&A
 
 * Implementation sticks to the IBAN found in the configuration, **if** the bank
   does not show any IBAN related to the EBICS subscriber.
+
+* from nexus-ebics-submit: "if the server accepts the request, sets the
+  initiated flag in the table to true".  May there be a case where the
+  server accepted the request, but the client never got any response (some
+  network issue..), and therefore didn't set the submitted flag, ending
+  up in submitting the payment twice?