commit ec6dfc91a97d6a5ec0d286029e1fb92e49d91a41
parent 5f5357a0634b96caf1fe35c7db83d3d073221660
Author: Joel-Haeberli <haebu@rubigen.ch>
Date: Sat, 25 May 2024 17:15:16 +0200
docs: enhance abstract
Diffstat:
3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/docs/content/architecture/c2ec.tex b/docs/content/architecture/c2ec.tex
@@ -98,14 +98,3 @@ The structure of the three entities form a tree which is rooted at the terminal
\caption{Relationships of the entities.}
\label{fig-logical-model-relations}
\end{figure}
-
-\section{Payto wallee-transaction extension}
-RFC 8905 \cite{rfc8905} specifies a URI scheme (complying with RFC 3986 \cite{rfc3986}), which allows to address a creditor with theoretically any protocol that can be used to pay someone (such as IBAN, BIC etc.) in a standardized way. It introduces a registry which holds the specific official values of the standard. The registry is supervised by the GANA (GNUnet Assigned Numbers Authority) \cite{gnunet-gana}.
-
-In case a refund becomes necessary, which might occur if a transaction does not succeed or a reserve is not withdrawn within the specified time, a new \textit{target type} called \textit{wallee-transaction} is registered. It takes a transaction identifier as \textit{target identifier} which identifies the transaction for which a refund process shall be triggered. The idea is that the handler of the payto URI is able to deduct the transaction from the payto-uri and trigger the refund process.
-
-\subsection{Payto refund using Wallee}
-Wallee allows to trigger refunds using the Refund Service of the Wallee backend. The service allows to trigger a refund given a transaction identifier. Therefore the C2EC component can trigger the refund using the refund service if needed. The payto-uri retrieved as debit account by the wire gateway API, is leveraged to delegate the refund process to the Wallee Backend using the Refund Service and parsing the transaction identifier of the payto-uri.
-
-\subsection{Extensibility}
-The flow is extensible and other providers like Wallee might be added. They might want to register their own refund payto-uri (if needed) with the GANA and then the refund process can be implemented likewise.
diff --git a/docs/content/architecture/wallee.tex b/docs/content/architecture/wallee.tex
@@ -36,3 +36,14 @@ The \textit{Refund Service} is used by C2EC in case of a refund. Therefore the C
\subsubsection{Wallee Transaction State}
To decide if a transaction was successful, the states of a transaction within Wallee must be mapped to the world of Taler. This means that a reserve shall only be created, if the transaction is in a state which allows Taler not having any liabilities regarding the transaction and that Wallee could process the payment successfully. The documentation states that \textit{only} in the transaction state \textit{fulfill}, the delivery of the goods (in case of withdrawal this means, that the reserve can be created) shall be started \cite{wallee-transaction-process}. For the withdrawal this means, that the only interesting state for fulfillment is the \textit{fulfill} state. Every other state means, that the transaction was not successful and the reserve shall not be created.
+
+\section{Payto wallee-transaction extension}
+RFC 8905 \cite{rfc8905} specifies a URI scheme (complying with RFC 3986 \cite{rfc3986}), which allows to address a creditor with theoretically any protocol that can be used to pay someone (such as IBAN, BIC etc.) in a standardized way. It introduces a registry which holds the specific official values of the standard. The registry is supervised by the GANA (GNUnet Assigned Numbers Authority) \cite{gnunet-gana}.
+
+In case a refund becomes necessary, which might occur if a transaction does not succeed or a reserve is not withdrawn within the specified time, a new \textit{target type} called \textit{wallee-transaction} is registered. It takes a transaction identifier as \textit{target identifier} which identifies the transaction for which a refund process shall be triggered. The idea is that the handler of the payto URI is able to deduct the transaction from the payto-uri and trigger the refund process.
+
+\subsection{Payto refund using Wallee}
+Wallee allows to trigger refunds using the Refund Service of the Wallee backend. The service allows to trigger a refund given a transaction identifier. Therefore the C2EC component can trigger the refund using the refund service if needed. The payto-uri retrieved as debit account by the wire gateway API, is leveraged to delegate the refund process to the Wallee Backend using the Refund Service and parsing the transaction identifier of the payto-uri.
+
+\subsection{Extensibility}
+The flow is extensible and other providers like Wallee might be added. They might want to register their own refund payto-uri (if needed) with the GANA and then the refund process can be implemented likewise.
diff --git a/docs/thesis.pdf b/docs/thesis.pdf
Binary files differ.
