QUOTE(Haloperidol @ Jan 19 2021, 01:29 PM)
Quite unlikely.
PAS record the transaction with their own transaction ID instead of using biller's ID as reference.
This is the receipt i make today.
I am the only one who operate the PAM at that moment, but i noticed the transaction ID had +1 instead of being cumulative (85,86 but mine is 85,87) - assumption of there is someone in Malaysia performed another transaction while i am processing my 2nd payment.
So i think it will be hard to be detect as duplicate.

did 2x just before you, around 11:30
the ref number should be running number for ALL transactions performed. date, time, machine id, branch id, ewallet name are identifiers to give detailed descriptions of the ref number for further analysis (reporting, recon, troubleshoot, support)
my guess is, backend would have already captured the ewallet ID/ewallet ref number (barcode/qrcode string) to recon back with ewallet providers.