View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005987||Taler||mechant backend||public||2019-12-06 00:26||2019-12-06 23:19|
|Reporter||Florian Dold||Assigned To||Christian Grothoff|
|Priority||low||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005987: review abort-refund mode of /pay|
|Description||It is currently not clear why the API needs the deposit permissions, when the merchant could just refund all coins deposited so far for this order.|
Maybe this was intended to abort a partial payment on device A and complete it on device B? It is not clear from the documentation whether an "aborted" payment can be continued.
|Tags||No tags attached.|
Looks like the "two devices" scenario is why the API was designed this way.
Leaving this open since the rationale for this needs to be clarified in the documentation, and it needs to be emphasized that an aborted payment can still be completed.
Furthermore, it is not clear how this interacts with the API for the merchant frontend: If I pay something for 10 EUR, but do (1) partial pay (2) abort-refund (3) partial pay (3) abort-refund (4) partial pay, then I have a refund of a bit less than 20 EUR, but actually paid 10 EUR plus fees. How is this information presented to a merchant frontend in the /check-payment API?
|2019-12-06 00:26||Florian Dold||New Issue|
|2019-12-06 00:26||Florian Dold||Status||new => assigned|
|2019-12-06 00:26||Florian Dold||Assigned To||=> Christian Grothoff|
|2019-12-06 00:34||Florian Dold||Note Added: 0015127|
|2019-12-06 00:35||Florian Dold||Note Edited: 0015127||View Revisions|
|2019-12-06 23:19||Christian Grothoff||Priority||normal => low|