View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008557Talerexchangepublic2024-03-03 13:472024-08-28 21:31
ReporterChristian Grothoff Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.13Fixed in Version0.13 
Summary0008557: support more complex KYC flows [1d!]
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.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2024-08-08 21:09

manager   ~0022957

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.

Issue History

Date ModifiedUsernameFieldChange
2024-03-03 13:47Christian GrothoffNew Issue
2024-03-03 13:47Christian GrothoffStatusnew => assigned
2024-03-03 13:47Christian GrothoffAssigned To => Christian Grothoff
2024-04-14 23:06Christian GrothoffTarget Versionpost-1.0 => 0.11
2024-04-23 16:08Christian GrothoffSummarysupport more complex KYC flows => support more complex KYC flows [30d!]
2024-05-05 13:40Christian GrothoffTarget Version0.11 => 0.14
2024-05-13 19:19Christian GrothoffTarget Version0.14 => 0.13
2024-07-17 11:55Christian GrothoffSummarysupport more complex KYC flows [30d!] => support more complex KYC flows [20d!]
2024-07-25 22:24Christian GrothoffSummarysupport more complex KYC flows [20d!] => support more complex KYC flows [15d!]
2024-07-26 15:44Christian GrothoffSummarysupport more complex KYC flows [15d!] => support more complex KYC flows [12d!]
2024-07-27 21:07Christian GrothoffSummarysupport more complex KYC flows [12d!] => support more complex KYC flows [10d!]
2024-07-28 18:39Christian GrothoffSummarysupport more complex KYC flows [10d!] => support more complex KYC flows [9d!]
2024-07-30 20:48Christian GrothoffSummarysupport more complex KYC flows [9d!] => support more complex KYC flows [6d!]
2024-08-03 16:55Christian GrothoffSummarysupport more complex KYC flows [6d!] => support more complex KYC flows [5d!]
2024-08-04 15:12Christian GrothoffSummarysupport more complex KYC flows [5d!] => support more complex KYC flows [4d!]
2024-08-07 10:51Christian GrothoffSummarysupport more complex KYC flows [4d!] => support more complex KYC flows [3d!]
2024-08-07 17:57Christian GrothoffSummarysupport more complex KYC flows [3d!] => support more complex KYC flows [2d!]
2024-08-08 08:52Christian GrothoffSummarysupport more complex KYC flows [2d!] => support more complex KYC flows [1d!]
2024-08-08 21:09Christian GrothoffStatusassigned => informing
2024-08-08 21:09Christian GrothoffResolutionopen => fixed
2024-08-08 21:09Christian GrothoffFixed in Version => 0.13
2024-08-08 21:09Christian GrothoffNote Added: 0022957
2024-08-28 21:31Christian GrothoffStatusinforming => closed
Powered by locust
Contact administrator for assistance
User Documentation