View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010577 | Taler | merchant backend | public | 2025-11-10 22:54 | 2026-06-30 13:02 |
| Reporter | htgoebel | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0010577: Refund needs identifier or such [4d] | ||||
| 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. | ||||
|
|
We could just return the row ID of the refund operation, that'd be unique. |
|
|
Note that a single refund may result in multiple DB entries, one per coin impacted. So this would be multiple row IDs. |
|
|
I'm pushing on this, since I have concrete user story: Orders and refunds are managed by the ERP system. Now (for whatever reason) a refund is created directly in the Merchant Backend. Any refund created this way needs to be mirrored in the ERP system to ensure accounting matches the Merchatn Backend. For this, the ERP system needs some refund identifier. The refund timestamp would be okay, since refunds are always related to a order. Since the RefundDetails already include a timestamp. I propose to return this timestamp - or return a RefundDetails struct. |
| 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 |
| 2025-11-22 08:50 | Christian Grothoff | Note Added: 0026577 | |
| 2025-11-28 22:14 | Christian Grothoff | Summary | Refund needs identifier or such => Refund needs identifier or such [4d] |
| 2025-12-07 01:00 | Christian Grothoff | Target Version | 1.6 => post-1.0 |
| 2025-12-21 20:01 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2026-01-26 07:04 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2026-01-26 07:04 | Christian Grothoff | Status | confirmed => assigned |
| 2026-01-26 07:05 | Christian Grothoff | Status | assigned => confirmed |
| 2026-02-07 13:45 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2026-06-30 13:02 | htgoebel | Note Added: 0029026 |
