diff options
author | MS <ms@taler.net> | 2023-10-23 11:33:18 +0200 |
---|---|---|
committer | MS <ms@taler.net> | 2023-10-23 11:33:18 +0200 |
commit | 7dc8ad3e5d82ab945dc79a9a52c3127ac7928eab (patch) | |
tree | 5713d39d2b0e661d5c7182ba68ff5b5915c43fda /design-documents | |
parent | 7a3025e0d8ae698994a0d1c51dba15fff78aea1c (diff) | |
download | docs-7dc8ad3e5d82ab945dc79a9a52c3127ac7928eab.tar.gz docs-7dc8ad3e5d82ab945dc79a9a52c3127ac7928eab.tar.bz2 docs-7dc8ad3e5d82ab945dc79a9a52c3127ac7928eab.zip |
DD 50 Q&A
Diffstat (limited to 'design-documents')
-rw-r--r-- | design-documents/050-libeufin-nexus.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst index ed5f466b..6f3638be 100644 --- 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? |