Is Dwolla Down Right Now? Check if there is a current outage ongoing.

Our team has processed all pending notifications. The incident is resolved. Thank you for your patience.

A fix has been deployed, and new notifications are being processed normally. Our team is working through a process to send the pending notifications that were generated from approximately 3:20pm through 7pm CT. We will update the incident when that is completed.

We are currently experiencing delays in sending certain operational notifications. This impacts only the email notifications themselves and does not affect the underlying transaction processing or any other parts of the platform. Affected Operational Notification: - MassPay completed emails - Some transfer completion and transfer failed emails Our team is actively investigating the cause, and we will provide further updates as we work to resolve this issue. Thank you for your patience.

This incident has been resolved.

We are currently monitoring an issue in Production affecting several endpoints that power Secure Exchange, Open Banking, and Virtual Account Number (VAN) Creation. These endpoints were returning 500 Server Error responses between 1:02 AM CT and 9:11 AM CT, but are now showing signs of recovery after applying a fix. Affected endpoints include: /exchange-sessions /exchanges /exchange-partners POST /funding-sources (for token exchanges and VANs creation only) Note: Sandbox environments are not impacted, and testing continues to function as expected. We will continue to monitor the fix closely and provide further updates as needed. Thank you for your patience.

The status of all previously affected RTP transfers has been successfully updated to reflect the correct status. Webhooks have also been sent to notify of these status changes. Thank you for your patience and understanding as we worked to resolve this issue.

Our team is now executing the status updates for the affected RTP transfers that remain in a pending state. This process is underway, and we will provide a final update once it is complete.

We are continuing to work on updating the status of the previous RTP transfers that remain in a pending state. These transfers were affected before our recent fix, which has been successfully processing new RTP transfers since deployment. While we don’t have a precise ETA for when these status updates will be fully resolved, this is our top priority, and our team is actively working to correct the status of these affected transfers. Thank you for your continued patience and understanding as we work to fully resolve this issue.

We have implemented a fix for the RTP status issue. All new RTP transfers submitted are processing correctly and are reflecting the appropriate status. We are now working on updating the status of the 508 previously affected RTP transfers that remain in a "pending" state. We will provide further updates as this effort progresses. Thank you for your patience and understanding.

We are currently experiencing an issue affecting Real-Time Payments (RTP) submitted through our API. Since approximately 5:00 AM CT, these payments have been processing as expected — meaning that funds are being successfully transferred to the intended bank accounts. However, their transfer status remains "pending" in our system, creating a discrepancy between the actual fund movement and the reported transaction state. The root cause has been identified, and we are actively implementing a fix to resolve the underlying issue. Note: To avoid unintended duplicate payments, please refrain from resubmitting these transactions, as the transfers are still being processed correctly. We appreciate your patience as we work to restore normal transfer status updates. Further updates will be provided as soon as they are available.

We experienced a temporary outage that impacted the /customers endpoint. Between 4:29:45 AM and 4:34:16 AM CT, the system was returning HTTP 500 errors due to a brief disruption in service. The total duration of the impact was 4 minutes and 29 seconds. The issue has been resolved, and the system has been stable since 4:34:16 AM CT. We apologize for any inconvenience this may have caused.

This incident has been resolved.

Since 103/27/2025 1:27pm CT, we have been experiencing an issue where retrieving customers by ID for Business Verified Customer Records in the Retry, Document, or Suspended statuses is failing. This issue affects both the Dashboard and API in Sandbox and Production environments. Our team is actively working on a fix, and we will provide updates as soon as possible. We appreciate your patience and apologize for any inconvenience.

We have resolved the issue causing elevated API error rates and 500 errors that began at approximately 4:09 PM CT. Some transfer requests during this period resulted in a 500 status code. For clients using idempotency-keys, retrying these requests might initially return a ‘409 Conflict’ error. This is due to Dwolla’s 24-hour idempotency key lock. To ensure your transfers were processed correctly: 1. Check the Dashboard/API: Verify if the affected transfers were successfully created. If they weren’t, proceed to the next step. 2. Retry with a New Idempotency Key: If the original request resulted in a 500 and subsequently a 409, retry the request using a new idempotency key. This is the recommended approach. 3. Retry with Original Idempotency Key (After 24 Hours): Alternatively, you can retry the original request (with the same idempotency key) after the 24-hour lock expires. This will eventually return a ‘201 Created’ response if the transfer was ultimately successful. If you continue to experience issues or have any further questions, please reach out to us at support@dwolla.com. We apologize for the inconvenience.

A fix has been implemented and we are monitoring the results.

Beginning 03/21/2025 04:09 PM CT, we began experiencing an elevated level of API errors on the creation of new Transfers in the Dwolla API. Our engineering team is actively investigating the cause and working towards a resolution. We apologize for the inconvenience and will provide an update shortly.

This incident has been resolved. All transfers statuses have been updated and webhooks are being delivered.

The scheduled 9:00 AM CT Same Day ACH processing completed successfully. While the core ACH processing is functioning, there are still delays in webhook delivery. We will post another update as soon as the issue is resolved.

We have experienced a delay in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. Our support team is working as quickly as possible to recover from this and avoid downstream impacts with the 9:00 AM CT export of Same-day ACH debit and credit transactions. We will provide an update when the process completes, and we apologize for any inconvenience caused by this disruption.

On 2/21/2025, at approximately 5:28 PM CT, we identified an issue affecting RTP transfers, causing them to remain in a pending state longer than expected. The issue was resolved by 6:59 PM CT, and all impacted RTP transfers were successfully processed by 7:40 PM CT.

We have resolved the issue causing elevated API error rates and 500 errors that began at approximately 3 PM CT. Some transfer requests during this period resulted in a 500 status code. For clients using idempotency keys, retrying these requests might initially return a ‘409 Conflict’ error. This is due to Dwolla’s 24-hour idempotency key lock. To ensure your transfers were processed correctly: 1. Check the Dashboard/API: Verify if the affected transfers were successfully created. If they weren’t, proceed to the next step. 2. Retry with a New Idempotency Key: If the original request resulted in a 500 and subsequently a 409, retry the request using a *new* idempotency key. This is the recommended approach. 3. Retry with Original Idempotency Key (After 24 Hours): Alternatively, you can retry the original request (with the same idempotency key) after the 24-hour lock expires. This will eventually return a ‘201 Created’ response if the transfer was ultimately successful. If you continue to experience issues or have any further questions, please reach out to us at support@dwolla.com. We apologize for the inconvenience.

We are currently investigating elevated API error rates resulting in 500 errors. This began at approximately 3 PM CT.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're aware of the issue affecting Funding Sources pages in the Production Dashboard and are actively investigating. We'll provide an update as soon as we have more information.

This incident has been resolved. All transfers statuses have been updated and webhooks have been delivered. Please note: As a result, this impacted the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. We will be sending out communications with additional details to Dwolla customers that have been impacted. We apologize for the inconvenience.

We have experienced a delay in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We will provide an update when the process completes, and we apologize for any inconvenience caused by this disruption.

This incident has been resolved.

RTP transfer functionality has been restored to all Dwolla funding sources.

We are continuing to roll out the fix that will restore RTP functionality for all funding sources created at Dwolla. The rollout is in progress and we will continue to monitor its progress until it completes.

The issue has been identified and a fix is being implemented.

At approximately 8pm Central Time on 12/14/2024, we began experiencing issues processing RTP transfers. RTP Transfer attempts in the API are failing with an HTTP 400 error. This issue only impacts users creating RTP transfers. We are currently actively investigating the issue. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this issue.

This incident has been resolved.

We are observing elevated 500 error rates originating from our Cloudflare edge. We are actively working to identify the root cause of this issue and restore full API availability. A subset of Dwolla API consumers may experience intermittent failures when making requests. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve this issue.

We experienced delays in the morning processing of ACH transactions on the platform. This impacted the webhook delivery and API transfer status updates for ACH credit and debit transactions that were expected to update today. The processing completed at 9:10 AM CT, initiating the delivery of webhooks and transfer status updates. We apologize for any inconvenience caused by this disruption.

This incident has been resolved. All affected Same Day transfers, originally expected to process at 11:30 AM CT, have now been successfully processed as of 5:21 PM CT. Webhook delivery and API transfer status updates are functioning normally again. We apologize for any inconvenience this may have caused and appreciate your patience.

We are experiencing delays processing Same-Day ACH transactions on the platform that exported today at 9:00 AM CT. This impacts the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 11:30 AM CT today. As a result these transfers are now expected be processed at 5:00 PM CT. We apologize for the inconvenience.

We identified irregular API response times and status code 500 responses for a small percentage of API consumers on the platform. After review of data captured at the edge of our platform, intermittent errors began at approximately 7:30pm CT and ended around 10:25PM CT. We are working with our networking provider to understand the root cause and future preventative measures. We apologize for any inconvenience to the small number of consumers impacted. Please don’t hesitate to reach out with any questions or concerns.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We experienced delays processing Same-Day ACH transactions on the platform that were supposed to export at 9:00 AM CT. This impacts the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 11:30 AM CT today. As a result these transfers will now be processed at 5:00 PM CT. We apologize for the inconvenience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate the increase in issues with Dwolla API access token creation and HTTP 500 responses (server error) that began on May 16, 2024, at 10:36 AM CT. Our investigation has led us to believe that the intermittent HTTP 500 errors might be specific to a certain region. We are working closely with our hosting providers to pinpoint the root cause of the issue. We apologize for any inconvenience this may cause and appreciate your patience. We are committed to resolving this issue as quickly as possible. In the meantime, if you are experiencing difficulties calling the API to create a new access token, or any other API endpoints, please try again later. We will provide a further update as soon as we have more information.

Beginning 05/16/2024 10:36am CT, we began experiencing an increase in issues with the creation of access tokens in the Dwolla API and HTTP 500 responses (server error) being returned. We are currently investigating this issue. The following endpoints are affected: /token

This incident has been resolved.

We experienced delays in the morning processing of ACH transactions on the platform. This impacted the webhook delivery and API transfer status updates for ACH credit and debit transactions that were expected to update today. The processing completed at 8:25 AM CT, initiating the delivery of webhooks and transfer status updates. We apologize for any inconvenience caused by this disruption. Our team is actively monitoring the situation to ensure smooth operation moving forward.

Beginning 01/24/2023 11:20 AM CT, we began experiencing an elevated level of API errors on the creation of new Transfers in the Dwolla API. The issue was resolved at around 12:15 PM CT. During this time API calls to create transfers in Production may have returned an HTTP 500 or 503 response.

We are investigating intermittent exceptions (HTTP 500s) creating new transfers via the API. We apologize for the inconvenience and will provide an update shortly.

We experienced delays processing Same-Day ACH transactions on the platform that exported at 9:00 AM CT. This impacted the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 11:30 AM CT today. As a result these transfers will now be processed at 5:00 PM CT. We apologize for the inconvenience.

We experienced delays processing Same-Day ACH transactions on the platform that exported at 9:00 AM CT. This impacts the webhook delivery and API transfer status updates for Same-Day ACH credit and debit transactions that were expected to process at 11:30 AM CT today. As a result these transfers will now be processed at 5:00 PM CT. We apologize for the inconvenience.

This incident has been resolved.

Beginning 09/20/2023 04:00am CT, we began experiencing an increase in issues with the creation of new Mass Payments in the Dwolla API and HTTP 500 responses (server error) being returned. We are currently investigating this issue. The following endpoints are affected: POST /mass-payments

This incident has been resolved.

At approximately 8:48am Central Time on September 11, 2023, we began experiencing issues processing RTP transfers. RTP Transfers created after 8:48am appear as "pending". This issue only impacts users creating RTP transfers. We are currently actively investigating the issue.

This incident has been resolved.

We are continuing to investigate this issue.

We're experiencing an elevated level of API errors and are currently looking into the issue. API calls to Production may intermittently return HTTP 500 responses (server error), and the Production Dashboard may be unavailable.

Beginning 07/18/2023 07:50 AM CT, we began experiencing an elevated level of API errors on the creation of new Transfers in the Dwolla API. The issue was resolved at around 08:03 AM CT. During this time API calls to create transfers in Production returned HTTP 500 responses (server error).

Beginning 07/17/2023 11:03 AM CT, we began experiencing an increase in issues with the creation of new Transfers in the Dwolla API. The issue was resolved at around 11:12 AM CT. During this time API calls to create transfers in Production returned HTTP 500 responses (server error).

We began experiencing degraded performance in Sandbox starting at 12:19 PM CT June 27, 2023. The issue was resolved at around 12:28 PM CT. During this time API calls to Sandbox intermittently returned HTTP 500 responses (server error), and the Sandbox Dashboard would have been unavailable for some periods of time.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We're experiencing an elevated level of API errors and are currently looking into the issue. API calls to Sandbox intermittently returned HTTP 500 responses (server error), and the Sandbox Dashboard is unavailable.

We began experiencing degraded performance in Sandbox starting at 3:25 PM CT June 13, 2023. The issue was resolved at around 3:50 PM CT. During this time API calls to Sandbox intermittently returned HTTP 500 responses (server error); including high response times, webhooks were delayed, and the Sandbox Dashboard would have been unavailable for some periods of time.

This incident has been resolved. Same-day debit and credit transactions that were scheduled to export 9:00 AM CT will export at 1:00 PM CT.

Correction: Webhook delivery and API transfer status updates are not affected. The only impact is on Same-day ACH debit and credit transactions export.

The issue has been identified and a fix is being implemented.

We're currently experiencing delays in the morning export of Same-day ACH debit and credit transactions. We apologize for the inconvenience and we'll provide an update once the process has completed. This impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. We have sent out communications with additional details to Dwolla customers that have been impacted.

Beginning 04/19/2023 02:39 pm CT, we began experiencing an increase in issues with creating and updating Verified Customers in the Dwolla API. The requests returned HTTP 500 responses (server error). We identified and resolved the issue at 3:49 pm CT. The following endpoints were affected: POST /customers POST /customer/{id}

This incident has been resolved. All API transfer statuses are now updated.

A fix has been implemented and we're continue to monitor for further issues. Transfer statuses are in the process of updating and related webhooks are being delivered.

Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. We have sent out communications with additional details to Dwolla customers that have been impacted.

We're currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we'll provide an update shortly once the process has begun.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We've received some reports of issues when retrieving a new application token. We are currently identifying the issue and will keep updated. Currently affected API endpoints: * POST /token

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We’ve received reports of intermittent issues when attempting to login to the Dwolla sandbox interface at https://accounts-sandbox.dwolla.com/login. We’re investigating the issue and will provide an update shortly.

This incident has been resolved. All transfer statuses have updated and related webhooks are being delivered.

Please note: This delay impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at the 1:00 PM CT window.

We’re currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved.

Dwolla was made aware that our banking partner that enables VAN transactions on the platform is experiencing delays in ACH file delivery. This delay impacts availability of funds in balances in the first processing window. As more information is made available to us we will be sure to keep you updated.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We’re currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are experiencing an issue that is causing 500 Internal Server Error with our Sandbox dashboard and some Sandbox API endpoints. We're investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We’ve received reports of timeout issues when attempting to access the Transactions page in the Dwolla Dashboard interface at https://dashboard.dwolla.com. The API is also experiencing issues with retrieving transfers. We’re investigating the issue and will provide an update shortly.

This incident has been resolved. All transfer statuses have updated and related webhooks and emails are being delivered.

This incident has been resolved. All transfer statuses have updated and related webhooks and emails are being delivered.

We’re currently experiencing an issue with internal events that impacts delays in webhook delivery, API status updates, Operational Notifications for a subset of ACH transactions in the morning processing of ACH transactions on the platform. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved.

A fix has been implemented and we're monitoring the results.

The issue has been identified and a fix is being implemented. We observed an increase in errors beginning around 6:20am CDT.

We’ve received reports of issues when attempting to login to the Dwolla Dashboard interface at https://dashboard.dwolla.com. Users are met with a 503 error response. The API is also experiencing issues with retrieving the Funding Source balance. We’re investigating the issue and will provide an update shortly.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We're experiencing an elevated level of API errors and are currently looking into the issue. The issue started at 12:02pm Central Time. API requests to create new resources are returning HTTP status code 500.

This incident has been resolved. All transfer statuses have updated and related webhooks are being delivered.

We’re currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved. All transfer statuses have updated and related webhooks are being delivered. Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. We have sent out communications with additional details to Dwolla customers that have been impacted.

We’re currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved.

At approximately 10:48 am Central Time, we began experiencing issues processing RTP transfers. A subset of RTP Transfers created are immediately being updated with a "failed" status. We are currently actively investigating the issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are investigating an issue that is causing higher than normal response times when retrieving transfers via the API and searching for transactions in the Dashboard. We apologize for the inconvenience and will provide an update shortly.

This incident has been resolved. All transfer statuses have updated and related webhooks are being delivered. Please note: As a result, this impacts the 9:00 AM CT export of Same-day ACH debit and credit transactions. These transactions will now export at 1:00 PM CT. We have sent out communications with additional details to Dwolla customers that have been impacted.

We’re currently experiencing delays in the morning processing of ACH transactions on the platform. This impacts the webhook delivery and API transfer status updates for ACH credit and debit transactions that are expected to update today. We apologize for the inconvenience and we’ll provide an update once all processes have completed.

This incident has been resolved.

Our automated tests detected issues and our team is investigating. The following endpoints are affected: GET /transfers/{id}

This incident has been resolved.

At approximately 2:34pm CDT on May 26, 2022 we identified an issue with an internal service that is tasked with creating and retrieving webhook-subscriptions as well as delivering webhook requests to applications that have an active webhook subscription. We are actively looking into the issue. The following endpoints are affected: POST /webhook-subscriptions GET /webhook-subscriptions