commit 3828df4d792d76ec8086874a90e3a76096e69cb8
parent 2edbf79c7735edd923879bd173502fe96e513d25
Author: MS <ms@taler.net>
Date: Sat, 28 Oct 2023 10:34:55 +0200
DD 50
ACCOUNT_NUMBER gone in favor of the account
triple IBAN, BIC, NAME.
Diffstat:
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
@@ -60,7 +60,9 @@ Configuration file
USER_ID = myuser
PARTNER_ID = myorg
SYSTEM_ID = banksys
- ACCOUNT_NUMBER = payto://iban/BIC/IBAN?receiver-name=NexusUser # all fields mandatory
+ IBAN = MY-IBAN
+ BIC = MY-BIC
+ NAME = MY NAME
BANK_PUBLIC_KEYS_FILE = enc-auth-keys.json
CLIENT_PRIVATE_KEYS_FILE = my-private-keys.json
BANK_DIALECT = postfinance # EBICS+ISO20022 style used by the bank.
@@ -296,17 +298,3 @@ Discussion / Q&A
the bank response, may lead double-submission even if the HTTP talk ended
well: it suffices to crash after having received a "200 OK" response but
before setting the submitted flag to the database.
-
-* Given that PostFinance does not provide the IBAN & BIC pair
- on HTD (or other "admin" message types), the client cannot
- confirm the bank account metadata with the bank. As a result,
- it can only rely on what the configuration has in the
- ACCOUNT_NUMBER value.
-
- The current design however does NOT mandate any particular
- format for such configuration value, and given that the debtor
- BIC is mandatory in the pain.001 generation, ACCOUNT_NUMBER
- should be a Payto address with BIC and account holder name.
-
- Possibly, it may even be renamed to better match its content,
- for example to ACCOUNT_METADATA.
