View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008557 | Taler | exchange | public | 2024-03-03 14:47 | 2024-08-28 23:31 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0008557: support more complex KYC flows [1d!] | ||||
| Description | Right now, every KYC operation does exactly one exchange-selected KYC operation. However, for example, to check Swiss-ness, we could allow SMS *or* address validation. This should be the choice of the user, instead of right now where the exchange makes a decision and then the user has no choice of validation method. Another case is where we have multiple KYC requirements and a single KYC provider cannot check all of them. Right now, we always redirect at the end of a KYC process to a "success" page, which will be confusing if afterwards we actually have additional KYC requirements. We should design and implement a more guided process to handle more complex KYC flows (especially and/or). | ||||
| Tags | No tags attached. | ||||
|
|
It is done. More tests needed, likely small bugs, but the big lines are all implemented, some tests exists, and the documentation was also updated. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-03 14:47 | Christian Grothoff | New Issue | |
| 2024-03-03 14:47 | Christian Grothoff | Status | new => assigned |
| 2024-03-03 14:47 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-04-15 01:06 | Christian Grothoff | Target Version | post-1.0 => 0.11 |
| 2024-04-23 18:08 | Christian Grothoff | Summary | support more complex KYC flows => support more complex KYC flows [30d!] |
| 2024-05-05 15:40 | Christian Grothoff | Target Version | 0.11 => 0.14 |
| 2024-05-13 21:19 | Christian Grothoff | Target Version | 0.14 => 0.13 |
| 2024-07-17 13:55 | Christian Grothoff | Summary | support more complex KYC flows [30d!] => support more complex KYC flows [20d!] |
| 2024-07-26 00:24 | Christian Grothoff | Summary | support more complex KYC flows [20d!] => support more complex KYC flows [15d!] |
| 2024-07-26 17:44 | Christian Grothoff | Summary | support more complex KYC flows [15d!] => support more complex KYC flows [12d!] |
| 2024-07-27 23:07 | Christian Grothoff | Summary | support more complex KYC flows [12d!] => support more complex KYC flows [10d!] |
| 2024-07-28 20:39 | Christian Grothoff | Summary | support more complex KYC flows [10d!] => support more complex KYC flows [9d!] |
| 2024-07-30 22:48 | Christian Grothoff | Summary | support more complex KYC flows [9d!] => support more complex KYC flows [6d!] |
| 2024-08-03 18:55 | Christian Grothoff | Summary | support more complex KYC flows [6d!] => support more complex KYC flows [5d!] |
| 2024-08-04 17:12 | Christian Grothoff | Summary | support more complex KYC flows [5d!] => support more complex KYC flows [4d!] |
| 2024-08-07 12:51 | Christian Grothoff | Summary | support more complex KYC flows [4d!] => support more complex KYC flows [3d!] |
| 2024-08-07 19:57 | Christian Grothoff | Summary | support more complex KYC flows [3d!] => support more complex KYC flows [2d!] |
| 2024-08-08 10:52 | Christian Grothoff | Summary | support more complex KYC flows [2d!] => support more complex KYC flows [1d!] |
| 2024-08-08 23:09 | Christian Grothoff | Status | assigned => resolved |
| 2024-08-08 23:09 | Christian Grothoff | Resolution | open => fixed |
| 2024-08-08 23:09 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-08 23:09 | Christian Grothoff | Note Added: 0022957 | |
| 2024-08-28 23:31 | Christian Grothoff | Status | resolved => closed |
