Duplicate notification
A duplicate notification is a repeated message about the same payment event: the provider sends the same callback again, or the merchant logs the same response twice. Duplicates are normal in payment traffic. Collapsed into one event they are harmless; counted twice they inflate turnover or trigger a second credit.
How it works
A duplicate notification usually comes from a retry. A provider sends a callback, does not receive the acknowledgement it expects, and sends it again. An illustrative sequence for one synthetic payment:
10:00:01 callback PAY-7A8B Provider E status: success amount: 1500
10:00:31 callback PAY-7A8B Provider E status: success amount: 1500
10:01:31 callback PAY-7A8B Provider E status: success amount: 1500
-> one event: PAY-7A8B success, observed 3 times
The three messages say one thing. They should become one event, with the repeats kept as observations.
Why it matters
Duplicates are not rare noise. On one anonymised merchant day, 401,255 repeated observations were collapsed into the events they described. A platform that credits a player on every success callback, or a report that sums every message, turns each duplicate into money that does not exist.
How to spot it
Count callbacks per payment ID for one provider. More than one success message per payment means retries. Then check that your platform credits once, whatever the number of messages, and that your reports count payments, not messages.
Related terms
Callback · Idempotency key · Merchant log · Normalisation · The normalizer
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated