commit 8192da3b7cee2ea4a86165eaffe2620321f394ef
parent 5ced8f9ca1141937e6987d212452497aef1126cd
Author: Joel-Haeberli <haebu@rubigen.ch>
Date: Tue, 14 May 2024 22:30:24 +0200
poster: draft
Diffstat:
2 files changed, 24 insertions(+), 15 deletions(-)
diff --git a/poster/cashless2ecash_poster.pdf b/poster/cashless2ecash_poster.pdf
Binary files differ.
diff --git a/poster/cashless2ecash_poster.tex b/poster/cashless2ecash_poster.tex
@@ -17,12 +17,8 @@
% \includegraphics[width=10cm]{taler_logo.png}
% \includegraphics[width=10cm]{wallee_logo.png}
% }
- \footerqrcode{https://taler-c2ec.ti.bfh.ch}
- \footer{}
-
- \footergraphics{
- \includegraphics[height=\height]{taler_logo.png}
- \includegraphics[height=\height]{wallee_logo.png}
+ \footer{
+ \footerqrcode{https://taler-c2ec.ti.bfh.ch}
}
\begin{tcbposter}[
@@ -30,10 +26,10 @@
columns=4,
rows=7,
spacing=1cm,
- showframe, %Gitter einblenden. Für Platzierung häufig hilfreich
+ %showframe, %Gitter einblenden. Für Platzierung häufig hilfreich
}]
- \begin{posterboxenv}[,BFH-abstract,title=Introduction]{name=intro,column=1,row=1,span=3, rowspan=2}
+ \begin{posterboxenv}[BFH-abstract,title=Introduction]{name=intro,column=1,row=1,span=3, rowspan=2}
In a report commissioned by the ECB (European Central Bank) the universal acceptance was identified as one of the most important aspects of a digital euro. The report published in 2022 is the result of a focus group concerning the acceptance of a digital euro as new payment system. The universal acceptance was even identified as the most important property amongst the general public and tech-savvy people in the report.
@@ -45,19 +41,26 @@
\end{posterboxenv}
- \begin{posterboxenv}[title=Report]{name=intro,column=4,row=1,span=1, rowspan=2}
+ \begin{posterboxenv}[BFH-abstract,title=Report]{name=intro,column=4,row=1,span=1, rowspan=2}
\includegraphics[width=\linewidth]{report_qr_code.png}
\captionof{figure}{QR Code to the report commissioned by the ECB}
\end{posterboxenv}
- \begin{posterboxenv}[title=Terminals API]{name=api,column=2,row=3,span=3}
- To allow the withdrawal of digital cash using Taler, the newly introduced Terminals API must be implemented by the Exchange. It specifies the requests needed by a third party terminal to setup and process the the withdrawal. To fully integrate into the Taler ecosystem, implementing parties are adviced to add their payto target type with the GANA (GNU Assigned Numbers Authority) if needed. This prevents conflicts with other technologies and integrations in the future.
+ \begin{posterboxenv}[BFH-abstract,title=Terminals API]{name=api,column=2,row=3,span=3}
+ To allow the withdrawal of digital cash using Taler, the newly introduced Terminals API must be implemented by the Exchange. It specifies the requests needed by a third party terminal to setup and process the the withdrawal. Therefore the setup of the withdrawal operation must implement the generation of a cryptographically sound nonce. It will allow the withdrawal operation and links the customers reserve public key to the withdrawal, which eventually allows the withdrawal. To fully integrate into the Taler ecosystem, implementing parties are adviced to add their payto target type with the GANA (GNU Assigned Numbers Authority) if needed. This prevents conflicts with other technologies and integrations in the future.
+ \end{posterboxenv}
+
+ \begin{posterboxenv}[BFH-abstract]{name=api,column=1,row=3,span=1, rowspan=1}
+
+ \includegraphics[width=\linewidth]{taler_docs_terminals_api.png}
+ \captionof{figure}{Terminals API Specification}
+
\end{posterboxenv}
- \begin{posterboxenv}[title=Integrating Wallee]{name=wallee, row=4, span=3, span=4}
- Explain Wallee Integration
+ \begin{posterboxenv}[BFH-abstract,title=Integrating Wallee]{name=wallee, column=2, row=4, span=3, span=3}
+ To show that the specification is able to capture the needs for third party withdrawals and therefore allow the integration for theoretically any means of payment, an integration was done for the payment provider Wallee. Therefore an android app was implemented on the Wallee platform. The newly created withdrawal application sets up the withdrawal and awaits the registration of the withdrawal parameters (the reserve public key) through the Taler Wallet. After the parameters were registered, the terminal authorizes the payment by letting the customer present his credit card, which will trigger the attestation of the payment at the provider backend through the C2EC component.
\end{posterboxenv}
@@ -67,8 +70,14 @@
\end{posterboxenv}
- \begin{posterboxenv}[title=Integrate your platform!]{name=Integrate your platform, row=7, span=4}
- How to integrate other platforms
+ \begin{posterboxenv}[BFH-abstract,title=Integrate your platform!]{name=Integrate your platform, column=1,row=6,span=2,rowspan=2}
+ C2EC is designed to be extensible. Therefore the component defines two interfaces which must be implemented in order to make use of the C2EC components. The first interface defines the interface between the transaction of the provider and the C2EC components. This includes the definition of the transaction state mapping between the provider specific states and the states defined by the Taler API. This step is crucial since, when implemented wrong, can lead to issues concerning the securities on the side of the Taler Exchange. This means that digital cash is withdrawn by the customer, when the counter payment was not yet fully secured. The second interface defines the integration of the provider backend into the C2EC component. This includes the requests necessary to load the state of the transaction on the side of the provider and the request to trigger refunds.
+ \end{posterboxenv}
+
+ \begin{posterboxenv}[title=Flow]{name=flow-diagram,column=3,row=6,span=2,rowspan=2}
+
+ \includegraphics[width=\linewidth]{system_overview.png}
+
\end{posterboxenv}
\end{tcbposter}
