View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009360 | Taler | merchant backend | public | 2024-11-27 15:14 | 2025-12-21 20:46 |
| 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 | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.3 | Fixed in Version | 1.3 | ||
| Summary | 0009360: consider computing refund deadline based on payment deadline, not order creation timestamp | ||||
| Description | That way we guarantee that the user always has at least the time span defined by `refund_delay` to ask for a refund. (Suggested during QC, rationale is that the user might pay minutes after scanning the QR code, and when the refund deadline would have already expired.) | ||||
| Tags | ux | ||||
| Semantics will change to be cumulative for all delays, so pay_delay on top of order creation, refund_delay on top of payment deadline, wire_transfer_delay on top of the refund deadline, and then (see 0009078) the final wire transfer deadline may be subject to rounding up based on a default_wire_rounding_interval. (as of v23). | |
| c2fdcad95404316a673c4fcd5d8ab0f1af7dffbc .. d79af27618a095b7f48f1d5b359dd5f80559e238 implement the new cumulative delay logic. This still requires changes to the wallet-core testsuite, hence assigning now to Florian. | |
| The tests have been adjusted. Is there anything else to do? UI / documentation? | |
| The refund_delay now can be any value, and is no longer constrained by the wire_delay or pay_delay, as they are each additive. So Sebastian: please remove the corresponding constraints from the merchant SPA. | |
| d3a94fe62 | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-11-27 15:14 | Florian Dold | New Issue | |
| 2024-11-27 15:14 | Florian Dold | Status | new => assigned |
| 2024-11-27 15:14 | Florian Dold | Assigned To | => Christian Grothoff |
| 2024-11-28 23:02 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2024-11-28 23:02 | Christian Grothoff | Status | assigned => implementing |
| 2024-12-07 22:04 | Christian Grothoff | Target Version | post-1.0 => 1.5 |
| 2024-12-07 22:05 | Christian Grothoff | Relationship added | related to 0009078 |
| 2025-01-02 12:01 | Christian Grothoff | Severity | minor => tweak |
| 2025-03-22 13:09 | Christian Grothoff | Category | mechant backend => merchant backend |
| 2025-04-17 20:45 | Christian Grothoff | Tag Attached: ux | |
| 2025-10-22 19:41 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-10-22 19:41 | Christian Grothoff | Status | implementing => assigned |
| 2025-10-28 19:35 | Christian Grothoff | Note Added: 0026271 | |
| 2025-10-28 21:59 | Christian Grothoff | Note Added: 0026272 | |
| 2025-10-28 21:59 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2025-11-14 19:36 | Florian Dold | Assigned To | Florian Dold => |
| 2025-11-14 19:36 | Florian Dold | Status | assigned => feedback |
| 2025-11-14 19:36 | Florian Dold | Note Added: 0026443 | |
| 2025-11-28 21:23 | Christian Grothoff | Note Added: 0026674 | |
| 2025-11-28 21:23 | Christian Grothoff | Assigned To | => sebasjm |
| 2025-11-28 21:23 | Christian Grothoff | Status | feedback => assigned |
| 2025-12-12 12:02 | sebasjm | Status | assigned => informing |
| 2025-12-12 12:02 | sebasjm | Resolution | open => fixed |
| 2025-12-12 12:02 | sebasjm | Note Added: 0026936 | |
| 2025-12-15 10:45 | Christian Grothoff | Target Version | 1.5 => 1.3 |
| 2025-12-15 10:46 | Christian Grothoff | Fixed in Version | => 1.3 |
| 2025-12-21 20:46 | Christian Grothoff | Status | informing => closed |