View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011484 | Taler | quality checkpoint | public | 2026-06-06 02:03 | 2026-07-03 14:21 |
| Reporter | vecirex | Assigned To | vecirex | 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 | low | Severity | feature | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | 1.8 | ||||
| Summary | 0011484: Notify merchants of relevant changes to the instance (like IBAN no.) [QC] | ||||
| Description | Regardless of who did the changes, alterations of relevant information like the IBAN(s) used (where paid orders go to, by settlements) should be accompanied by notifications to the tan channels defined, like sms and email. | ||||
| Additional Information | The merchant like this has a chance to react before any bank transfers are conducted from the exchange to any (new) IBAN no.; despite attacks, this is also helpful to check the defined IBAN again, which might also be helpful if a merchant has various IBAN numbers. | ||||
| Tags | quality | ||||
| related to | 0011483 | closed | Christian Grothoff | Adding another IBAN requires MFA, but can be circumvented |
| This ticket relates and also mitigates 0011483, but should be introduced IMHO even if fixed. | |
| e9d4f601..b63b1ec2 implements the core logic for such notifications. However, I did *not* test it. We should test this together with the QC for KYC-status-change notifications! | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-06-06 02:03 | vecirex | New Issue | |
| 2026-06-06 02:07 | vecirex | Summary | Notify changes to certain merchant settings (like IBAN no.) => Notify merchants of relevant changes to the instance (like IBAN no.) |
| 2026-06-06 02:07 | vecirex | Additional Information Updated | |
| 2026-06-06 02:08 | vecirex | Note Added: 0028792 | |
| 2026-06-06 02:08 | vecirex | Relationship added | related to 0011483 |
| 2026-06-06 16:25 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2026-06-06 16:25 | Christian Grothoff | Status | new => implementing |
| 2026-06-06 16:25 | Christian Grothoff | Target Version | => 1.8 |
| 2026-06-14 17:50 | Christian Grothoff | Status | implementing => assigned |
| 2026-06-15 21:31 | Christian Grothoff | Note Added: 0028905 | |
| 2026-06-15 21:31 | Christian Grothoff | Assigned To | Christian Grothoff => vecirex |
| 2026-06-15 21:31 | Christian Grothoff | Category | merchant backend => quality checkpoint |
| 2026-06-15 21:32 | Christian Grothoff | Summary | Notify merchants of relevant changes to the instance (like IBAN no.) => Notify merchants of relevant changes to the instance (like IBAN no.) [QC] |
| 2026-06-15 21:32 | Christian Grothoff | Priority | normal => low |
| 2026-06-15 21:32 | Christian Grothoff | Status | assigned => implementing |
| 2026-07-03 14:21 | vecirex | Tag Attached: quality |