View Issue Details

IDProjectCategoryView StatusLast Update
0008557Talerexchangepublic2024-05-13 21:19
ReporterChristian Grothoff Assigned ToChristian Grothoff  
PrioritynormalSeverityfeatureReproducibilityN/A
Status assignedResolutionopen 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.13 
Summary0008557: support more complex KYC flows [30d!]
DescriptionRight 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).
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

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