Bug #148
closed
Backend API|UAT| Getting multiple entries for a single transaction
Added by Vaishali Tomar 19 days ago.
Updated 17 days ago.
Description
Getting multiple entries for a single transaction
Merchant ID - 8523054217
Serial Number- 26220N7M3838,26220N7M3833
Device ID-10500052, 10500039
Terminal Number- 10400023, 10400014
VPA- CV130009017
Do transaction for single VPA which is attached with 2 device and two terminal has creating 4 entries at a single time with same order ID
Files
- Assignee changed from Ayush Tyagi to Kunal Chaudhary
- Status changed from New to Resolved
- Assignee changed from Kunal Chaudhary to Vaishali Tomar
join query issue fix in transaction report API
transaction api report RCA :
The issue occurred due to multiple notification message records
existing for the same transaction in UAT, combined with multiple
active terminal mappings for the same VPA.
During execution, the stored procedure joined both terminal and
notification tables without restricting duplicate notification entries,
which resulted in row multiplication (2 terminals × 2 notifications = 4 rows)
Issue has been fixed in latest Release, but it is related to VPA confirmation that VPA has to be unique for every device so as of now when single VPA is connected with two device it will create two entries only but in original data user can use single VPA for diff devices. 
closing this issue on the behalf of this status
Also available in: Atom
PDF