taler-docs

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

commit 36bba29282a8b64f2f1715782676e5d9d999db40
parent d29126c515ff34bd47a82c7cfeff9f92c2c758f1
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Sun, 30 Jul 2023 14:53:36 +0200

DD45: add note re: alternative ways to set age-restriction

Diffstat:
Mdesign-documents/045-kyc-inheritance.rst | 9++++++---
1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/design-documents/045-kyc-inheritance.rst b/design-documents/045-kyc-inheritance.rst @@ -145,7 +145,7 @@ Definition of Done ================== For the exchange, the implementation of the configuration option and the -endpoint, and corresponding unit tests in `src/testing` are necessary. +endpoint, and corresponding unit tests in ``src/testing`` are necessary. For the wallet: TODO. @@ -165,9 +165,12 @@ Discussion / Q&A The proposed solution makes the principle of subsidiarty for age-restrictions (i.e parents are responsible for setting the age-restriction) explicit in the -code. +code. However, the proposed solution does not exclude the possibility for other +ways to set age-restriction in the wallet. For example, parents who do _not_ +have a Taler wallet, must still be able to assist their children with the +settings of age-restriction during the withdraw process. + It also simplifies the KYC process for many situations for customers: Families members and partners benefit from it. -