Why user does not became a “verified” when he connects his own funding source (e.g his identity can be confirmed by bank)?
Unfortunately verifying a bank account doesn’t satisfy the identity verification requirements we are required to follow.
In order to process a payment between two users (using White Label), we should have two Customers (minimum one of them should be verified), and the sender should have a verified funding source (while receiver is not required to have a verified funding source)?
How can Customer withdraw a money, sent to his “Balance” funding source (while he has not access to Dwolla’s UI)? The only way is to add a new funding source and request an app to start transfer between “balance” and “bank” funding sources?
If you’re using white label, you control the entire experience for the customer via your app. So if you need to move money in/out of a customer’s balance, you would initiate that with the API. You would create a transfer with the customer’s balance as the source and the customer’s bank account as the destination, for instance.
Are there a way to manually set Customer’s status to “document request” or another one, to test an our application flow and scenarios to upload documents for verification? (same for payments processing - how we can test a situation, when payment has been rejected?)
Yes, you can create a customer that will end up in Document or Retry statuses by using the status as the first name of the customer in our sandbox environment. You can simulate failed transfers using our Sandbox Console: https://developers.dwolla.com/resources/sandbox-console.html
What will happen after we (as an app) will send to Dwolla a customer-provided documents to prove his verification? Will Dwolla notify us about customer status change (from “document” to “verified”, for example) ?
Yes, you should get webhooks to notify you of changes. More info is available in our developer documentation: https://developers.dwolla.com/resources/customer-verification.html