View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008881 | Taler | wallet-core | public | 2024-05-29 13:15 | 2025-04-23 23:06 |
| Reporter | Florian Dold | 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 | feature | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0008881: add better/high-level wallet-core request to check B-i withdrawal status | ||||
| Description | We should probably have a high-level version of getWithdrawalDetailsForUri that returns a discriminated union for the following cases: - withdrawal aborted or completed by another wallet (could also be an exception) - withdrawal already accepted by *this* wallet in case the user somehow scans the same QR code again (with the transaction ID of the existing withdrawal transaction) - withdrawal can be accepted (with same data as above, but without the status field value from the bank) | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-05-29 13:15 | Florian Dold | New Issue | |
| 2024-05-29 13:15 | Florian Dold | Status | new => assigned |
| 2024-05-29 13:15 | Florian Dold | Assigned To | => Florian Dold |
| 2024-06-30 22:05 | Florian Dold | Severity | minor => feature |
| 2024-07-09 11:00 | Florian Dold | Target Version | 0.13 => post-1.0 |
| 2025-04-23 23:06 | Christian Grothoff | Assigned To | Florian Dold => |
| 2025-04-23 23:06 | Christian Grothoff | Status | assigned => implementing |