commit 57064facac824e4a65925b9abb6974d3a0b03515
parent 19b653a3e5ea762d8b6dc081e2e53c339d91cd23
Author: Florian Dold <florian@dold.me>
Date: Tue, 18 Nov 2025 15:09:46 +0100
-clarification
Diffstat:
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/design-documents/075-wallet-bban-support.rst b/design-documents/075-wallet-bban-support.rst
@@ -10,15 +10,17 @@ the entry and display of BBANs for payto URIs with target type "iban".
Motivation
==========
-Some countries (e.g. Hungary) still use BBANs instead of IBANs. These BBANs can
-be mapped to IBANs, but users expect being able to see and enter BBANs instead
-of IBANs.
+Some countries (e.g. Hungary) still use BBANs (basic bank account numbers)
+instead of IBANs. These BBANs can be mapped to IBANs, but users expect being
+able to see and enter BBANs instead of IBANs.
Requirements
============
* Support for BBANs should not impact the UI for countries / deployments that only use IBAN
* Logic for IBAN parsing / validation should not be duplicated in all UIs.
+* The underlying protocol / other wallet-core requests should still use ``payto://iban/`` and
+ not some BBAN-specific logic.
Proposed Solution
=================
@@ -28,7 +30,9 @@ IBAN or BBAN bank account entry/display UI element. For the BBAN UI elements,
the country will be derived from the wire type and currency.
There will *not* be any change to the protocol / other wallet-core requests.
-Internally, the BBAN will be converted to a payto URI.
+Internally, the BBAN will be converted to a payto URI. A country code (for
+countries that need BBAN support) and a valid BBAN can always be mapped to a
+IBAN and vice versa.
The following wire type / currency pairs must support BBAN entry:
