Issue consuming customer verification document needed webhook

Hello Team,

When we receive customer_verification_document_needed webhook, to identify whether we need to upload a company document or a controller document, the following logic is in place:

  1. If customer details links contain verify-controller-and-business-with-document or verify-controller-and-business-with-document , upload controller document.
  2. If customer details links contain verify-controller-and-business-with-document or verify-business-with-document, upload company document

But in a recent event where both company and controller documents were not uploaded, the customer details link only consisted of verify-business-with-document, thus only the company document got uploaded and our customer went to document status for missing controller document.

Can you please let us know if our logic for checking which document to upload is valid?

Hi @Rabin_Dangol , Your logic for how you should handle this flow looks accurate! It also matches what we have outlined in our documentation. Do you have a recent example where there was a discrepancy between the link that was returned and the user behavior?

Hi Spencer,

Our user flow has not changed, and the onboarding process is also the same. But for this particular instance, we did not receive verify-controller-and-business-with-document or verify-controller-and-business-with-document links in the user detail query. Because of this, the controller document was not uploaded which resulted in rejection of the submission.

The dwolla customer_id is “274e4ed2-4041-48a0-91c8-3a38dab76ae3” and webhook request_id was “b6669fa6-95eb-42d4-8503-4d6238087884”.

Thank you

Hi @Rabin_Dangol – I see that we’ve only ever sent a verify-business-with-document link with the Customer resource indicating that only a Business Doc needs to be uploaded. The Controller seems to have been verified automatically upon creation.

I do see that the user has uploaded a business doc as of this morning (5/21/2024 9:27:57 AM). It’s on our Compliance team document review queue and should be reviewed soon!

Let us know if you’d like any further clarification!