summaryrefslogtreecommitdiff
path: root/design-documents
diff options
context:
space:
mode:
authorMS <ms@taler.net>2023-10-28 10:34:55 +0200
committerMS <ms@taler.net>2023-10-28 10:34:55 +0200
commit3828df4d792d76ec8086874a90e3a76096e69cb8 (patch)
tree32ba3ed7f4343ddb84e45f4e4c2c76861ad8618f /design-documents
parent2edbf79c7735edd923879bd173502fe96e513d25 (diff)
downloaddocs-3828df4d792d76ec8086874a90e3a76096e69cb8.tar.gz
docs-3828df4d792d76ec8086874a90e3a76096e69cb8.tar.bz2
docs-3828df4d792d76ec8086874a90e3a76096e69cb8.zip
DD 50
ACCOUNT_NUMBER gone in favor of the account triple IBAN, BIC, NAME.
Diffstat (limited to 'design-documents')
-rw-r--r--design-documents/050-libeufin-nexus.rst18
1 files changed, 3 insertions, 15 deletions
diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst
index e9e3b49b..62d1602f 100644
--- 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.