diff options
| author | Christian Grothoff <grothoff@gnunet.org> | 2023-12-18 15:55:03 +0800 |
|---|---|---|
| committer | Christian Grothoff <grothoff@gnunet.org> | 2023-12-18 15:58:48 +0800 |
| commit | 7fef4557d0dcda50d6fa7f4da49902caec1f1752 (patch) | |
| tree | 139ff344d1c4b2c89a9ab9db22e7dab121b0c742 /taler-exchange-manual.rst | |
| parent | ac94943039f6cd70cd19b03846f5019d2eecc152 (diff) | |
| download | docs-7fef4557d0dcda50d6fa7f4da49902caec1f1752.tar.gz docs-7fef4557d0dcda50d6fa7f4da49902caec1f1752.tar.bz2 docs-7fef4557d0dcda50d6fa7f4da49902caec1f1752.zip | |
KYC process illustration
Diffstat (limited to 'taler-exchange-manual.rst')
| -rw-r--r-- | taler-exchange-manual.rst | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst index f663a63c..72a4418f 100644 --- a/taler-exchange-manual.rst +++ b/taler-exchange-manual.rst @@ -1308,6 +1308,15 @@ Taler permits an exchange to require KYC data under the following circumstances: * Merchant receives money over a threshold * Reserve is "opened" for invoicing or rewards (**planned feature**) +Any of the above requests can trigger the KYC process, +which can be illustrated as follows: + +.. image:: kyc-process.png + +At the end of the KYC process, the wallet re-tries the +original request, and assuming KYC was successful, the +request should then succeed. + Taler KYC Terminology --------------------- |