taler-docs

commit abd7c855b98f0fefc62acb9a47a0ea965c3afd1c
parent 6c0d79ea6d4907f4bd6d52cdce315a8ee1f10592
Author: MS <ms@taler.net>
Date:   Fri,  3 Nov 2023 09:32:41 +0100

DD 50, extending the payment initiations table.

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

1 file changed, 9 insertions(+), 0 deletions(-)
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
@@ -343,3 +343,12 @@ Discussion / Q&A
   * ``transient_failure``: submission failed but can be retried, for example after a network issue.
   * ``permanent_failure``: EBICS- or bank-technical error codes were not EBICS_OK (nor any tolerated EBICS code like EBICS_NO_DOWNLOAD_DATA_AVAILABLE), never retry.  
   * ``never_heard_back``: the payment initiation submission has **been** ``success`` but it was never confirmed by any outgoing transaction (from a camt.5x document) or any pain.002 report.  It is responsability of a garbage collector to set this state after a particular time period.
+
+* the initiated_outgoing_transactions table takes two more columns:
+  ``last_submission_date``, a timestamp in microseconds, and a
+  ``submission_counter``.  Both of them would serve to decide retry
+  policies.
+
+* the ``failure_text`` column at the initiated_outgoing_transactions table
+  should contain a JSON object that contains any useful detail about the problem.
+  That *could* be modeled after the Taler `ErrorDetail <https://docs.taler.net/core/api-common.html#tsref-type-ErrorDetail>`_, where at least the error code and the hint fields are provided.