Hey @alex4Zero, You mention resources/tools only available for white label integrations so I am assuming you're wanting to leverage white label Customers vs. Dwolla accounts on your platform.
Correct. A Dwolla user account creates and manages white label Customers via a user account OAuth access_token that contains the ManageCustomers scope.
Yes. We provide a list of CSS classes that can be customized when using IAV within dwolla.js. A list of these classes are shown on this page, and a demo of what these may look like within your app can be found here.
Correct. At least one party in a transaction must be CIP verified requiring additional identity vetting (ssn, dob, address, etc.) You can choose to make all of your users verified Customers within Dwolla or only have one party in the transaction be a verified Customer and the other create an unverified Customer. Customer types are briefly described in our docs here or in our resource article here.
Assuming Alice created her Customer account as "unverified" then these account types do not have a 'balance' funding source where funds can land when someone sends them money. In this case, money would be sent to the bank account that Alice has attached to her Customer account within Dwolla. If you're having all of your users create verified Customers then Alice would need to complete the additional identity verification when setting up her account.
Yes. If Alice is a verified Customer then she can manually trigger to move her funds from her balance to an attached bank. You'll call our transfers API to move the money.
Hope this helps! Let me know if I can clarify any of the above responses.