View Issue Details

IDProjectCategoryView StatusLast Update
0010737Talermerchant backendpublic2025-12-21 20:46
Reportersebasjm 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
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0 
Target Version1.3Fixed in Version1.3 
Summary0010737: 451 of template creation dont returns a PaymentDeniedLegallyResponse without urls
Description
spec
https://docs.taler.net/core/api-merchant.html#tsref-type-PaymentDeniedLegallyResponse
https://docs.taler.net/core/api-merchant.html#post-[-instances-$INSTANCES]-templates-$TEMPLATE_ID

$ curl 'http://merchant.taler.test/instances/qwe/templates/qwe' --data-raw '{}' --insecure -v
> POST /instances/qwe/templates/qwe HTTP/1.1

< HTTP/1.1 451 Unavailable For Legal Reasons
{
  "code": 2513,
  "hint": "The total order amount exceeds hard legal transaction limits from the available exchanges, thus a customer could never legally make this payment. You may try to increase your limits by passing legitimization checks with exchange operators. You could also inquire with your legislator why the limits are prohibitively low for your business."
}
Steps To Reproducefollow instructions on 0010733
Additional Informationi will be making this optional on the client side, i think it doesn't have consequences yet, so it's not blocker
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0010635 closedChristian Grothoff wrong response doesn't follow spec [3d] 
related to 0010733 closedsebasjm 451 response not handled by spa for template instantiation 

Activities

Christian Grothoff

2025-12-21 19:00

manager   ~0027161

112a2c62..e25c28c2 fixes the specification. The implementation remains unchanged, the spec wrongfully re-used a response from /pay while the order creation doesn't (need to) return a list of exchanges. We may return more extensive actual diagnostics in the future, but that is another issue and won't follow this format.

Issue History

Date ModifiedUsernameFieldChange
2025-12-05 14:10sebasjmNew Issue
2025-12-05 14:10sebasjmStatusnew => assigned
2025-12-05 14:10sebasjmAssigned To => Christian Grothoff
2025-12-05 14:10sebasjmRelationship addedrelated to 0010733
2025-12-19 19:06Christian GrothoffRelationship addedrelated to 0010635
2025-12-21 19:00Christian GrothoffStatusassigned => informing
2025-12-21 19:00Christian GrothoffResolutionopen => fixed
2025-12-21 19:00Christian GrothoffFixed in Version => 1.3
2025-12-21 19:00Christian GrothoffNote Added: 0027161
2025-12-21 19:00Christian GrothoffProduct Version => 1.0
2025-12-21 19:00Christian GrothoffTarget Version1.5 => 1.3
2025-12-21 20:46Christian GrothoffStatusinforming => closed