View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010577 | Taler | merchant backend | public | 2025-11-10 22:54 | 2025-11-11 12:41 |
| Reporter | htgoebel | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Target Version | 1.6 | ||||
| Summary | 0010577: Refund needs identifier or such | ||||
| Description | When managing orders and refunds by a web-shop or ERP system, one needs to keep orders and refunds in sync between the ERP system and the backend. For orders this is done by the API returning an order-ID. For refunds there is no such thing. An ERP system can just guess the mapping passed on the data. Expected: Some way to identify the refund. Propsed solution: Since the RefundDetails already contain a timestamp, I propose to add an optional timestamp field to RefundRequest (much like OrderCommon.timestamp). While still not 100% perfect due to duplicate refunds at the very same time, I expect this to be good enough. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-10 22:54 | htgoebel | New Issue | |
| 2025-11-11 12:29 | Christian Grothoff | Note Added: 0026372 | |
| 2025-11-11 12:41 | Christian Grothoff | Status | new => confirmed |
| 2025-11-11 12:41 | Christian Grothoff | Target Version | => 1.6 |
| 2025-11-11 12:41 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-11-11 12:41 | Christian Grothoff | Status | confirmed => assigned |
| 2025-11-11 12:41 | Christian Grothoff | Status | assigned => confirmed |
