Frequently Asked Questions #

When creating a funding source, a Plaid processor_token value is passed in using the plaidToken key. With this information, Dwolla executes a call to Plaid's API to securely retrieve the account and routing number and creates a funding source on your behalf. Upon success, Dwolla returns a URL that represents the new funding source via the Location response header.

Yes, if the end user has 2FA enabled with their bank, Plaid will attempt to mimic their bank's login flow, meaning that the user should receive a 2FA code, and is subsequently prompted to enter it in on the next screen.

If the processor_token has already been used to create a funding source, then the token changing or expiring will not affect it; Dwolla only uses the processor_token to fetch the account and routing number from Plaid and then immediately discards it.

However, if you have not yet used the processor_token to create a funding source, then you will need to follow Plaid's process for creating a new token before sending it over to Dwolla.

Yes, it is possible to use Plaid Link to both automatically verify bank accounts and manually verify via micro-deposits if the bank is not supported or an error occurs during automatic verification.

No. Since Dwolla only uses Plaid to securely retrieve the account and routing number, any changes to the underlying Plaid account will not affect the funding source(s) that have already been created in Dwolla.