View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009956 | Taler | merchant backend | public | 2025-05-14 11:48 | 2026-02-07 21:57 |
| Reporter | Bohdan | Assigned To | 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 | tweak | Reproducibility | have not tried |
| Status | acknowledged | Resolution | open | ||
| Product Version | 1.0 | ||||
| Target Version | post-2.0 | ||||
| Summary | 0009956: Error for the exchange being not available are not descriptive enough in the taler-merchant-exchangekeyupdate | ||||
| Description | The message that is shown when the exchange is down is generic and next: { "code": 2509, "hint": "The backend does not trust any exchange that would allow funds to be wired to any bank account of this instance using the wire method specified with the order. (Note that right now, we do not support the use of exchange bank accounts with mandatory currency conversion.) One likely cause for this is that the taler-merchant-exchangekeyupdate process is not running.", "detail": "iban" } I believe it needs to be adapted to display the error in more detail. And be actually different for different situations... | ||||
| Steps To Reproduce | 1. Put the exchange down 2. Try to create the order 3. Get the error | ||||
| Tags | ux | ||||
| related to | 0010988 | closed | Christian Grothoff | when an exchange is not reachable, merchant backend does not expose any error |
| related to | 0011026 | informing | Florian Dold | expand SPA with list of exchanges and status information from new /exchanges endpoint |
| related to | 0009746 | informing | Christian Grothoff | improve error reporting when order can't be created due to wire method mismatch |
| We should review this if it is still an issue after 0011026 is implemented. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-14 11:48 | Bohdan | New Issue | |
| 2025-05-14 18:31 | Christian Grothoff | Status | new => implementing |
| 2025-05-14 18:31 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.5 |
| 2025-10-22 19:39 | Christian Grothoff | Severity | minor => tweak |
| 2025-10-22 19:39 | Christian Grothoff | Status | implementing => acknowledged |
| 2025-10-23 10:57 | Christian Grothoff | Target Version | 1.5 => post-2.0 |
| 2026-02-07 21:55 | Christian Grothoff | Relationship added | related to 0010988 |
| 2026-02-07 21:55 | Christian Grothoff | Relationship added | related to 0011026 |
| 2026-02-07 21:55 | Christian Grothoff | Tag Attached: ux | |
| 2026-02-07 21:56 | Christian Grothoff | Note Added: 0027650 | |
| 2026-02-07 21:57 | Christian Grothoff | Relationship added | related to 0009746 |