taler-docs

commit 7b75d09335c11d9defc15d59fb516053f45f4aa8
parent bf9fbd4a5d0421019dd0453475d96f1d5cab9a18
Author: MS <ms@taler.net>
Date:   Wed, 18 Oct 2023 08:50:19 +0200

format

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

1 file changed, 13 insertions(+), 15 deletions(-)
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
@@ -293,18 +293,16 @@ Discussion / Q&A
 ================
 (This should be filled in with results from discussions on mailing lists / personal communication.)
 
-From private discussion: bouncing goes inside nexus-fetch as
-it saves one database event, makes the HTTPd simpler, and lets
-the bouncing happen even when no HTTPd runs.
---
-Implementation suggested that --force-keys-resubmission affects both keys.
---
-Sign-up PDF is ever only generated if both keys have the "submitted" state.
---
-What is 'override option for re-submission of private keys?'.
---force-keys-submission already re-submits the keys but it does not
-override them.  If the user wants new keys, they can easily remove
-the keys file on disk.  That makes the CLI shorter.
---
-If bank does not give HTD (information about one EBICS subscriber's bank
-account), then the bank account metadata file gets what *the config* suggests.
+* From private discussion: bouncing goes inside nexus-fetch as
+  it saves one database event, makes the HTTPd simpler, and lets
+  the bouncing happen even when no HTTPd runs.
+
+* Sign-up PDF is ever only generated if *both* INI & HIA have the "submitted" state.
+
+* What is 'override option for re-submission of private keys?'.
+  --force-keys-submission already re-submits the keys but it does not
+  override them.  If the user wants new keys, they can easily remove
+  the keys file on disk.  That makes the CLI shorter.
+
+* Implementation sticks to the IBAN found in the configuration, **if** the bank
+  does not show any IBAN related to the EBICS subscriber.