View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009078 | Taler | merchant backend | public | 2024-08-15 10:18 | 2025-10-28 23:01 |
| Reporter | how | Assigned To | sebasjm | ||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 0.12 | ||||
| Target Version | 1.5 | ||||
| Summary | 0009078: Default wire transfer delay should be absolute | ||||
| Description | Currently the default wire transfer delay is computed relatively from current date + N. This opens potential accounting and legal issues when delays are shifted, e.g., in the case of irregular payments. E.g., a 90-day invoice limit might be overstepped, or an accounting period miss some late payments. This situation can be alleviated by deciding on a precise transfer day to convert existing relative dates to regular (absolute) calendar dates. | ||||
| Additional Information | Eponym field appears at https://backend.demo.taler.net/webui/#/settings | ||||
| Tags | ux | ||||
| related to | 0009148 | assigned | sebasjm | merchant should have a default refund deadline |
| related to | 0009360 | assigned | Florian Dold | consider computing refund deadline based on payment deadline, not order creation timestamp |
|
|
I'm not sure you actually want it to be absolute, that would give you the same time always. Note that per-order, you already have refund_deadline and pay_deadline and wire_transfer_deadline which ARE absolute. See https://docs.taler.net/core/api-merchant.html#creating-orders in the spec. I think you want a "rounding" value, where the *-deadline is computed automatically rounded to the next minute/hour/day/week/month/year. That's not the same as an 'absolute' time though (in our terminology). Now, I wonder if you missed the above fields, or if we really need to add a per-instance default deadline "rounding" option. Also, do we need just rounding to minute/hour/day/week/month/year, or do we also need offsets (deadline == always 27th of the month, or always at 23:55 each day) in that case? |
|
|
Protocol v23 will add a new "default_wire_rounding_interval" setting to instances which specifies how the wire_transfer_deadline computed via the "default_wire_transfer_delay" is to be rounded up. Note that orders with an explicitly given wire transfer deadline are not subjected to rounding. |
|
|
c2fdcad95404316a673c4fcd5d8ab0f1af7dffbc .. d79af27618a095b7f48f1d5b359dd5f80559e238 add a new DEFAULT_WIRE_TRANSFER_ROUNDING_INTERVAL that allows users to automatically round up computed wire transfer deadlines to the end of the second/minute/hour/day/week/month/quarter or year using the system time of the merchant backend. The new instance setting still needs to be exposed in the SPA => assigning to Sebastian. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-15 10:18 | how | New Issue | |
| 2024-08-15 10:18 | how | Status | new => assigned |
| 2024-08-15 10:18 | how | Assigned To | => Christian Grothoff |
| 2024-08-18 17:53 | Christian Grothoff | Target Version | => 1.0 stretch goals |
| 2024-08-19 08:00 | Christian Grothoff | Note Added: 0022994 | |
| 2024-08-19 08:00 | Christian Grothoff | Status | assigned => feedback |
| 2024-08-19 08:02 | Christian Grothoff | Assigned To | Christian Grothoff => how |
| 2024-09-16 23:51 | Christian Grothoff | Target Version | 1.0 stretch goals => 1.5 |
| 2024-12-07 23:05 | Christian Grothoff | Relationship added | related to 0009360 |
| 2025-03-22 14:09 | Christian Grothoff | Category | mechant backend => merchant backend |
| 2025-04-17 22:45 | Christian Grothoff | Tag Attached: ux | |
| 2025-10-28 20:34 | Christian Grothoff | Note Added: 0026270 | |
| 2025-10-28 23:00 | Christian Grothoff | Note Added: 0026273 | |
| 2025-10-28 23:00 | Christian Grothoff | Assigned To | how => sebasjm |
| 2025-10-28 23:00 | Christian Grothoff | Status | feedback => assigned |
| 2025-10-28 23:01 | Christian Grothoff | Relationship added | related to 0009148 |
