View Issue Details

IDProjectCategoryView StatusLast Update
0009156Talerexchange AML officer webuipublic2024-09-17 14:29
ReporterChristian Grothoff 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
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version0.14Fixed in Version0.14 
Summary0009156: allow AML decisions for unknown accounts
DescriptionFor this we need to add the payto_uri to AML decisions, at least as an optional parameter.
We should also consider returning the payto_uri with AML GET requests, so that the SPA has it and can use it
in decisions -- then we can stop using h_payto entirely and give AML officers more information.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2024-09-05 11:29

manager   ~0023168

docs.git::f32c3721..01e50cf6 adds the "payto_uri" field to AML decisions so that the AML SPA can post decisions for accounts previously unknown to the exchange.

Christian Grothoff

2024-09-05 11:30

manager   ~0023169

exchange.git :: c39040ad..a666b706 implements support in the exchange.

Christian Grothoff

2024-09-05 11:32

manager   ~0023170

@sebasjm: please extend the AML SPA to allow the user to enter a payto:// URI (and/or select IBAN/x-taler-bank and then enter the account details like the IBAN/username) and based on that make AML decisions for new accounts. You will need to compute the payto hash, if that is non-trivial, we can modify the exchange API to make passing the payto-hash optional (let me know!).

sebasjm

2024-09-11 15:19

developer   ~0023248

f401ab076..e2ede9ff4

but the backend replies with 404 when the decision is posted (including the payto string) EVEN if the decision is correctly saved.

issue on the way

Issue History

Date ModifiedUsernameFieldChange
2024-09-02 22:14Christian GrothoffNew Issue
2024-09-02 22:14Christian GrothoffStatusnew => assigned
2024-09-02 22:14Christian GrothoffAssigned To => Christian Grothoff
2024-09-05 11:29Christian GrothoffNote Added: 0023168
2024-09-05 11:30Christian GrothoffNote Added: 0023169
2024-09-05 11:30Christian GrothoffAssigned ToChristian Grothoff => sebasjm
2024-09-05 11:32Christian GrothoffNote Added: 0023170
2024-09-05 12:21Christian GrothoffCategoryexchange => exchange AML backoffice (SPA)
2024-09-11 15:19sebasjmStatusassigned => informing
2024-09-11 15:19sebasjmResolutionopen => fixed
2024-09-11 15:19sebasjmNote Added: 0023248
2024-09-13 23:08Christian GrothoffFixed in Version => 0.14
2024-09-17 14:29Christian GrothoffStatusinforming => closed
2026-08-23 14:17Florian DoldCategoryexchange AML backoffice (SPA) => exchange AML officer webui