View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010576 | Taler | documentation | public | 2025-11-10 22:45 | 2025-11-11 12:45 |
| Reporter | htgoebel | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | tweak | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010576: Please clarify "approvement" | ||||
| Description | The docs for RefundDetails.timestamp use the term "When was the refund approved." For my understanding "approve" means: first the refund gets filed/drafted, then one (maybe the same person) confirms/approves the refund. Anyhow, I'm not aware of any such two-step process/behavior in the merchant backend. Please clarify what is meant here. | ||||
| Tags | No tags attached. | ||||
|
|
CheckPaymentPaidResponse.pending also uses the term "approved". |
|
|
Well, as you said, it's a one-step process, we don't do "file + approve", just one step with the POST to /private/orders/$ID/refund. That's the approval of a refund, and so obviously this timestamp refers to it. |
|
|
Clarified in the documentation. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-10 22:45 | htgoebel | New Issue | |
| 2025-11-10 23:05 | htgoebel | Note Added: 0026369 | |
| 2025-11-11 12:43 | Christian Grothoff | Note Added: 0026374 | |
| 2025-11-11 12:45 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-11-11 12:45 | Christian Grothoff | Status | new => resolved |
| 2025-11-11 12:45 | Christian Grothoff | Resolution | open => fixed |
| 2025-11-11 12:45 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-11 12:45 | Christian Grothoff | Note Added: 0026375 | |
| 2025-11-11 12:45 | Christian Grothoff | Product Version | => 1.0 |
| 2025-11-11 12:45 | Christian Grothoff | Target Version | => 1.2 |
