View Issue Details

IDProjectCategoryView StatusLast Update
0004502Talermerchant backendpublic2016-10-11 15:28
ReporterMarcello Stanisci 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
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Product Version0.0 
Target Version0.1Fixed in Version0.1 
Summary0004502: tracking wire transfers
Descriptionthe backend will use the exchange's API aimed to associate wire transfers with deposit of coins
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Relationships

related to 0004160 closedChristian Grothoff it should be possible to query the payment status of a contract by transaction id 

Activities

Marcello Stanisci

2016-05-18 09:06

reporter   ~0010685

starting with testcase of it

Marcello Stanisci

2016-05-30 12:25

reporter   ~0010778

/track/deposit skeleton added to backend, and testcase correctly calling it.
todo: add /track/deposit logic and /track/wtid function to backend

Christian Grothoff

2016-06-09 14:05

manager   ~0010881

/track/deposit is now called in the testcase, but we need to
1) check the signature in the backendlib
2) revise the API to see what information to pass back to applications
3) extend the testcase to check that information
4) reconsider passing the /track/deposit stuff as part of the URI in the backend
5) figure out how the merchant is supposed to learn the exchange URI.

Christian Grothoff

2016-06-10 00:42

manager   ~0010886

Rudimentary testcase for /track/transfer (renamed!) passes as of 18d70cf..eeb8703

Still has a few FIXME/TODOs in the implementation, this only tests the main 200-logic.

As for note 10881:
(1) makes no sense, we trust our backend (after all, we are offloading the crypto there!)

(2) may need to be looked at again for distinguishing error codes from backend vs. error codes from exchange.

(3) is done, but errors are not covered;

(4/5) are done, but we may want to escape the exchange URI we were given

Christian Grothoff

2016-06-11 18:09

manager   ~0010893

(2/3) now better with respect to error codes.

Might still want to pass execution date of wire transfer if available.

Christian Grothoff

2016-06-11 18:26

manager   ~0010894

Should be fine now.

Issue History

Date ModifiedUsernameFieldChange
2016-05-18 09:05Marcello StanisciNew Issue
2016-05-18 09:05Marcello StanisciStatusnew => assigned
2016-05-18 09:05Marcello StanisciAssigned To => Marcello Stanisci
2016-05-18 09:06Marcello StanisciNote Added: 0010685
2016-05-18 16:01Christian GrothoffSeverityminor => feature
2016-05-18 16:01Christian GrothoffProduct Version => 0.0
2016-05-18 16:01Christian GrothoffTarget Version => 0.1
2016-05-30 12:25Marcello StanisciNote Added: 0010778
2016-05-31 07:53Christian GrothoffAssigned ToMarcello Stanisci => Christian Grothoff
2016-05-31 17:10Christian GrothoffRelationship addedrelated to 0004160
2016-06-09 14:05Christian GrothoffNote Added: 0010881
2016-06-10 00:42Christian GrothoffNote Added: 0010886
2016-06-11 18:09Christian GrothoffNote Added: 0010893
2016-06-11 18:26Christian GrothoffNote Added: 0010894
2016-06-11 18:26Christian GrothoffStatusassigned => informing
2016-06-11 18:26Christian GrothoffFixed in Version => 0.1
2016-06-11 18:26Christian GrothoffResolutionopen => fixed
2016-10-11 15:28Christian GrothoffStatusinforming => closed
2025-03-22 13:09Christian GrothoffCategorymechant backend => merchant backend