Dwolla Plaid integration

General
1

Hi

I would like to know which solution is recomanded by Dwolla for plaid and Dwolla integration with respect to funding source creation ?

  1. As per plaid we can directly call funding source API with palid-processor token
    https://api-sandbox.dwolla.com/customers/AB443D36-3757-44C1-A1B4-29727FB3111C/funding-sources
  2. As per Dwolla documentation we need to do few sub-steps before creating funding source with exchange API
2

Hi @sudhir1,

Dwolla recommends using #2 — Secure Exchange solution with Plaid. We plan to eventually move away from the tokenized solution to either Secure Exchange or Open Banking for bank verification.

Let us know if you have any questions about #2!

3

Thank you for your response.

Could you clarify which account types are supported by Dwolla when creating a funding source?

The Dwolla documentation mentions checking, savings, general-ledger, and loan as accepted value,
but your integration example only includes savings and checking

4

Hi @sudhir1,

Sure thing! Bank account types of general-ledger and loan are only supported when added using the bank account’s Account and Routing numbers via the Dwolla API using this request.

For all other Secure Exchange and Open Banking bank addition processes, only checking and savings are supported.

Thanks for asking! Hope this helps clarify things. I will also make a note on our end to clarify this in the docs!

5

Could you also help me with dwolla webhooks.
It looks confusing to subscribe each request for payment or am I getting it wrong ?
How to setup webhooks so we could get to know if payments are completed ?

Thanks

6

We tried to set up a webhook in our sandbox, but we couldn’t figure out which method to use for sending the request to Dwolla or the appropriate URL to acknowledge that our app has received the webhook.
Your documentation suggests using an SQS queue, but it doesn’t provide any sandbox URL for sending these webhook responses/requests for acck.

7

Hi @sudhir1,

Just to clarify, when you set up a webhook subscription with Dwolla, you’re subscribing to all events, not specific ones. The webhook URL you provide should be publicly accessible, and that’s where Dwolla will send notifications for any activity in your account.

Here’s a quick overview:

  1. Create a Webhook Subscription: Use the Dwolla API to create a subscription by sending a POST request with your webhook server URL. This is where Dwolla will send events, including payment completions.

  2. Webhook Listener: Set up a listener on your server to handle incoming webhook requests. Your server must respond with a 2XX status code within 10 seconds to acknowledge receipt.

  3. Testing in Sandbox: There’s no special URL for the sandbox; you can use the same approach for testing. Just make sure your server is publicly accessible and can receive POST requests.

  4. Using AWS SQS Queue (Optional)
    As you mentioned, our documentation suggests using AWS SQS for webhook handling. This is optional, but it can be useful for handling high volumes of webhooks or ensuring message reliability. If you set up an SQS queue, you’ll need to configure your server to pull messages from the queue and process them.

    However, for testing purposes in the sandbox, you can simply send the webhook events directly to your server’s URL without the need for an SQS queue. You can integrate SQS in production later if your app needs more robust message handling.

Let me know if you need any further clarification!

8

This topic was automatically closed after 365 days. New replies are no longer allowed.