Send payouts with Stripe
stripe.com
stripe.com
Balanced (https://balancedpayments.com) provides a payouts solution for marketplaces like redditgifts, Crowdtilt, Fancy, Artsy, Visual.ly, and many others.
The differences with Stripe include the money being available for payout immediately (instead of 5 days), and the recipient will receive the money the next business day. Balanced has also performed a lot of work to verify merchants with as little information as possible — name, dob, and address. Instead of SSN for an individual you only need to pass in the last four.
Still, this isn't about Stripe vs Balanced -- we just built the API many of our users wanted. Hope you guys continue to do well!
curl https://api.balancedpayments.com/v1/credits \
-u f97912a2cd8a11e2a411026ba7cd33d0: \
-d "amount=10000" \
-d "bank_account[name]=Johann Bernoulli" \
-d "bank_account[routing_number]=121000358" \
-d "bank_account[type]=checking" \
-d "bank_account[account_number]=9900000001"
In that case you can also use Balanced only for payouts by funding your escrow with your own bank account. Stripe would require you to charge your own credit card to perform this service.As you said, the main difference is about focus. Balanced has focused on supporting marketplaces from the beginning and continues to do so.
They've caught a number of fraud incidents for me which has been incredibly helpful (and obviously saves me money).
All three founders have engineering degrees. I built the original version of the product, was the second engineer at Milo.com, and wrote DDoS prevention software in college. Mahmoud built high-frequency trading systems for Wachovia Securities and built Milo.com's matching and categorization system. Jareau studied Electrical Engineering at U Penn, built GPS enabled devices in college, and wrote Milo.com's original systems to interact pull in data from retailers.
Even our General Counsel codes. He studied Symbolic Systems and wrote some of our internal reporting systems in Python.
Stripe wrote this blog post to promote their brand, Balanced let potential customers know that they have similar functionality. Both companies, in my opinion, offer extremely high-quality services (I have used both in production) and have great engineering talent. I do not think we should knock either company for "promoting their brand", it's important that potential customers (read: HN users) are able to make informed decisions. I think zende, pc, and the original blog post all do a good job of articulating the features available through their respective APIs.
spoiledtechie opinted out that a Stripe employee wished you well, while you only promoted your own brand, and your response was to prattle on about how qualified the founders are and basically list your resumes. Oh, and your lawyer codes too! What fun!
Hint: It's Stripe.
I think it's disingenuous to not suggest that Balanced doesn't 'have the developer's true interests at heart.' They've been really pushing the hypermedia API stuff, which is technologically exciting, as well as doing the whole 'open company' thing, which is taking the concept open source to interesting places.
It's clear they just copied (with permission? consent?) the public interface of Stripe. They tried to copy the documentation format (layout, style, presentation) too, but it came off kinda poorly (margins, people. margins). They have public test cards/accounts, but they fail to test correctly because they get "used" and can't have multiple actions performed against them. Then, there's the whole ID thing. Why the fuzzy heck would you use ugly, long, probably-going-to-run-off-my-screen URIs as IDs instead of short IDs? They advise you to never construct your own API endpoint URIs from shorter IDs, except that's exactly what they do all throughout their documentation.
But, Balanced lets you pay out next day and Stripe holds your funds for 7 days before allowing payment. So, Balanced wins on time-to-pay speed (and they have same-day transfers to Wells Fargo). Though, with Stripe I assume you could eventually have enough of a float in your account to pay out next-day under your own prior funds.
From my complete outsider point of view it feels like Balanced is full of slightly subpar copy ninjas. (obviously just on their API, documentation, and front-end presentation. Their backend could be amazing or it could be meter high jenga code.)
Disclaimer/Validator: I've written a tiny unofficial client for each each product/company. https://github.com/mattsta/stripe-erlang and https://github.com/mattsta/balanced-erlang
Re: UUID's, Jeff Atwood has a good post explaining their pros and cons: http://www.codinghorror.com/blog/2007/03/primary-keys-ids-ve....
> From my complete outsider point of view it feels like Balanced is full of slightly subpar copy ninjas.
I couldn't disagree more. Over the past couple of years, I've come to trust and admire the product as much as any other, including Stripe. These guys know what they're doing.
It's really unfortunate that we have a fractured payment processing market where overlapping them doesn't solve the problem. For example:
Square: Best in-person payment processor. Next day payments if taken before 5 PM PST. Does card-not-present transactions as well. For some insane reason, does not have web access or an API despite being around longer than Stripe and Balanced.
Stripe: Best integration with wp-commerce, third party plugins, etc. Excellent interface. Rapid prototyping and feature rollout. Cons: 7 day rolling payments are slower than Square, Balanced, and Paypal.
Balanced: Fastest payments. Terrible third-party support. Documentation not nearly as good as Stripe, interface is slightly confusing.
I use Stripe for my ecommerce business and Square for in-person transactions, but I desperately want to switch to Balanced because of cashflow improvements. But that's not going to happen until third-party plugin support is vastly improved (I've already opened tickets on this months ago in their tracker with no response). Or I'd switch to Square if they decided they wanted an additional $XXX million dollars in business and offered a web API (what is the reason for NOT having this).
Annoying, but considering where we were just a few years ago, I'll take it.
Calling Balanced a group of subpar copy ninjas is very ignorant. Dealing with payments, fraud, and banks is an extremely difficult. I rather Balanced tackle new problem in the payments like ACH debits than reinventing their documentation. Plus, they are a much smaller team than Stripe.
If a sector is already a polished like project management, then you can complain about how one company is not perfect enough with its smaller features.
(I don't work for either, but I use both apis extensively)
In the US, operating an unlicensed money transmitter is an offense that carries, if I recall properly, up to five years of federal prison time per count[1]. That is to say, if you create a service by which one party is able to send money to another third party, and operate that service without a license where one is required (and under that license adhere to capital, bonding and procedural compliance requirements), you are subject to federal criminal prosecution.
I'd be curious as to Stripe's and Balanced's interpretation of their obligations under these laws vis-a-vis their payout services.
Pros: + auto deposit into the back account without having to make requests
+ easy refund process
+ easy charge identification process
Cons:
- a few customers like using PayPal, so there's that. We dropped PayPal entirely from the online sign up and payment so for the users who wanted PayPal we had to send them our PayPal address. Not entirely smooth or professional, but that's not Stripe's fault, it's the reality of having an entrenched payment processor.
- the dashboard displays total volume, and that's it. Would like this to be configurable. Showing total volume since day 1 is pretty useless, especially since it does not appear to remove refunds.
Many banks in European countries don't charge anything for receiving any wires, including SWIFT, only sending them.
(the $15 fee is just for receiving any wire transfer, and is independent of the standard SWIFT fees)
Disclosure, referral links:
Even cooler would be full blown ACH. We are working with ACH providers now and what a stark contrast to the beauty of stripe. All require some form of monthly fee, paper set-up forms with 1-2 week delays (vetting periods) and API's from the 90's
The risk scales with the size of the transaction. Granted, the risk does not scale at the same rate as the transaction size, but we wanted to keep it simple in the beginning.
What do you think about 1% + 30¢ with a cap?
The money is a bank account is real money after all, and once it's spent, it's gone for good. This is one reason I (and I suspect a few others) feel very uneasy connecting bank account(s) with a third party web service.
The problem with disputes on ACH debits is that the process is not formalized through a standard network like Visa or MasterCard. It's a mess operationally, and there's a near zero chance of winning the dispute. This becomes even worse because of the size of ACH transactions.
We've reduced the risk by requiring trial deposits on any bank account that you want to debit, which is also a problem for a lot of our customers.
To be clear, does this refers to the business accounts / users ? The consumers with personal accounts who dispute the charges have their way and the charging entity is left to deal with the results?
It seems cordial and I would rather read about the two products together than in some later thread I'll probably miss.
We launched payouts in February: http://techcrunch.com/2013/02/14/balanced-payments-ach-api-o...
Right. Those are both things that are on our product roadmap. (:
1) Better support for disputes in the API (right now to get all our disputes, we have to pull _all_ charges and walk them...)
2) The ability to generate test disputes. You guys provide an awesome test API, but there's no way to generate disputed charges in testing, so I can't test any of that functionality...
2) Definitely. We'll keep that in mind!
My startup was in the private beta for this and is in the process of switching to Stripe for ACH payouts from our previous provider bill.com. The folks at Stripe are super friendly and helpful. Two thumbs up! :)
FYI I'm working on a guide to integrating Stripe with Rails[1] and I'll definitely be covering this, as well as Stripe Connect.
IMO in a couple of years the offerings from these two companies will be so close that this distinction won't matter, but for now they are converging in from different directions so you should choose appropriately.
(I feel this is a lot like Box vs. Dropbox. One started from the team/enterprise side, and the other from the personal/consumer side, but now Box offers free 5GB for personal use, Dropbox offers dropbox for teams etc. A couple of years back, it mattered which one you picked depending on your use case, but these days not so much.)
Not really compatible.
By the way, I still run a payments company, and you should not assume that you know what I know (or don't).
You didn't answer the question.
I understand Aaron's motivation. Asking for that info on HN though is the same as starting a fight in a Starbucks. We're better than that.
Payments systems are complex and the regulations are complex. I don't think it's rude to ask questions about complex topics, and here I honestly do not know what Stripe is doing. As both a Stripe customer and competitor I have the right to ask.
http://dockets.justia.com/docket/california/candce/5:2013cv0...
Yes, the law is being metered out in a discriminatory fashion. No, this is the not the way to go about fixing it.
https://stripe.com/docs/tutorials/sending-transfers#transfer...
Example: If something goes sideways on an $100k transfer, $0.25 is 0.0003% of the borked transaction....
My next big problem is taxes. I wish one of these two could make it a no-brainer for the same market-place scenario (eg. selling a work from a South African gallery to a customer in France via a U.S. based marketplace).
As a footnote, I am a very happy Balanced customer @ http://artsy.net.
Bonus: with this, the lister doesn't need a Stripe account and will perceive all of their interactions with money being handled by you or their bank. This means you don't have to, as a part of making the sale to them to list their room, convince them "You should really open a Stripe account."
With Stripe Connect, your users have to have Stripe accounts. This makes sense for, say, Squarespace, where their users are likely to want to manage the business themselves: logging in to their Stripe account, watching their analytics, providing refunds, handling customer service, etc.
This is designed for cases like paying Lyft drivers. The drivers don't really care about the internals; they just want money to appear in their bank account.
There's more at https://support.stripe.com/questions/stripe-connect-vs-sendi....
Is a rollout to scandinavia in the weeks, months or years-timeframe?
What OS/browser are you on? (Feel free to email me at amber@stripe.com as well.)
And Paypal can afford many more hours of lawyering than most startups.