• Getting Started
    Testing in the Sandbox
    Generate an OAuth Access Token
    Send Money to Users
    Receive Money from Users
    Transfer Money Between Users
    Transfer Money Me-to-Me
    Building With Drop-in Components
  • Customers
    Create a Business Verified Customer
    Create a Personal Verified Customer
  • Funding Sources
    Add a Debit Card Using Dwolla-cards.js
    Add a Bank Using Dwolla.js
    Add a Bank Using Dwolla.js + IAV
    Verify Bank with Micro-deposits
    Add Bank via Dwolla + Plaid Integration
  • Webhooks

Frequently Asked Questions #

  • Event — An event is a unique resource that gets created whenever an action occurs in Dwolla that changes the state of an API resource like a Customer being created or a funding source being verified.
  • Webhook Subscription — A webhook subscription is a resource in the API that you can create in order to subscribe to Dwolla webhooks.
  • Webhook — A webhook is an HTTP request that Dwolla sends to your subscribed URL to notify your app of an event. In order to get webhook notifications, you will need to have an active webhook subscription.

While a webhook subscription is not required for you to integrate with the API, Dwolla requires all applications to have one in production for automated notifications of events to your application. Webhooks provide automatic near real-time status updates to your application versus polling the API which causes unnecessary load on your application and the API.

Dwolla includes a X-Request-Signature-SHA-256 header on each webhook request which is a SHA-256 HMAC hash of the request body with the key being the webhook secret you passed in when you created the webhook subscription. As a best practice, we recommend validating webhooks by generating the same SHA-256 HMAC hash and comparing it to the signature sent with the payload.

We do not recommend nor support relying on IP whitelisting as a method of validating webhooks. Dwolla's IPs are dynamically allocated with no defined range and are subject to change. Refer to the Processing/Validating section for a more detailed guide.

Dwolla sends webhooks for all events that occur in your platform and there isn’t a way to filter what events you subscribe to.

Dwolla automatically pauses a webhook subscription after 400 consecutive failed delivery attempts and sends an email to notify the Admin of the Dwolla account. While it's paused, Dwolla isn’t able to send webhooks for new events to your URL. To resume webhooks, you need to address the issue that’s causing failures, unpause the subscription and retry missed webhooks.

Yes. You can create up to 5 webhook subscriptions in Production and 10 in Sandbox. While only one subscription is needed to be notified of all events, you can have multiple in case one or more of your URLs becomes unreachable.

Test in the Sandbox for free today.

Use sandbox environment to test API requests.

Get API Keys
2022 All Rights Reserved
Financial institutions play an important role in our network.

All funds transfers made using the Dwolla Platform are performed by a financial institution partner, and any funds held in a Dwolla Balance are held by a financial institution partner. Learn more about our financial institution partners.