About Dwolla

Dwolla is an online payments solution that helps businesses of all sizes organize, scale and automate payments in a secure environment.

Dwolla offers a host of features such as onsite payment processing, adding and verifying bank accounts, mass payments, data tokenization for improved security, on-demand transfers and more.

The application enables users to manage funds, applications, multilevel access and monitor transactions via a visual dashboard. Additionally, the platform allows adding multiple users with different rights. Dwolla uses Plaid for instant Automated Clearing House (ACH) and Sift Science for fraud monitoring.

Pricing is based on transactions and a monthly subscription. Support is available via email, phone and live chat.


Supported Operating System(s):

Web browser (OS agnostic)

19 Reviews of Dwolla

Average User Ratings

Overall

4.16 / 5 stars

Ease-of-use

3.5

Value for money

3.5

Customer support

4.5

Functionality

4.0

Ratings Snapshot

5 stars

(8)

8

4 stars

(8)

8

3 stars

(2)

2

2 stars

(0)

0

1 stars

(1)

1

Likelihood to Recommend

Not likely

Very likely

Showing 1 - 5 of 19 results

December 2019

Anonymous

Verified Reviewer

Company Size: 11-50 employees

Time Used: More than 2 years

Review Source: Capterra


Ease-of-use

5.0

Value for money

5.0

Customer support

5.0

Functionality

5.0

December 2019

Scalable service with fantastic customer service

An amazing support team that over delivers on an amazing customer experience.

Pros

Reliable platform that you can integrate with ease.

Cons

Nothing wrong with using Dwolla to date!

October 2018

Aalok from EnergyFunders

Company Size: 2-10 employees

Industry: Financial Services

Time Used: Less than 12 months

Review Source: Capterra


Ease-of-use

4.0

Value for money

3.0

Customer support

2.0

Functionality

5.0

October 2018

Great software, great API, marred by mixed quality customer service

Overall the experience is good. Using Dwolla as a system for sending and receiving automated payments via ACH is the primary goal and purpose. Having implemented the API, we have achieved those goals. Also having our customers go through verification and becoming verified customer records solves a major point for us as well. That said, the negative points come into play when something goes awry and you need support, or someone to talk to, and the only thing you can do is put a message in the slack channel and wait ...

Pros

There are many things about the system that are great. The API and the documentation are excellent. The API is extremely robust, and the platform itself is easily navigable to perform actions manually. The ability to vet users by creating verified customer records is excellent as well. The initial sales conversation is great as well, and pretty much all expectations are answered. Even afterwards, having dedicated account managers and a dedicated slack channel are great.

Cons

Getting through the legal review is an arduous process. Afterwards, support through the slack channel is a bit slow. There is no phone based support. After the phone conversations with sales, you cannot call them back for support. There is no phone based customer support. There is no phone based technical support.

October 2018

Anonymous

Verified Reviewer

Company Size: 2-10 employees

Time Used: Less than 12 months

Review Source: Capterra


Ease-of-use

3.0

Value for money

3.0

Customer support

4.0

Functionality

3.0

October 2018

Features good for leasing companies, ok for startups

Customer service has been prompt, but mistakes have still been made by the dwolla team in processing some transactions. The dev team at Dwolla has been very helpful and have offered very good advice. The price is below the competition but not sure the hassle to our customers is worth the savings.

Pros

The software allows for ACH transfers in a API at a reasonable cost.

Cons

API document had several errors that we had to inform Dwolla about, also not as easy to integrate as advertised. Since I believe their clients are generally leasing or real estate companies, the checks they do on our customers is not ideal. Dwolla said they regularly send customers below the age of 26 in document or retry status, for a tech app, those customers will never come back due to the hassle of the dwolla process.

March 2019

Brittany from Tillable

Company Size: 11-50 employees

Industry: Farming

Time Used: Less than 6 months

Review Source: Capterra


Ease-of-use

3.0

Customer support

5.0

Functionality

3.0

March 2019

User Experience

Overall, Dwolla does what we need right now and has been great with supporting our business transactions; however, I do worry about scaling with Dwolla's limited external user support.

Pros

I like how Dwolla interfaces with our platform and streamlines our payment process for customers.

Cons

The verification process can take awhile and if there's an issue with user's verification (i.e. blurry document image, mismatched information, etc.) Dwolla doesn't notify the the user and help explain the issue. There's still a lot involvement on our side (as Dwolla's customer) to look into the issue, troubleshoot it and help the user make the correction). Overall, Dwolla doesn't really account for user errors. I'm hoping this functionality is in Dwolla's product roadmap, because I can't imagine scaling our business using Dwolla with it's current functionality . Also, the micro deposit verification method and time it takes to transact a payment from one customer to another seems too long when there is clearly the technology with other products to do even instant payments. Any way to tighten this window would be ideal.

March 2019

Anoop from Tillable

Company Size: 11-50 employees

Industry: Farming

Time Used: Less than 2 years

Review Source: Capterra


Ease-of-use

3.0

Value for money

3.0

Customer support

5.0

Functionality

4.0

March 2019

API was too granular. Customer service was fantastic.

The customer service was fantastic. Shoutout to @coolstorycory.

Pros

Was able to get transfers working the way we needed it to work.

Cons

Not enough abstraction. Was exposed to - and had to deal with - too much detail. The API was waay too granular. On each "webhook", had to do multiple calls to the api to resolve various attributes associated with the transaction. Biggest issue was that it took some doing to resolve subsequent webhooks to find out which "parent" transaction the webhook was for.