Hi @spencer - You’re right, my code is actually retrieving the resource link on the webhook payload to get the correlation ID. The issue is that sometimes the correlation ID isn’t always there. Checking the more recent events, they do seem to have this, so I’m wondering if this was user error of some sort. Thanks for the good info in this discussion.
As I look into this further, the main issue I’m having is determining when the transfer is 100% complete - from customer A bank into customer B bank. This is a bit of a tangent in this discussion, so I can make another thread if necessary…
My understanding was that the customer_transfer_completed event is supposed to represent the funds arriving in the bank account of the destination. I see in the documentation that this is incorrect, since it reads:
“Description: A Customer transfer was successful. Represents a successful funds transfer either to an unverified Customer’s bank or to a verified Customer’s balance.”
Here’s an example event, the ID of this event is
The topic is
I follow the resource link, which leads to the transfer information. It says
status: processed. Currently my webhook endpoint is grabbing the correlation ID from here to mark the transfer as complete in our DB. However, there’s a link called
funded-transfer here, which from this forum I recently learned means the transaction further down the pipeline (side note - is this anywhere in the documentation?). This transfer’s status is
So the transfer is not completed, and must still be in the dwolla balance of the verified customer that’s receiving it.
Checking the dwolla balance, I see that it has a balance of $0.
Where is the money? Am I missing something?
How should my webhook endpoint tell when a transfer is 100% completed, ideally without traversing through a maze of links? What’s best practice here? Is there not a webhook event that represents funds moving the entire journey from bank account A to bank account B?