diff options
| author | Christian Grothoff <christian@grothoff.org> | 2022-09-18 11:34:06 +0200 |
|---|---|---|
| committer | Christian Grothoff <christian@grothoff.org> | 2022-09-18 11:34:06 +0200 |
| commit | 561e76a26b1e63e6c604c427799de6a8ae69939d (patch) | |
| tree | 380047de8c63f5a204001e99875d51aab1a9f04c /design-documents/023-taler-kyc.rst | |
| parent | 3f7927f435da3ff89b126f6837b5fb0016025a23 (diff) | |
| download | docs-561e76a26b1e63e6c604c427799de6a8ae69939d.tar.gz docs-561e76a26b1e63e6c604c427799de6a8ae69939d.tar.bz2 docs-561e76a26b1e63e6c604c427799de6a8ae69939d.zip | |
note on #7365
Diffstat (limited to 'design-documents/023-taler-kyc.rst')
| -rw-r--r-- | design-documents/023-taler-kyc.rst | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst index 410c4d85..bfc6e514 100644 --- a/design-documents/023-taler-kyc.rst +++ b/design-documents/023-taler-kyc.rst @@ -17,6 +17,8 @@ banks to identify parties involved in transactions at certain points. Requirements ============ +The solution should support fees to be paid by the user for the KYC process (#7365). + Taler needs to run KYC checks in the following circumstances: * Customer withdraws money over a monthly threshold @@ -38,6 +40,10 @@ Taler needs to run KYC checks in the following circumstances: * key: IBAN (encoded as payto:// URI) +* Reserve is "opened" for invoicing or tipping. + + * key: reserve (=KYC account) long term public key per wallet (encoded as payto:// URI) + Proposed Solution @@ -97,8 +103,8 @@ Access is ``authenticated`` by also passing the hash of the payto://-URI. initiate a KYC process are not very sensitive.) Given this triplet, the ``/kyc-check/`` endpoint returns either the (positive) KYC status or redirects the client (202) to the next required stage of the KYC process. The -redirection must be for an HTTP(S) endpoint to be triggered via a simple HTTP -GET. +redirection must be for an HTTP(S) endpoint to be triggered via a simple HTTP GET. As this endpoint is involved in every KYC check at the beginning, this is also the place where we can +integrate the payment process for the KYC fee. The specific KYC provider to be executed depends on the configuration (see below) which specifies a ``$PROVIDER_SECTION`` for each authentication procedure. @@ -310,6 +316,10 @@ long-poller return with positive news. 128-bit salt values (to keep ``deposits`` table small) and checks for salt to be well-formed should be added "everywhere". +An additional complication will arise once the exchange can trigger a KYC +fee (402) on ``/kyc-check/``. In this case, the merchant SPA must show the QR +code to the merchant to allow the merchant to pay the KYC fee with a wallet. + Bank requirements |