0004102: re-submitting payment request gives a database error

ID	Project	Category	View Status	Date Submitted	Last Update
0004102	Taler	merchant backend	public	2015-12-23 21:10	2016-09-26 12:01

Reporter	Florian Dold	Assigned To	Marcello Stanisci	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Target Version	0.0	Fixed in Version	0.0

Summary	0004102: re-submitting payment request gives a database error
Description	Submitting the backend/pay request twice with the same data yields a database error. Instead, then backend should check if a contract with the same hash already exists in the database, and then check if the request data matches and return the appropriate response.
Tags	No tags attached.

Date Modified	Username	Field	Change
2015-12-23 21:10	Florian Dold	New Issue
2015-12-23 21:10	Florian Dold	Status	new => assigned
2015-12-23 21:10	Florian Dold	Assigned To	=> Marcello Stanisci
2015-12-24 16:12	Marcello Stanisci	Note Added: 0010029
2015-12-24 16:12	Marcello Stanisci	Status	assigned => informing
2015-12-24 16:12	Marcello Stanisci	Resolution	open => fixed
2015-12-25 09:48	Christian Grothoff	Status	informing => closed
2016-09-26 12:00	Christian Grothoff	Fixed in Version	=> 0.0
2016-09-26 12:01	Christian Grothoff	Target Version	=> 0.0
2025-03-22 13:09	Christian Grothoff	Category	mechant backend => merchant backend

Marcello Stanisci 2015-12-24 16:12 reporter ~0010029	the merchant had transaction_id set as primary key in the 'payments' table, so not only attempting the same payment twice caused error, but also paying with more than one coin. A check on the transaction_id is done as soon as /pay gets handled.