View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005867 | Taler | wallet (WebExtension) | public | 2019-08-31 14:23 | 2023-09-23 15:09 |
| Reporter | Florian Dold | Assigned To | sebasjm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0005867: interaction between refunds and payment re-play unclear | ||||
| Description | When an article is refunded and the merchant offers to pay for a new instance of it (with a new order ID), the wallet will still try to replay the payment for the refunded payment. This will just lead to the "can't view article, it has been refunded" page of the merchant. The wallet should probably provide some escape hatch and offer the user to make a payment for the new contract in case there is a refund for the matching old payment. All these cases should be written down somewhere, also to make it easier for merchants. | ||||
| Tags | No tags attached. | ||||
|
|
I think that we may want to have 2 kind of order/payment/refund interaction. (a) Fungible asset: like the right to read the article in the demo * Any paid order will work * Having a refunded order is like no having an order at all * If no order or order refunded, show the paywall (b) non-Fungible asset: like buying a drink online * There is 1-to-1 match between an order an a product * The merchant need to see the order to know which product is * If the order is refunded, is ok for the merchant to inform that this product is no longer accessible I think the demo shop example is (a) but behaving like (b) |
|
|
Assigning to Sebastian as he's currently looking over DD7. |
|
|
From the discussion with Christian and Sebastian: This is something we need to address before 1.0, but we need to address this without introducing some completely new feature. Maybe the wallet just needs to disable repurchase detection when there is a refund. |
|
|
c077426..f5da2dc blog, create new order if the order is refunded and the user ask for new_if_refunded 742b00028..d759f0822 wallet, when doing repurchase detection omit purchase with refund |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-08-31 14:23 | Florian Dold | New Issue | |
| 2019-08-31 14:23 | Florian Dold | Status | new => assigned |
| 2019-08-31 14:23 | Florian Dold | Assigned To | => Florian Dold |
| 2023-02-16 22:22 | Florian Dold | Target Version | => 0.9.3 |
| 2023-02-16 22:22 | Florian Dold | Relationship added | parent of 0007475 |
| 2023-02-17 15:09 | sebasjm | Note Added: 0019866 | |
| 2023-04-05 17:35 | Florian Dold | Assigned To | Florian Dold => |
| 2023-04-05 17:35 | Florian Dold | Assigned To | => sebasjm |
| 2023-04-05 17:36 | Florian Dold | Note Added: 0020026 | |
| 2023-04-11 18:04 | Florian Dold | Note Added: 0020072 | |
| 2023-04-13 20:37 | Florian Dold | Category | wallet (WebExtensions) => wallet (WebExtension) |
| 2023-07-10 19:12 | sebasjm | Status | assigned => resolved |
| 2023-07-10 19:12 | sebasjm | Resolution | open => fixed |
| 2023-07-10 19:12 | sebasjm | Note Added: 0020350 | |
| 2023-09-23 15:07 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-09-23 15:09 | Christian Grothoff | Status | resolved => closed |
