Webhooks on sandbox coming twice

Could you suggest please. We have subscription on sandbox and webhooks like customer_transfer_created, customer_transfer_completed etc coming to our endpoint twice, which leads to sending notifications twice. Is that bug or feature of sandbox? And how we can avoid it?

Best regards, Yuriy

Hi @Yuriy_Dovhopol , Do those webhook events have a different Event Ids or are they the same? One thing to note is that Dwolla will send Events for both Customers involved in a transaction. So if Customer A is sending funds to Customer B then you’ll receive the customer_transfer_* events for both end-users.

Ids of events are different. But resourceId are the same so then we process it it points to one transfer and our logic is done so we send notifications for first events and for second. Probably we need refer to customer link to differ them.
Best regards Yuriy

1 Like

Ah, yes! Referring to the Customer link/ID will help differentiate those events.

Hi I noticed strange situation which is the same webhooks are coming twice
Content = {“id”:“9dad1e09-8d9d-44f7-8f1d-1fa96312bf1d”,“resourceId”:“ea0a7a2f-15ee-eb11-8136-b0300d0c7e2a”,“topic”:“customer_transfer_completed”,“timestamp”:“2021-07-26T13:27:58.835Z” at Jul 27, 2021 @ 04:40:32.
Content = {“id”:“9dad1e09-8d9d-44f7-8f1d-1fa96312bf1d”,“resourceId”:“ea0a7a2f-15ee-eb11-8136-b0300d0c7e2a”,“topic”:“customer_transfer_completed”,“timestamp”:“2021-07-26T13:27:58.835Z” came at Jul 26, 2021 @ 22:36:04.137
It is on sandbox.
Could you suggest why it could happened
Best regards Yuriy

Hi @Yuriy_Dovhopol

Sometimes multiple webhooks may be triggered for the same event. To avoid this, we recommend checking the idempotence in each webhook before doing any business logic. To find more information about handling duplicate webhooks, please check out our Developer Guide on Webhooks