View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010032 | Taler | exchange AML officer webui | public | 2025-05-26 21:49 | 2025-08-31 17:10 |
| Reporter | Florian Dold | Assigned To | sebasjm | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.0 stretch goals | Fixed in Version | 1.0 stretch goals | ||
| Summary | 0010032: AML SPA does not show account AML status in AML SPA despite successful KYC auth and access token | ||||
| Description | When a merchant completes KYC auth, hits a deposit zero-limit and receives an auth token, the exchange clearly knows something about the merchant. However, this info doesn't show up anywhere in the AML SPA. We don't have a decision yet at this point, but we should be able to return some state for the account, even if it's not a proper decision, as we clearly have active legi measures for it. Maybe `GET /aml/$OFFICER_PUB/legitimizations` is the right endpoint for the SPA to query? | ||||
| Tags | compliance | ||||
| related to | 0010031 | closed | sebasjm | AML SPA should also show KYC auth transfers under transfers page |
| child of | 0008155 | closed | Christian Grothoff | acceptance testing of SPA with MG [Feb 7th, 11am CET] |
| Alternatively, we could consider a new end point that combines decisions and legitimizations into an AML account status. The old endpoints would still be useful for historic information, but to list AML accounts, we'd use the new one. | |
| Or alternatively, maybe easier: We just create an initial decision with default rules! | |
| *If* we do this, it would be important to represent the default rules via a "NULL" in the database. But I'm not sure that makes sense yet. | |
| I think the better answer (also related to 0010031) is to add a per-account filter to the /aml/$OFFICER_PUB/transfers-* endpoints, allowing the SPA to easily query all wire transfers related to any account. | |
| taler-docs :: ff649e17..902a35ca adds a per-account filter to the /aml/$OPUB/transfer-* endpoints so that the AML SPA can easily obtain a list of all incoming/outgoing/kycauth transfers per account and add those to the account details page of the SPA. IMO that should address this issue nicely, as it would show us that the KYC auth transfer has happened (plus of course we have the default rules now returned, so we know that if there was no other decision, the default rules apply and can show those). Note that IMO 0010031 is about showing the lists of all wire transfers (kycauth/credit/debit) globally (unfiltered by account), while this issue should then be read as showing the wire transfers per-account on the per-account page. | |
| exchange :: 250a2376b..1c53b0276 implements the new per-account filter for the transactions. | |
| 5c66655f9..effe8b919 links account details with transfers and back | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-26 21:49 | Florian Dold | New Issue | |
| 2025-05-26 21:52 | Florian Dold | Note Added: 0025014 | |
| 2025-05-27 07:06 | Christian Grothoff | Tag Attached: compliance | |
| 2025-05-27 07:06 | Christian Grothoff | Status | new => implementing |
| 2025-05-27 07:49 | Florian Dold | Note Added: 0025018 | |
| 2025-06-03 21:14 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-06-03 21:14 | Christian Grothoff | Status | implementing => assigned |
| 2025-06-04 22:20 | Christian Grothoff | Summary | AML SPA does not show account AML status in AML SPA despite successful KYC auth and access token => AML SPA does not show account AML status in AML SPA despite successful KYC auth and access token [8h], 25.6.25 |
| 2025-06-11 20:38 | Christian Grothoff | Product Version | => 1.0 |
| 2025-06-12 07:07 | Christian Grothoff | Note Added: 0025213 | |
| 2025-06-12 07:14 | Christian Grothoff | Relationship added | related to 0010031 |
| 2025-06-12 07:19 | Christian Grothoff | Note Added: 0025214 | |
| 2025-06-12 07:41 | Christian Grothoff | Note Added: 0025217 | |
| 2025-06-12 07:41 | Christian Grothoff | Note Added: 0025218 | |
| 2025-06-12 07:45 | Christian Grothoff | Assigned To | Christian Grothoff => sebasjm |
| 2025-06-12 07:45 | Christian Grothoff | Category | exchange => exchange AML backoffice (SPA) |
| 2025-06-12 07:45 | Christian Grothoff | Summary | AML SPA does not show account AML status in AML SPA despite successful KYC auth and access token [8h], 25.6.25 => AML SPA does not show account AML status in AML SPA despite successful KYC auth and access token |
| 2025-06-12 07:47 | Christian Grothoff | Relationship added | child of 0008155 |
| 2025-06-12 07:47 | Christian Grothoff | Target Version | 1.1 => 1.0 stretch goals |
| 2025-06-12 15:28 | sebasjm | Status | assigned => informing |
| 2025-06-12 15:28 | sebasjm | Resolution | open => fixed |
| 2025-06-12 15:28 | sebasjm | Note Added: 0025227 | |
| 2025-08-31 17:09 | Christian Grothoff | Status | informing => closed |
| 2025-08-31 17:10 | Christian Grothoff | Fixed in Version | => 1.0 stretch goals |
| 2026-08-23 14:17 | Florian Dold | Category | exchange AML backoffice (SPA) => exchange AML officer webui |