Discussions

Hi everyone,

I'm currently integrating PayMongo into our backend system (built on Node.js), and I had a question about how webhook retries are handled—specifically in terms of idempotency.

From what I understand, PayMongo sends webhooks multiple times until it receives a 2xx response. My concern is around ensuring that duplicate webhooks (e.g., multiple payment.paid events) don't result in multiple updates in our system, such as double order fulfillment or duplicated logs.

Does PayMongo include any sort of unique event ID or signature in each webhook payload that we can safely use for idempotency checks on our end? And if so, what's the best practice to implement this?

Would appreciate any advice or real-world solutions anyone here has used in production. Thanks in advance!

—Alex geometry dash lite