summaryrefslogtreecommitdiff
path: root/template
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2023-05-16 12:11:25 +0200
committerChristian Grothoff <christian@grothoff.org>2023-05-16 12:11:25 +0200
commit56dad093a37be94a6a668ccd3d810bf4bb2d4fdd (patch)
tree7544e01fb799d063d69c45238ee7a558fbcad8a6 /template
parent1129110ee0d47089437b9706794552fb9766771c (diff)
downloadwww-56dad093a37be94a6a668ccd3d810bf4bb2d4fdd.tar.gz
www-56dad093a37be94a6a668ccd3d810bf4bb2d4fdd.tar.bz2
www-56dad093a37be94a6a668ccd3d810bf4bb2d4fdd.zip
comment
Diffstat (limited to 'template')
-rw-r--r--template/kyc.html.j260
1 files changed, 37 insertions, 23 deletions
diff --git a/template/kyc.html.j2 b/template/kyc.html.j2
index bda2f2b9..fded22aa 100644
--- a/template/kyc.html.j2
+++ b/template/kyc.html.j2
@@ -57,9 +57,40 @@
additional data collected, can profiles be easily deleted, etc.). However,
already the above list narrows down the field to basically nobody.
</p>
- <h3>Providers</h3>
+ <h3>Supported Providers</h3>
<p>
- Here is a list of KYC solutions we have found and evaluated against the
+ These are the KYC solutions for which a GNU Taler integration is
+ available or under active development:
+ <table>
+ <tr><td></td>
+ <th>KYC?</th><th>Open API?</th><th>Web?</th>
+ <th>Standard API?</th><th>FLOSS client?</th><th>Pricing?</th>
+ <th>FLOSS server?</th></tr>
+ <tr><th><a href="https://git.taler.net/challenger.git/">Challenger</a></th>
+ <td>&#10060;</td><td>&#9989;</td><td>&#9989;</td>
+ <td>&#9989;</td><td>&#9989;</td><td>free</td>
+ <td>&#9989;</td></tr>
+ <tr><th>kycaid.com</th>
+ <td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
+ <td>&#10060;</td><td>&#10060;</td><td>&#9989;</td>
+ <td>&#10060;</td></tr>
+ <tr><th>withpersona.com</th>
+ <td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
+ <td>&#10060;</td><td>some</td><td>some</td>
+ <td>&#10060;</td></tr>
+ </table>
+ Challenger is our own home-brewed address validation service
+ (under development).
+ We additionally selected KYCAID and WithPersona for our
+ first implementations as they seem closest to our objectives
+ (see below for lists of other providers we considered),
+ and we needed <em>some</em> KYC support.
+ That said, there is room for improvement for both of these
+ solutions towards respecting their user's freedom.
+ </p>
+ <h3>Other providers</h3>
+ <p>
+ Here is a list of other KYC solutions we have found and evaluated against the
criteria above.
<table>
<tr><td></td>
@@ -90,10 +121,6 @@
<td>&#9989;</td><td>&#10060;</td><td>&#9989;</td>
<td>&#10060;</td><td>&#10060;</td><td>&#9989;</td>
<td>&#10060;</td></tr> <!-- consider -->
- <tr><th>kycaid.com</th>
- <td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
- <td>&#10060;</td><td>&#10060;</td><td>&#9989;</td>
- <td>&#10060;</td></tr>
<tr><th>metamap.com</th>
<td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
<td>&#10060;</td><td>&#10060;</td><td>&#10060;</td>
@@ -110,7 +137,7 @@
<td>&#9989;</td><td>&#9989;</td><td>&#10060;</td>
<td>&#10060;</td><td>&#10060;</td><td>&#10060;</td>
<td>&#10060;</td></tr>
- <tr><th>SumSub</th>
+ <tr><th>SumSub.com</th>
<td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
<td>&#10060;</td><td>&#10060;</td><td>&#9989;</td>
<td>&#10060;</td></tr>
@@ -126,7 +153,7 @@
<td>&#9989;</td><td>&#10060;</td><td>?</td>
<td>&#10060;</td><td>&#10060;</td><td>&#10060;</td>
<td>&#10060;</td></tr>
- <tr><th>Ondato</th>
+ <tr><th>Ondato.com</th>
<td>&#9989;</td><td>&#10060;</td><td>?</td>
<td>&#10060;</td><td>&#10060;</td><td>&#9989;</td>
<td>&#10060;</td></tr>
@@ -134,15 +161,7 @@
<td>&#9989;</td><td>&#9989;</td><td>?</td>
<td>&#10060;</td><td>some</td><td>&#10060;</td>
<td>&#10060;</td></tr>
- <tr><th>withpersona.com</th>
- <td>&#9989;</td><td>&#9989;</td><td>&#9989;</td>
- <td>&#10060;</td><td>some</td><td>some</td>
- <td>&#10060;</td></tr>
</table>
- Of these, we have for now selected KYCAID and WithPersona for our
- first implementations as they seem closest to our objectives.
- That said, the room for improvement for both towards respecting
- their user's freedoms is huge.
</p>
<h3>Not quite KYC Providers</h3>
<p>
@@ -156,18 +175,13 @@
would not usually satisfy the legal requirements.
These providers
are only listed so that they do not get re-evaluated as they
- came up in a search.
+ came up in a search (and it took time to understand that
+ they do not actually offer KYC).
<table>
<tr><td></td>
<th>KYC?</th><th>Open API?</th><th>Web?</th>
<th>Standard API?</th><th>FLOSS client?</th><th>Pricing?</th>
<th>FLOSS server?</th></tr>
- <!--
- <tr><th></th>
- <td></td><td></td><td></td>
- <td></td><td></td><td></td>
- <td></td></tr>
- -->
<tr><th>accubits/smart-kyc</th>
<td>&#10060;</td><td>&#9989;</td><td>&#9989;</td>
<td>&#10060;</td><td>&#9989;</td><td>free</td>