# Looking for resources on testing transfer failures

**URL:** <https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019>\
**Category:** General\
**Created:** [June 13, 2023, 9:35pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019 "2023-06-13T21:35:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![davidsonsns](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/davidsonsns/32/3449_2.png) [@davidsonsns](https://discuss.dwolla.com/u/davidsonsns)\
**Post date:** [June 13, 2023, 9:35pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019/1 "2023-06-13T21:35:05Z")

</div>

I’d like to double-check if the [girst](https://gist.github.com/spencerhunter/2ab064e8e76a049eb22e17ed8e92f350) listed on the answer below is still a valid resource? If not, is there any official reference to _ **find out all possible scenarios that a transfer may encounter and the webhooks triggered in each scenario** _?

> [@Testing transfer failures](https://discuss.dwolla.com/t/testing-transfer-failures/7832/2):
>
> Hi @andrew-willow! It appears that this is a transfer to a Verified Customer type. In that case, this is expected behavior – the second leg of the transaction fails due to an R03 return from the bank, however, the funds were still successfully transferred to the recipient’s Dwolla Balance funding-source, which is why it is processed. If you retrieve the funded-transfer link from the links in the resource, it will take you to the final leg of the transfer which is failed. You can check out thi…

---

<div class="post-metadata">

**Author:** ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)\
**Post date:** [June 14, 2023, 2:19pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019/2 "2023-06-14T14:19:26Z")

</div>

Hi @davidsonsns – that gist is still a valid resource!

As an alternative, we have another resource, [Transfer Lifecycle interactive component](https://developers.dwolla.com/concepts/transfer-lifecycle#interactive-transfer-lifecycle), in the docs that lets you simulate a transfer and retrieve all webhooks possible in that scenario, however, it doesn’t have all the failure cases yet.

---

<div class="post-metadata">

**Author:** ![davidsonsns](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/davidsonsns/32/3449_2.png) [@davidsonsns](https://discuss.dwolla.com/u/davidsonsns)\
**Post date:** [June 14, 2023, 6:05pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019/3 "2023-06-14T18:05:45Z")

</div>

Hey @shreya - thanks for answering so fast

Regarding the link you shared, I’m not sure if I’m missing something, but I haven’t been able to reproduce any failure case. Perhaps the combinations I’ve tried aren’t covering this yet. Just flagging it.

---

<div class="post-metadata">

**Author:** ![shreya](https://sea2.discourse-cdn.com/dwolla/user_avatar/discuss.dwolla.com/shreya/32/2154_2.png) [@shreya](https://discuss.dwolla.com/u/shreya)\
**Post date:** [June 20, 2023, 9:34pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019/4 "2023-06-20T21:34:42Z")

</div>

Hi @davidsonsns – apologies for the confusion; we don’t currently have the failure cases in the interactive lifecycle component. We have them covered in the [gist](https://gist.github.com/spencerhunter/2ab064e8e76a049eb22e17ed8e92f350#file-transferandevents-md) though!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/dwolla/original/2X/1/1b70808226fb9abeaaf7386224caffb453efb690.png) [@system](https://discuss.dwolla.com/u/system)\
**Post date:** [June 12, 2024, 9:35pm UTC](https://discuss.dwolla.com/t/looking-for-resources-on-testing-transfer-failures/9019/5 "2024-06-12T21:35:55Z")

</div>

This topic was automatically closed after 365 days. New replies are no longer allowed.
