|
|
| Reporter | vecirex | Assigned To | | |
|---|
| Priority | normal | Severity | major | Reproducibility | always |
|---|
| Status | confirmed | Resolution | open | |
|---|
| Product Version | 1.2 | |
|---|
| Target Version | post-1.0 | |
|---|
|
|
| Summary | 0010627: For exchanges w/ KYC: taler-merchant-kyccheck and "KYC Status" in the UI can be brought out of touch; leading to various issues |
|---|
| Description | The "KYC Status" menu entry in the backoffice/SPA can be made to never show up if the taler-merchant-kyccheck was NOT running when adding TOPS/CHF IBAN account to be verified (which is the use case here).
1.
This can lead to a series of issues, where also @stefan has cases documented where he has IBANs ready to open orders without KYC check ever been completed, leading of course to an "invalid response" by the exchange.
That is, it's possible to setup IBAN accounts without taler-merchant-kyccheck running and without ever seeing a "KYC Status" menu, leading to behaviour which normal shop owners cannot grasp.
Such an added IBAN account can also not be fixed to work and be made verified after the taler-merchant-kyccheck component was made available. The "KYC Status" menu entry just doesn't show up, instead "no kyc required" messages appear: @stefan can add screenshot of his test cases.
2.
On the other hand, if the IBAN was added with taler-merchant-kyccheck running, then the "KYC Status" sticks there even if taler-merchant-kyccheck is not running anymore, e.g., killing it soon after addition of the IBAN which must be verified to be able to receive payments as a shop owner. That is, nothing is shown for the shop operator that KYC Status will never be updated: this can also make support cases difficult, if in the end it's because of the taler-merchant-kyccheck component not running for any reason. |
|---|
| Steps To Reproduce | To see if taler-merchant-kyccheck is running:
root@bcead3ae4f5e:/var/taler-src/gnunet# su -s /bin/bash taler-merchant-httpd
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$ echo $USER
taler-merchant-httpd
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$ ps -axw | grep taler-me
rchant-kyccheck
135263 pts/1 S 0:00 taler-merchant-kyccheck
136180 pts/2 S+ 0:00 grep taler-merchant-kyccheck
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$
Fine by process 135263 in above's case.
Having added an IBAN number in the UI, particularly in the case of TOPS/CHF, the "KYC Status" menu entry is clearly required and it shows up -- upon addition of a bank account of IBAN type, for the TOPS/CHF case starting with prefix "CH". See screenshot.
Killing taler-merchant-kyccheck by
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$ pkill -9 taler-merchant
-kyccheck
pkill: pattern that searches for process name longer than 15 characters will res
ult in zero matches
Try `pkill -f' option to match against the complete command line.
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$ pkill -9 -f taler-merchant-kyccheck
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$ ps -axw | grep taler-merchant-kyccheck
136207 pts/2 S+ 0:00 grep taler-merchant-kyccheck
taler-merchant-httpd@bcead3ae4f5e:/var/taler-src/gnunet$
leads to the button in the UI either to stay (case 1 above), but not show updates (forever), or just never appear and lead to unusable IBAN accounts leading to errors when creating orders.
|
|---|
| Additional Information | Better would be to always show the "KYC Status" iff the exchange communicates to require KYC, and then state that taler-merchant-kyccheck component is needed for this exchange, but it's not running. Maybe it's to easier to just always show the KYC menu entry, and if the merchant learns from the exchange it's not needed to just say there: for all accouns configured on this merchant, no KYC is required by the exchange.
As a further solution, it should be said to the shop owner / merchant operator to contact the system administrator / operator and ideally link to https://docs.taler.net/taler-merchant-manual.html#launching-the-backend with changes from 0010624, making clear that taler-merchant-kyccheck must be around for the menu entry to load actual KYC payload (as in: status info, steps to do, additional buttons to refresh etc.). |
|---|
| Tags | No tags attached. |
|---|
|
|
