taler-docs

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

commit 13178de76fc409f5aae36747741650781bb7cea6
parent 4a87d6eaf84abe42727038ceca134807ff78cb9c
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Tue, 20 Aug 2024 09:00:22 +0200

also update DD23

Diffstat:
Mdesign-documents/023-taler-kyc.rst | 8+++-----
1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst @@ -947,7 +947,7 @@ description of the high-level process for different providers. # if the provided inputs do not match expectations. # Note that the converter will be expected to output the # set of attributes listed under the respective ``[kyc-check-*]`` - # sections. Calling the converter with ``--list-outputs`` + # sections. Calling the converter with ``-o`` # should generate a (newline-separated) list of attributes # the converter promises to generate in its JSON output # (when run regularly). @@ -1019,10 +1019,8 @@ providers, one per configuration section: # Basically, the check's output is expected to # provide the following fields as attribute inputs into # a subsequent AML program. - # Only given for type FORM; INFO never has any outputs, - # and for type LINK we can obtain the same information - # from the CONVERTER via ``--list-outputs``. - OUTPUTS = business_name street city country registration + # INFO never has any outputs. + OUTPUTS = "business_name street city country registration" # **original** measure to take if the check fails # (for any reason, e.g. provider or form fail to