View Issue Details

IDProjectCategoryView StatusLast Update
0009048Talerexchangepublic2026-02-07 21:36
ReporterChristian Grothoff Assigned ToResolution 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
PrioritylowSeverityfeatureReproducibilityN/A
Status implementingResolutionopen 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Versionpost-2.0 
Summary0009048: introduce a default check and support vATTEST API [4h]
DescriptionA check with the "check_name" of "default" should be configured. This check is
used when users inquire about KYC in the original state before any trigger
thresholds have been passed.

This would require:
1) a new endpoint to allow users to get their access token based only on their (h_)payto -- as kyc-check requires a requirement row.
2) changes to the /kyc-info/ endpoint to return the default check if there is no requirement for the given account/access token
3) documentation updates

This would enable users to do *voluntary* KYC. See *vATTEST*.
Tagssecurity

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

has duplicate 0009879 implementing voluntary measures not implemented 

Activities

Christian Grothoff

2024-08-08 08:45

manager   ~0022952

Relevant previous kyc_logic.c API code fragment (currently removed):
  {
    const struct TALER_KYCLOGIC_KycCheck *check;

    check = find_check ("default");
    if (NULL == check)
    {
      GNUNET_log (GNUNET_ERROR_TYPE_WARNING,
                  "A 'default' check should be defined\n");
    }
  }

Christian Grothoff

2024-09-02 23:11

manager   ~0023146

(1) is done with the latest change to the kyc-check endpoint now using h_payto instead of a requirement row.

Christian Grothoff

2024-09-05 09:57

manager   ~0023165

We now have *voluntary* *measures*. (That can be set as such in the configuration.) That seems saner than 'default checks'.

Christian Grothoff

2025-04-21 20:01

manager   ~0024644

we need to distinguish required nothing-left and you may do something if you want in the KYC-info status for the merchant SPA so that the merchant spa shows the KYC link. Right now, we only have 'ready' (nothing to be done) and 'kyc-required', nothing for 'optional'.

Issue History

Date ModifiedUsernameFieldChange
2024-08-08 08:45Christian GrothoffNew Issue
2024-08-08 08:45Christian GrothoffStatusnew => assigned
2024-08-08 08:45Christian GrothoffAssigned To => Christian Grothoff
2024-08-08 08:45Christian GrothoffNote Added: 0022952
2024-08-08 08:46Christian GrothoffSummaryintroduce a default check => introduce a default check and support vATTEST API
2024-08-08 08:50Christian GrothoffAssigned ToChristian Grothoff =>
2024-08-08 08:50Christian GrothoffStatusassigned => implementing
2024-09-02 23:11Christian GrothoffNote Added: 0023146
2024-09-02 23:11Christian GrothoffTarget Versionpost-1.0 => 0.14
2024-09-02 23:11Christian GrothoffAssigned To => Christian Grothoff
2024-09-02 23:11Christian GrothoffStatusimplementing => assigned
2024-09-04 21:26Christian GrothoffSummaryintroduce a default check and support vATTEST API => introduce a default check and support vATTEST API [4h]
2024-09-05 09:57Christian GrothoffNote Added: 0023165
2024-09-05 11:38Christian GrothoffTarget Version0.14 => post-1.0
2024-09-05 11:45Christian GrothoffAssigned ToChristian Grothoff =>
2024-09-05 11:45Christian GrothoffStatusassigned => implementing
2024-09-16 21:47Christian GrothoffTarget Versionpost-1.0 => 1.2
2025-04-17 20:46Christian GrothoffTag Attached: security
2025-04-17 20:46Christian GrothoffTarget Version1.2 => post-1.0
2025-04-21 20:01Christian GrothoffNote Added: 0024644
2025-05-08 19:37Christian GrothoffRelationship addedhas duplicate 0009879
2026-01-26 05:29Christian GrothoffTarget Versionpost-1.0 => post-2.0
2026-02-07 21:36Christian GrothoffPrioritynormal => low