Checklist: Validate a server-to-server postback before trusting it

Checklist: Validate a server-to-server postback before trusting it
A postback that 'works' in a test can still attribute wrong in production. Verify each field.

☐ Click ID parameter name matches what you pass and what the advertiser returns
☐ Payout value arrives in the postback (don't hardcode amounts)
☐ Currency field present if you run multi-currency offers
☐ Status field distinguishes approved / pending / rejected
☐ Postback fires from the advertiser's server IP, not the user's browser
☐ Duplicate postbacks for one click ID are deduped on your side
☐ A rejected/charged-back postback reverses the conversion, not just adds
☐ Timestamp present so you can measure attribution lag

If payout is hardcoded, a payout change silently breaks your reporting.

Validate postbacks for every new advertiser integration and re-test after any tracker update.