taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 2edbf79c7735edd923879bd173502fe96e513d25
parent e691373fd1c176729875524d23ad38df9cea2599
Author: MS <ms@taler.net>
Date:   Fri, 27 Oct 2023 12:46:33 +0200

adapt DD 50 to latest choice

Diffstat:
Mdesign-documents/050-libeufin-nexus.rst | 21+--------------------
1 file changed, 1 insertion(+), 20 deletions(-)

diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst @@ -60,10 +60,9 @@ Configuration file USER_ID = myuser PARTNER_ID = myorg SYSTEM_ID = banksys - ACCOUNT_NUMBER = DE1234567890 # This value must identify with how the bank calls the bank account + ACCOUNT_NUMBER = payto://iban/BIC/IBAN?receiver-name=NexusUser # all fields mandatory BANK_PUBLIC_KEYS_FILE = enc-auth-keys.json CLIENT_PRIVATE_KEYS_FILE = my-private-keys.json - ACCOUNT_META_DATA_FILE = ebics-meta.json BANK_DIALECT = postfinance # EBICS+ISO20022 style used by the bank. [nexus-postgres] @@ -112,15 +111,6 @@ JSON with: * submitted_ini (boolean) * submitted_hia (boolean) -File contents: ACCOUNT_META_DATA_FILE -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - -JSON with: - - * account_holder_iban - * bank_code - * account_holder_name - Database schema --------------- @@ -194,15 +184,6 @@ The ebics-setup tool performs the following: accept them (or auto-accept via --auto-accept-keys). If the user accepted the public key, update the flag to "accepted". - * If all of the above has happened and we have accepted public keys from the - bank, try to download the list of bank accounts associated with the - connection and check that the configured account number is among them. On - success, store the associated meta data in the account meta data file. On - failure, show an error message with the list of available accounts (also - show this list via --show-associated-accounts). If the configured account - number is available, show a brief "setup ready" message. - - nexus-ebics-fetch -----------------