View Issue Details

IDProjectCategoryView StatusLast Update
0006600Talermerchant backendpublic2021-08-24 14:23
ReporterMS Assigned ToChristian Grothoff Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.8Fixed in Version0.8 
Summary0006600: Refund should not be offered when the frontend did not give a delay.
DescriptionIf the merchant frontend does not give a "refund_delay" value upon creating a order, then no refund option should be offered for the item.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2020-09-10 18:02

manager   ~0016962

Last edited: 2020-09-10 18:02

Eh, offered by whom? Oh, and to clarify: it's OK if the /refund API is used in this case, it's just not _guaranteed_ that any refund will be possible because the exchange may then wire the funds virtually immediately to the merchant. So I'm not sure what change you expect is needed to the merchant here. Maybe the spec is still unclear? ;-)

Florian Dold

2020-09-11 11:16

manager   ~0016963

After clarifying this with Marcello: The merchant backend currently allows requests to /{orders}/refund even if giving a refund for this order doesn't make much sense, because the refund deadline is set to "0".

Basically Marcello suggests to add a "sanity check" in the merchant that gives some error when the storefront tries POST /{orders}/refund for an order where we already know giving a refund doesn't make much sense.

(Sure, it's possible that the exchange didn't wire the money yet ... but such a check by the backend might make sense to prevent the common error of forgetting to set the refund deadline. The current behavior just hides it between non-deterministic behavior.)

Christian Grothoff

2020-10-07 10:45

manager   ~0017000

Documented new 403 status code in 0212cfe..d356cbb

Christian Grothoff

2020-10-07 10:47

manager   ~0017001

Implemented in e2406406..7d81706c

Issue History

Date ModifiedUsernameFieldChange
2020-09-10 17:52MSNew Issue
2020-09-10 17:52MSStatusnew => assigned
2020-09-10 17:52MSAssigned To => MS
2020-09-10 18:02Christian GrothoffNote Added: 0016962
2020-09-10 18:02Christian GrothoffNote Edited: 0016962
2020-09-11 11:16Florian DoldNote Added: 0016963
2020-09-11 20:54Christian GrothoffAssigned ToMS => Christian Grothoff
2020-10-07 10:45Christian GrothoffNote Added: 0017000
2020-10-07 10:47Christian GrothoffNote Added: 0017001
2020-10-07 10:47Christian GrothoffStatusassigned => informing
2020-10-07 10:47Christian GrothoffResolutionopen => fixed
2020-10-07 10:47Christian GrothoffFixed in Version => 0.8
2020-10-07 10:47Christian GrothoffProduct Version => git (master)
2020-10-07 10:47Christian GrothoffTarget Version => 0.8
2021-08-24 14:23Christian GrothoffStatusinforming => closed
2025-03-22 13:09Christian GrothoffCategorymechant backend => merchant backend