I take the ‘a8bd…’ value and store it in the database. We have a webhook set up, which send us a post almost immediately after the request is made. The issue is that the value it’s passing as the id is something different, it’s incremented by 1 ‘a7bd…’ why is that the case?
This may be different legs of the same transaction. Looks like a7bd17c5-6301-ec11-8137-d4c9c28fa0b6 came from Plaid and a8bd17c5-6301-ec11-8137-d4c9c28fa0b6 came from the balance of userid e3c8194a-cc68-4be0-bac9-840765d90357 which came from the Plaid verified account.
I need a means to map the payload arriving in the webhook to an existing transaction…how can I do that if the resourceid is not the primary identifier?
kmoreira
(Kelly M. - Developer Advocate @ Dwolla)
4
You can supply a correlationId. When a webhook is delivered, call off to the API to extract the correlation ID and do a lookup.
Or you can use the funded-transfer and funding-transfer links. If you do a GET to the resource that includes the ID you don’t have, you could map that to the funded-transfer link which should be the one you have stored.
Your code should actually retrieve the resource link on the webhook payload to get the correlation ID.
The Event payload itself won’t include the correlationId field. These payloads were designed to be very lightweight and only include links to relevant resources in the API. The idea being, the event is used as a hint to call off to the API to get more information about the resource that changed state.