View the December 7th changes FAQ for Personal Accounts.
What was announced on November 11, 2016? What’s the timeline?
On November 11, 2016, Dwolla announced changes to some of the account functionality and services made available through its web and mobile applications. On December 7, 2016, the following capabilities were impacted:
2. The Dwolla mobile app will be removed from its respective app stores in favor of our mobile web-browser version, mobile.Dwolla.com.
3. Registering for a Personal account on Dwolla.com/register has been removed. See below for recommended options.
4. The capability to create and receive funds through Dwolla’s Forms and Hub Pages has been removed. Dwolla Buttons can no longer be generated and aren't supported.
What functionality will the Dwolla web and mobile applications facilitate for Personal accounts?
The ability to....
- Receive and withdraw funds to their connected bank or credit union account
- Fulfill payment requests from a Business, Non-profit, or Government account using a connected bank or credit union account
- Authorize applications using OAuth or the off-site gateway
Can my organization still payout to Personal accounts?
How might the changes on December 7, 2016 affect me?
- How do I receive or send payments with new individuals? Dwolla removed the signup experience on dwolla.com/register for Personal accounts. Organizations looking to onboard new customers have three options:
(Recommended) Use Dwolla’s API for onboarding individuals.
- (Recommended) Business, Non-profit, and Government accounts may send or request funds from any account type using the web, mobile, or a third-party application (e.g. JotForm). Also known as Dwolla Direct, this onboarding option sends new users an email. A unique URL provides a simplified experience to claim funds or fulfill a payment—no full Personal Dwolla account required. Learn more about the Direct experience.
We've created a specific URL (https://www.dwolla.com/register/customers) to facilitate full Personal account signup moving forward. This URL MUST be used when proactively encouraging Personal accounts to be set up. Business, Nonprofit, and Government accounts may still register on dwolla.com/register.
Personal accounts use Dwolla.com to pay my organization.
Because Personal accounts can no longer use the ‘Send’ function on Dwolla’s web or mobile applications, your organization will need to transition your payment flow to one of the following collection methods:
Use Dwolla.com to set up a one-time or recurring payment request.
Use the Transfers API to allow your customers to pay on your website or application using their bank accounts. View our developer guides to learn more.
Use our partner JotForm to create simple online and mobile forms to enroll users and collect funds digitally.
Individuals use the Dwolla iOS, Android, or Windows app to pay my organization.
Dwolla recommends transitioning all mobile customer activity to our mobile web browser version (mobile.Dwolla.com). The web app can easily be pinned to a user’s mobile home screen, just like the app and easily fulfill requests sent by your business.
My Personal account customers like to transfer funds into their Dwolla account OR my business model requires immediate payments from an available balance (i.e. ‘Real-time payments only’ from your ‘Settings’).
Dwolla’s API offers a number of co-branded and white label options that would preserve this functionality for your existing and future customers. Learn more in our developer documentation.
Individuals use or have used Dwolla.com to set up ‘Scheduled payments’ or ‘Recurring requests’ with my organization.
Personal accounts with existing scheduled payments will be honored through the completion of their life cycle. After December 7, 2016, Personal accounts will be unable to set up new ‘Scheduled payments’ or ‘Recurring requests’; however, businesses, nonprofits, and governments may set up and send recurring requests to Personal accounts at any time.
As an organization, I only use the web or mobile apps to transact with other businesses, nonprofits, and governments.
Neither you nor your customers are affected by these changes in functionality.
Does this affect White Label or Co-branded API functionality?
How did Dwolla communicate this to our customers? When?
On November 11, 2016, Dwolla notified all fully registered account types of the change in functionality. This included those individuals and businesses that provided complete account registration information on Dwolla.com or through the API. We did not notify Direct or White Label accounts, as their account functionality wasn't impacted by these changes.
As a courtesy, ongoing email reminders were sent by Dwolla throughout the month of November and early December.
What should I say to my Personal account customers?
We recognize that every organization uses Dwolla differently and therefore may be impacted differently. Feel free to use this FAQ to help communicate and inform your users.
Are other products and services going to be affected?
There are no immediate plans to change additional products or services in the near future.
Will Dwolla’s API continue to support applications building Peer-to-Peer or Account-to-Account functionality?
Absolutely. Dwolla will continue to support applications that facilitate peer-to-peer (P2P) transactions, which includes both Dwolla White Label and co-branded (OAuth) applications. Take a look at our developer documentation to learn more.
Why the change?
A lot has changed since Dwolla released its branded mobile apps and other easy-to-use products aimed at customers back in 2011. Today, businesses and developers use our simple developer documentation, robust API, and dynamic infrastructure to build their own apps, experiences, and solutions. These changes will provide focus and clarity on the products and services these new customers crave.