add screenshots

1 files changed, 75 insertions, 2 deletions

diff --git a/design-documents/053-wallet-ui.rst b/design-documents/053-wallet-ui.rst
index 5b5ba22d..5c3ccb9e 100644
--- a/design-documents/053-wallet-ui.rst
+++ b/design-documents/053-wallet-ui.rst
@@ -70,7 +70,7 @@ Common definition:
 Proposed Solutions
 ==================
 
-List of   dall screens with the defined properties
+List of all screens with the defined properties.
 
 cta-withdraw
 ------------
@@ -98,8 +98,62 @@ fee, restrictions and ETA should be clear for the user.
 .. attention::
   User should be able to play with the amount, not possible in the current design
 
+cta-wire-transfer
+-----------------
+
+``Description``: this screen is used to show the user the information for
+the wire transfer to complete a manual withdrawal operation.
+
+``Info``:
+ * wire transfer subject to be used (first, most important)
+ * target bank account to transfer funds to (e.g. IBAN)
+ * total amount to transfer in the wire transfer currency
+ * button to copy ``payto://`` URI with the information to clipboard
+
+``Actions``:
+ * abort: aborts the withdrawal operation
+ * menu: go back to the main balances list (operation continues in background)
+ * automatic: screen changes to "cta-withdraw-done" upon completion
+
+cta-withdraw-done
+-----------------
+
+``Description``: this screen is used to show the user the information for
+a completed withdraw operation (bank-integrated or manual)
+
+``Info``:
+ * amount wired  (hidden if no fees)
+ * fees paid (hidden if no fees)
+ * total amount withdrawn into wallet (effective balance change)
+ * exchange base URL
+ * date
+
+``Actions``:
+ * delete: deletes information about the withdrawal operation
+
+
+cta-url-entry
+-------------
+
+``Description``: this screen allows the user to scan a QR code, scan an NFC
+tag, or enter a taler://-URL.  Its implementation may differ significantly
+between platforms. For example, scanning NFC tags may be fully automated,
+scanning QR codes may involve some system applications, and maybe the dialog
+only allows the URL entry *or* the camera but not both at the same time,
+depending on implementation specifics.
+
+``Info``:
+ * camera with current image to enable user to focus on QR code
+ * current URL, with information if it is not well-formed for GNU Taler
+ * possibly status information on NFC reader (if available)
+
+``Actions``:
+ * open: if entered manually, open URL as-entered (otherwise open is automatic)
+ * back: return to previous view
+
+
 cta-payment
-------------
+-----------
 
 ``Description``: this screen is used for the confirmation of a payment to a merchant.
 the success of this operation will be an decrease of the balance in the wallet
@@ -121,6 +175,25 @@ fee, restrictions and ETA should be clear for the user.
  * get more cash: if there is not enough balance, it will be redirected to ``cta-witddraw``
  * cancel: user will be redirected to ``balance``
 
+
+cta-payment-paid
+----------------
+
+``Description``: this screen is used to show information with details
+about a historic payment.
+
+``Info``:
+ * merchant offering the order showing the URL
+ * order summary
+ * table of details of the operation: use the ``operation-table-details`` screen
+ * receipt: order id
+ * payment status: if the order was refunded
+
+``Actions``:
+ * delete: delete information about the transaction
+ * back: user will be redirected to ``balance``
+
+
 cta-deposit
 ------------