taler-docs

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

commit e691373fd1c176729875524d23ad38df9cea2599
parent ce22ffac43f8de45fa1fcf98bed572ce7be63f7b
Author: MS <ms@taler.net>
Date:   Fri, 27 Oct 2023 12:30:44 +0200

DD 50

Cutting the step where Nexus asks to the bank to
confirm their bank account metadata.

Diffstat:
Mdesign-documents/050-libeufin-nexus.rst | 14++++++++++++++
1 file changed, 14 insertions(+), 0 deletions(-)

diff --git a/design-documents/050-libeufin-nexus.rst b/design-documents/050-libeufin-nexus.rst @@ -315,3 +315,17 @@ 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.