Dwolla Blog

Well, I still see it as an accepted method of payment by the Treasury Department.
https://www.pay.gov/public/form/start/4624405

The Order is interesting.
http://files.consumerfinance.gov/f/201603_cfpb_consent-order-dwolla-inc.pdf
(As well as being one of, if not the, smallest monetary orders the CFPB has ever made.)
It is not based on Dwolla being breached in any way, or particularly insecure security practices (IMHO). Nor is it based on any particular legal requirement Dwolla has to follow. It's based on Dwolla advertising how secure they are, and the CFPB decided that, in their opinion, they were not that impressive. Hence they felt Dwolla misrepresented itself.

Specifically (on their main complaint), encrypting data at rest (as opposed to encrypting data in transit, as well as tokenizing data, which they do, and is very important) is the least important part of securing data...because the only way that stored data is used is by decrypting it...any anyone who has gets far enough to access that encrypted data at rest, would also be able to access the private security key that is decrypting it at the same time. Encryption for at rest data is more important for backups.

It's also interesting that it appears (maybe) Dwolla got on the CFPB's radar by writing them a letter two years ago, in part discussing how secure they are...
http://blog.dwolla.com/net-neutrality/

And from the "Isn't that Ironic" section...
http://www.gao.gov/assets/670/666000.pdf
The CFPB failed its…

Here's a few more to add to your list (not all SaaS)...

--ANALYTICS

Snowplow (https://github.com/snowplow/snowplow)

Segment.io (http://segment.io)

--CRM

Close.io (http://close.io),

Streak (http://www.streak.com/)

Base (http://getbase.com)

--SALES

ElasticSales (https://elasticsales.com/)

--CUSTOMER SERVICE

Metaverse Mod Squad (http://metaversemodsquad.com/)

--DATA

Factual (http://www.factual.com/)

--DATABASE

Titan (http://thinkaurelius.com/)

Tinkerpop (http://www.tinkerpop.com/)

Bulbs (http://bulbflow.com)

Datomic (http://datomic.com)

--LOG MONITORING

Logstash (http://logstash.net)

Lumberjack (https://github.com/jordansissel/lumberjack)

Fluentd (http://fluentd.org),

Flume (https://github.com/cloudera/flume)

Kafka (http://sna-projects.com/kafka/)

Scribe (https://github.com/facebook/scribe/)

--ACCOUNTING/INVOICING

Harvest (http://www.getharvest.com/)

Ballpark (http://www.getballpark.com/)

PaySimple (http://paysimple.com/)

AcceptPay (http://acceptpay.com)

FreshBooks (http://www.freshbooks.com/)

FreeAgent (http://www.freeagent.com/)

Blinksale (http://www.blinksale.com/)

--PAYMENTS

Balanced Payements (https://www.balancedpayments.com/)

Dwolla (https://www.dwolla.com/)

-- BANKING

Simple (http://simple.com)

--PHONE/PBX/SMS

Plivo (http://plivo.com/)

Tropo (https://www.tropo.com/)

Twillo (http://www.twilio.com/)

PhoneBooth (http://www.phonebooth.com/)

-- PROJECT MANAGEMENT

Orchestra (http://www.orchestra.com/)

-- RECOMMENDATION…

• The absolutely best way: have your payees have an account with your bank and have internal-to-your-own-bank transfers. Some USA banks make this very easy.

• Second best, bank to bank transfers of money to your trusted payee. International transfers are in a state of flux, and may after 2013 be able to avoid high fees. Not yet though.

Otherwise:

• Trusted payee who is sophisticated and smart: Bitcoin.

• Trusted USA to USA party: Dwolla. See: http://Dwolla.com Dwolla only for trusted parties or individuals! Dwolla has surprisingly small cost, because they do NOT deal with credit cards. Best for others who have DWOLLA accounts, or USA to USA bank transactions or people willing and able to submit to USA law and bank regime.

• The credit card interbank system typically has fees in the vicinity of 2% to 3% of the gross transaction. Avoid.

• Avoid PayPal. The PayPal terms of service agreement indicates that whatever PayPal decides in a dispute, PayPal's decision is final without appeal. This in known as a contract of adhesion in the USA, where one party has all of the power. Because of this, do not use PayPal. Look up "contract of adhesion" for details.

• Most other online services rely on the credit card interbank system with its high fees of 2% to 3% for transfers. Avoid.

Off Topic:

• Non-trusted parties? Don't deal with them without a letter of credit. Look up "letter of credit" for details.

Dwolla | Front End Engineer | Des Moines, IA | ONSITE

Looking for a smart and compassionate person to work with me on a Marketing Engineering team. We're doing our best to cultivate an inclusive culture (don't be an asshole) and to build a useful SaaS product (API) that we can be proud of. Des Moines may be flyover country, but it's sort of a hidden gem. I don't care at all if you have a degree, only that you've got some experience and are good at learning.

Here's the start of the actual posting:

We care about mastering the ideal platform to move money. At Dwolla, we empower our engineers to select the right languages, tools, and libraries for the job and deliver products based on those choices. If you want to become of a master of your craft while building something that matters, Dwolla may be right for you.

Our Front End Engineers design and build usable, performant, and beautiful user interfaces that help our users accomplish their goals. As a member of the Marketing Engineering team, you will work closely with marketing stakeholders to build web experiences that communicate the value of the Dwolla platform to potential customers, as well as maintain a strong and cohesive brand across all of our properties.

https://hire.withgoogle.com/public/jobs/dwollacom/view/P_AAAAAACAADjJHca-MY0du7

or check out all our postings here:
https://www.dwolla.com/careers/

It really depends on who you are sending money to. Assuming your sending to people with bank accounts a remittance service would work, like transfer-to (recently renamed Thunes) [1] and EMQ (sea only) [4]. There are several services like this, and its how mobile wallets and remittance agents (electronic ones) send cash. You may need several to provide maximum coverage if operating globally.

Each country also has their own remittance providers [2] so if you are serving a specific country it would be worth digging to find out who has the best APIs. Mastercard has a service [3] that supports 80 countries but your recipients require a card. Note if your recipient is a business with an EDC machine there is a nifty way to send them cash using MC VCNs (what some global hotel booking sites use).

Most remittance providers now send to wallets in addition to bank accounts, which can be used to send cash to non-banked users. Though in practice this could be a pain for them and coverage is limited and the mobile wallets vary in quality and KYC restrictions.

1. https://www.thunes.com/

2. Only use licensed ones! Spotted this one operating in us: https://www.dwolla.com/

3. https://developer.mastercard.com/product/mastercard-send

4. https://www.emq.com/

Your best choice would be Dwolla - https://www.dwolla.com/pricing/

You probably might want to start with the 0.5% Pay as You Go plan and as you go bigger, you can switch to a fixed-fee model. Once you switch to the other plans, you will be paying a flat ~$1 per transfer (both sending and receiving).

Handling fraud and chargebacks for ACH is more complicated compared to processing payments via cards. You probably should look into this before going live.

Source - Have built payment flows with ACH and cards for multiple marketplaces. Not associated with Dwolla at all. Just a happy customer.

EDIT:

Alternatives (that I have not tried) are Synapse - https://synapsefi.com/ach and Finix https://www.finixpayments.com/