diff options
author | Florian Dold <florian@dold.me> | 2021-09-12 21:51:32 +0200 |
---|---|---|
committer | Florian Dold <florian@dold.me> | 2021-09-12 21:51:32 +0200 |
commit | 078f48f5a9e109a7956f2b46050c906887a293d0 (patch) | |
tree | 25120a5353310b353b8251b08292aaef06cbac1d /design-documents/023-taler-kyc.rst | |
parent | 3aaf257d6d703dab33fe1e6c2e4837e90f3d24a7 (diff) | |
download | docs-078f48f5a9e109a7956f2b46050c906887a293d0.tar.gz docs-078f48f5a9e109a7956f2b46050c906887a293d0.tar.bz2 docs-078f48f5a9e109a7956f2b46050c906887a293d0.zip |
DD23 WIP
Diffstat (limited to 'design-documents/023-taler-kyc.rst')
-rw-r--r-- | design-documents/023-taler-kyc.rst | 76 |
1 files changed, 76 insertions, 0 deletions
diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst new file mode 100644 index 00000000..aba65a9a --- /dev/null +++ b/design-documents/023-taler-kyc.rst @@ -0,0 +1,76 @@ +DD 023: Taler KYC +################# + +Summary +======= + +This document discusses the KYC processes supported by Taler. + + +Motivation +========== + + +Requirements +============ + +Taler needs to run KYC checks in the following circumstances: + +* Customer withdraws money over a monthly threshold + + * exchange triggers KYC + * key: IBAN + +* Wallet receives (via refunds) money over a monthly threshold + + * this is a client-side restriction + * key: reserve public key (generated, long-term) + +* Wallet receives money via P2P payments + + * key: reserve (=KYC account) public key + +* Merchant receives money above a monthly threshold + + * key: IBAN + + +Proposed Solution +================= + +The new taler-kyc-ledger component keeps track of a mapping between an +identifier (as a payto URI?) and a KYC status (yes-merchant, yes-customer, no, +progress (with resume link)). Different identifiers might be mapped by the +bank's KYC provider to the same legal user entity. + +Identifier: + +* IBAN +* reserve / account + +What info do we look at to determine if threshold is crossed / being crossed? + +[ ... ] + +FIXME: Who keeps track of the threshold? +* since the kyc-ledger might be run by the bank and + not the exchange, the thresholds could/should be kept by + the exchange + +* kyc-ledger vs kyc-provider + + +Alternatives +============ + +None unless we want regulatory compliance? + + +Drawbacks +========= + + +Discussion / Q&A +================ + +(This should be filled in with results from discussions on mailing lists / personal communication.) |