In our application sender is always unverified customer and receiver is a verified customer all the times. I understood from the documentation that a verified customer may go into suspended state due to many reasons R01, R02 etc. I added a bank account at verified customer end as well as unverified customer end too.
When I made fund transfer from unverified customer fund source to verified customer fund source, I did not receive any web-hook notification for customer suspended. can you help me how can I simulate it?
We don’t have a transfer simulation option that will automatically suspend a customer. We only have one that will remove the funding-source, which is R03.
To test the customer falling into a suspended status, you can suspend then using an API call, or you can also create a Customer in that status by supplying the value "suspended" in the firstName or businessName field if it’s a business Verified Customer. Testing Different API Customer Types | Dwolla API Documentation
Thanks for the quick response shreya, I am referring about the below message.
customer_suspended Description: A Customer was suspended. Timing: Occurs when Dwolla systematically places a Customer in suspended status as a result of uploading fraudulent document, or upon receiving certain ACH return codes when a transfer fails.
How can we reproduce this to put the customer in suspended status?
Ah, we don’t have a way to simulate this in Sandbox. You could maybe have an automatic response in your inetgration (only in Sandbox) that will suspend the Customer (using one of the methods I mentioned above) when there is a trigger, like a particular transfer amount?
Basically we wants to display the reason to our customers why their Dwolla account status is in suspended status, is it because of R01, R02 or any other reason. Do we get this reason as response in the web-hook event (suspended trigger/ event) to our web-hook endpoint so that we can store at our database and display to our customers?
The reason for suspension isn’t included in the webhook event. It would either have to be inferred from their failed transaction or you could reach out to Dwolla for confirmation on why the customer was suspended and what other actions can be taken to unsuspend them.
I am trying to simulate customer suspended scenario to store the reason for customer suspension, so that we can display that to end user .
Scenario I tried is below.
Created an unverified customer and added a fund source with Dwolla+ Plaid for this customer
Created a personal verified customer with a fund source with name on account as R01.
Initiated a bank transfer from Unverified customer to verified customer, it is successful nothing returned by dwolla as its in sandbox may be,
When I clicked on process transfers button in sandbox account, I did not receive any webhook mentioning the verified customer account is suspended nor reason as well . how can we handle this scenario?
Can you check this query and respond. We have not received any webhook with regards to that failure transaction as well as the receiving end customer status changed to suspeneded. We are unable to handle these scenarios at present.
Hi @Sandeep_Challa1 – are you able to share the transfer ID? I can check our logs to see the transfer didn’t fail.
As for suspending the Customer due to a transfer failure, there isn’t a test scenario for this. You can programmatically suspend the Customer upon transfer failure webhook though!
Hi @Sandeep_Challa1, I’m seeing that the transfer did fail. Here’s the webhook Id for the customer_transfer_failed event - 2e4d8395-a937-4007-8da0-0b8bcc6b31a4
You can retrieve the webhook using that ID and view details about the webhook request attempt(s). You can also retry the webhook so you get the request to your server again.
Thanks for the response shreya, we are storing all the webhook event ids in our database so that we will not handle them twice if wehbook is duplicated, but I cant find this id in our database, meaning we have not received this webhook. Can you check it from your end, did dwolla sent that webhook to our end point and whats the status of that?
Other question I have is, during initial days of our sandbox account we used to receive webhooks immediately, but in the recent past we are noticing the webhooks are with significant delay. is there any reason for that?
The delay in webhooks might coincide with elevated activity in the Sandbox environment at a given point. If you notice any significant delays, do let us know!