summaryrefslogtreecommitdiff
path: root/design-documents
diff options
context:
space:
mode:
authorMS <ms@taler.net>2023-11-02 10:30:05 +0100
committerMS <ms@taler.net>2023-11-02 10:30:05 +0100
commit4d4e4ceb1624e74b68e06e0a9cf4695c9018dfc3 (patch)
tree7c323e9e2ac13000aa4a1d4f439d7aee8f4aed8a /design-documents
parent9c3e2169800023c3d84b0409085cd4268140f7b0 (diff)
downloaddocs-4d4e4ceb1624e74b68e06e0a9cf4695c9018dfc3.tar.gz
docs-4d4e4ceb1624e74b68e06e0a9cf4695c9018dfc3.tar.bz2
docs-4d4e4ceb1624e74b68e06e0a9cf4695c9018dfc3.zip
notes to DD50 about fetching payments
Diffstat (limited to 'design-documents')
-rw-r--r--design-documents/050-libeufin-nexus.rst17
1 files changed, 17 insertions, 0 deletions
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
index 272e7a7b..82982dc3 100644
--- a/design-documents/050-libeufin-nexus.rst
+++ b/design-documents/050-libeufin-nexus.rst
@@ -196,6 +196,23 @@ nexus-ebics-fetch
over (before committing any transactions with the next day!) also fetches a
final statement of the previous day, thus ensuring we get a statement
every day plus intra-day reports.
+
+ .. note::
+
+ (1) "from that day forward (inclusive)" must **not** rely on EBICS returning
+ the unseen messages: that's because they might **already** be downloaded but
+ never made it to the database.
+
+ (2) "and when the day rolls over". When does a day roll over? => A day rolls
+ over when the current time is at least on the day after the transaction with the
+ most recent timestamp that's stored in the database.
+
+ (3) "Afterwards, fetches reports". This must happen **only after** any possible
+ previous statement got downloaded.
+
+ To summarize: at any point in time the database must contain (the content of) any
+ possible statement up to the current time, plus any possible report up to the current
+ time (in case that's not covered by any statement so far).
* Bounces transactions with mal-formed wire transfer subjects.