taler-docs

commit 1b2239e9ae31cec77fdeb4bd8f50f56098bea9d4
parent b1ee352f3762e6c241dd88bc39e96797b4fc194d
Author: Florian Dold <florian@dold.me>
Date:   Wed, 19 Nov 2025 18:32:43 +0100

update DD75

Diffstat:
M
design-documents/075-wallet-bban-support.rst
 | 
18
++++++++++++++----

1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/design-documents/075-wallet-bban-support.rst b/design-documents/075-wallet-bban-support.rst
@@ -43,10 +43,18 @@ Wallet-core:
 
 * We provide two new requests to allow conversion between BBAN/IBAN:
 
-  * ``convertBbanToPaytoIban({ bban: string, currency: string }) -> { paytoUri: string }``
-  * ``convertPaytoIbanToBban({ paytoUri: string  }) -> { bban: string }``
+  .. code::
 
-In order to allow copy+pasting an IBAN into a BBAN field, the ``convertBbanToPaytoIban`` should
+    convertIbanAccountFieldToPayto({ value: string, currency: string })
+      => { ok: true, type: "iban" | "bban", paytoUri: string } | { ok: false, err: string }
+
+    convertPaytoIbanToAccountField({ paytoUri: string  })
+      => { type: "iban" | "bban", value: string }
+
+* The ``getDepositWireTypes`` request returns a ``preferredEntryType: "iban" | "bban"`` flag
+  for every payto URI of target tpye ``"iban"``.
+
+In order to allow copy+pasting an IBAN into a BBAN field, the ``convertBbanToPaytoIban`` must
 also accept actual IBANs as input and convert them to a payto URI.
 
 
@@ -58,8 +66,10 @@ Wallet-core: Unit tests for conversion functions.
 Wallet UIs should either:
 
 * Use story books to test the new UI elements for BBAN display/entry.
-* Use a feature flag to test the BBAN display with ``rusty`` and CHF
+* Use a dev experiment ``taler://dev-experiment/fake-chf-bban`` to force display/entry
+  of Swiss IBANs as BBAN.
 * Use a test HUF/IBAM deployment for testing (currently not provided/planned).
+* 
 
 
 Definition of Done