P2P banks, 1 line of code

Not sure why all the comments here are harping on the "one line" thing.<p>The point is that you can transfer money with one command and no pre-existing state. That's pretty great.

Is anyone else annoyed at the mix of parameter naming conventions, or is it just me? (e.g. client_id, emailAddress, client_secret, firstName).

I've got to remember this marketing spin. "A curl to an http endpoint with a plethora of parameters" == Only 1 line of code!

It's not really "P2P" if it's going through a central authority...

Conveniently arranged here in our article in 15 lines!

How is this different from saying that communication via Switft messages is really only one line of code at the end that's important?

I prefer Bitcoin

I'm waiting for someone to create a service on top of this. Think Stripe for ACH transfers.<p>I badly want to use this but the required BSA/AML and CIP compliance are too much for my startup. I would gladly pay someone to handle this compliance and just let me call an API.

1. Create fraudulent product page with billing form.<p>2. Add 1 line of code<p>3. ...<p>4. Profit!

"No, at this time Dwolla is only available for use within the United States." That is unfortunate, would have liked to try it out.

1 line of code in marketing speak.

yay, easier fraud and still no guarantees against chargebacks or merchant protections

Looking for where someone mentions <a href="http://www.opentransact.org" rel="nofollow">http://www.opentransact.org</a> but can't find it so I'll mention it.

Bruce Schneier would be proud.<p>It's good to see the world catching up and putting the emphasis on security.<p>[/sarcasm]

Because curl and a command line with 13 "arguments" is so much easier to use than a website.