@Michal_K, There are two sides to every bank-to-bank transaction (ACH debit and credit). Im assuming that this event is being triggered when the source ACH debit is marked as processed in Dwolla? If so, that should kick off a secondary transaction to withdraw funds from the recipient’s balance (held in Dwolla) to their bank account. The customer_bank_transfer_created event should be followed by a customer_bank_transfer_completed event wherein that completion should be an indication that funds are in the receiving bank account.
What I would likely recommend is utilizing the funded-transfer and/or funding-transfer links returned on a Transfer resource to indicate what action your app needs to take, and to identify if the funds have reached their destination. Described in this forum thread. You could then do the following:
- Store the transfer ID returned from the API when creating the transfer as well as a status (your own payment status).
- When a transfer related event is triggered, follow the resource URL to do a GET /transfers/{id} to retrieve the status as well as determine if the transfer has created a a subsequent transfer (as indicated by the presence of the
funded-transferlink). Iffunded-transferlink exists, follow that URL by making a GET /transfers/{id}. If there is nofunded-transferlink and the status isprocessedthen the lifecycle of the transaction is complete.
You should be able to test this for use case by setting the receiving Verified Customer’s attached funding source name to R03. Once that’s done, initiate a transfer and click the “Process bank transfers” button multiple times in the Sandbox Dashboard.