summaryrefslogtreecommitdiff
path: root/design-documents
diff options
context:
space:
mode:
Diffstat (limited to 'design-documents')
-rw-r--r--design-documents/050-libeufin-nexus.rst5
1 files changed, 4 insertions, 1 deletions
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
index 6f3638be..779e0b58 100644
--- a/design-documents/050-libeufin-nexus.rst
+++ b/design-documents/050-libeufin-nexus.rst
@@ -311,4 +311,7 @@ Discussion / Q&A
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?
+ up in submitting the payment twice? Also: flagging the payment _after_
+ the bank response, may lead double-submission even if the HTTP talk ended
+ well: it suffices to crash after having received a "200 OK" response but
+ before setting the submitted flag to the database.