View Issue Details

IDProjectCategoryView StatusLast Update
0009487Talerquality checkpointpublic2025-04-22 17:20
ReporterFlorian Dold Assigned Tosebasjm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionfixed 
Target 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.

Relationships

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

Activities

Christian Grothoff

2025-04-21 19: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 19:37

manager   ~0024636

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

Christian Grothoff

2025-04-21 19: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 19: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 21: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 13:44

manager   ~0024648

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

sebasjm

2025-04-22 17:20

developer   ~0024649

41abea61f..c261fc1e0

Issue History

Date Modified Username Field Change
2025-01-28 11:02 Florian Dold New Issue
2025-01-28 11:02 Florian Dold Status new => assigned
2025-01-28 11:02 Florian Dold Assigned To => Florian Dold
2025-03-21 13:59 Florian Dold Status assigned => acknowledged
2025-03-21 13:59 Florian Dold Assigned To Florian Dold =>
2025-04-17 21:03 Christian Grothoff Relationship added related to 0009719
2025-04-20 23:42 Christian Grothoff Assigned To => Christian Grothoff
2025-04-20 23:42 Christian Grothoff Status acknowledged => assigned
2025-04-21 19:34 Christian Grothoff Note Added: 0024635
2025-04-21 19:37 Christian Grothoff Note Added: 0024636
2025-04-21 19:47 Christian Grothoff Note Added: 0024637
2025-04-21 19:51 Christian Grothoff Note Added: 0024638
2025-04-21 19:51 Christian Grothoff Assigned To Christian Grothoff => sebasjm
2025-04-21 21:57 Christian Grothoff Note Added: 0024643
2025-04-22 13:44 Christian Grothoff Note Added: 0024648
2025-04-22 17:20 sebasjm Status assigned => resolved
2025-04-22 17:20 sebasjm Resolution open => fixed
2025-04-22 17:20 sebasjm Note Added: 0024649