View Issue Details

IDProjectCategoryView StatusLast Update
0009487Talerquality checkpointpublic2025-05-10 02:13
ReporterFlorian Dold Assigned Tosebasjm 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
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version1.0Fixed in Version1.0 
Summary0009487: qc merchant KYC
DescriptionThere are a bunch of UX issues with the merchant's KYC page, we should have a look at that.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0009719 closedsebasjm test 0-limit for deposit instant-triggers KYC requirement in SPA 

Activities

Christian Grothoff

2025-04-21 17:34

manager   ~0024635

The SPA failed to detect a change in KYC-requirements after adding a bank account. I had to explicitly reload it (F5) before the KYC needed would show up. Even going to the KYC status page itself failed to show the requirement, the SPA kept using the (outdated, stale) result.

Plus, the rendering of "no kyc required" sucks.

Christian Grothoff

2025-04-21 17:37

manager   ~0024636

Still to be tested: KYC-auth requirement clears when satisfied, KYC-process link shows.

Christian Grothoff

2025-04-21 17:47

manager   ~0024637

After the customer does the wire transfer, the SPA again does not re-fetch the KYC status, instead gets it from the cache *even* on F5. Had to really force the download this time to get the status change from the backend.

Christian Grothoff

2025-04-21 17:51

manager   ~0024638

Despite a soft zero limit on DEPOSIT (!) being returned by the backend, the SPA does *not* expose the KYC-SPA link. However, it really should do this as with a zero-limit on deposit the merchant backend won't do much else...

Christian Grothoff

2025-04-21 19:57

manager   ~0024643

Sebastian says the merchant backend should set the status to "kyc-required" if a deposit/aggregation limit is zero in the backend (instead of "ready") to fix the last point.

Christian Grothoff

2025-04-22 11:44

manager   ~0024648

Merchant backend *should* now return 'kyc-required' (99d75b86..a5c9b6c4). Did NOT test.

sebasjm

2025-04-22 15:20

developer   ~0024649

41abea61f..c261fc1e0

Issue History

Date ModifiedUsernameFieldChange
2025-01-28 10:02Florian DoldNew Issue
2025-01-28 10:02Florian DoldStatusnew => assigned
2025-01-28 10:02Florian DoldAssigned To => Florian Dold
2025-03-21 12:59Florian DoldStatusassigned => acknowledged
2025-03-21 12:59Florian DoldAssigned ToFlorian Dold =>
2025-04-17 19:03Christian GrothoffRelationship addedrelated to 0009719
2025-04-20 21:42Christian GrothoffAssigned To => Christian Grothoff
2025-04-20 21:42Christian GrothoffStatusacknowledged => assigned
2025-04-21 17:34Christian GrothoffNote Added: 0024635
2025-04-21 17:37Christian GrothoffNote Added: 0024636
2025-04-21 17:47Christian GrothoffNote Added: 0024637
2025-04-21 17:51Christian GrothoffNote Added: 0024638
2025-04-21 17:51Christian GrothoffAssigned ToChristian Grothoff => sebasjm
2025-04-21 19:57Christian GrothoffNote Added: 0024643
2025-04-22 11:44Christian GrothoffNote Added: 0024648
2025-04-22 15:20sebasjmStatusassigned => informing
2025-04-22 15:20sebasjmResolutionopen => fixed
2025-04-22 15:20sebasjmNote Added: 0024649
2025-05-10 02:12Christian GrothoffFixed in Version => 1.0
2025-05-10 02:13Christian GrothoffStatusinforming => closed