News for hackers. Stuff that matters.
Re:Stripe adds multiple account support by memset on Wednesday January 08, 2014 @03:51PM (#7026510)
This is great! This is one of the things we looked at when choosing a credit card provider. (We did not end up choosing Stripe, but this certainly sweetens the deal. Always looking for a better rate!)

Does this mean that we could have multiple accounts, with different soft descriptors, merged together? Would we also be able to see, in a single report, the transactions for all of the accounts (rather than having to log in separately to download sales data?)

Can't wait to see more of your de-annoying features!

Re:Stripe adds multiple account support by pc on Wednesday January 08, 2014 @04:09PM (#7026646)
I'd love to hear why you didn't choose Stripe -- feel free to drop me a line. I'm [email protected].
Re:Stripe adds multiple account support by rbritton on Wednesday January 08, 2014 @04:30PM (#7026838)
I'm not the OP, but I opted for Balanced over Stripe due to the delay in getting paid. Aside from that I prefer Stripe's API and overall experience more.
Re:Stripe adds multiple account support by steveklabnik on Wednesday January 08, 2014 @04:51PM (#7026986)
Balanced employee here: if anyone's wondering, we do next day deposits for all accounts and same-day deposits for Wells Fargo accounts. Some people even just use is solely for payouts.

And rbritton, as the guy in charge of the API these days, I'd love to hear how I can make it better.

Re:Stripe adds multiple account support by rbritton on Wednesday January 08, 2014 @05:55PM (#7027434)
I use Balanced for a non-marketplace ordering system as well as in an in-person ordering app. The Balanced dashboard is used for any account management and refunds.

I found the process of actually taking and charging a card to be a bit cumbersome with having to tokenize the card (wait for response), create the customer record (wait for response), associate the card token (wait for response), and finally create the debit (wait for response).

The tokenizing I'm absolutely fine with since it offloads the bulk of PCI compliance to Balanced, but the last three steps seemed a bit much when all I wanted to do was debit the card. I don't have any need to save a permanent customer and card record. This is a process Stripe doesn't have as far as I can tell, but I was ultimately willing to deal with it for the faster payouts.

I also like Stripe's two-factor authentication support.

And, on another note, I was a bit disappointed with both Balanced and Stripe's iOS libraries. They only support tokenizing a card. Though this is likely going to be the bulk of use by many people it meant creating everything else from scratch.

Re:Stripe adds multiple account support by mahmoudimus on Wednesday January 08, 2014 @08:08PM (#7028073)
Hi rbitton,

Balanced employee here.

>> I found the process of actually taking and charging a card to be a bit cumbersome with having to tokenize the card (wait for response), create the customer record (wait for response), associate the card token (wait for response), and finally create the debit (wait for response).

Couldn't agree more. Tracking this issue here: https://github.com/balanced/balanced-api/issues/472. We will have news very shortly on some changes that you might be interested in.

>> I also like Stripe's two-factor authentication support.

This is already done AFAIK. Email me directly -- [email protected]

>> And, on another note, I was a bit disappointed with both Balanced and Stripe's iOS libraries. They only support tokenizing a card. Though this is likely going to be the bulk of use by many people it meant creating everything else from scratch.

May I ask that you open a github issue on https://github.com/balanced/balanced-ios with exactly what you're looking for?

Thank you very much.

Re:Stripe adds multiple account support by tgflynn on Wednesday January 08, 2014 @08:29PM (#7028159)
I just looked at the balanced tutorials here:

https://docs.balancedpayments.com/current/overview.html?lang...

and while the code for "Collecting Credit Card Information" makes a lot of sense I find the steps under "Charge a credit card" unclear. Why does one need to create a customer to charge a card that has been tokenized ? I would also suggest making it more clear in this tutorial what the different numbers mean. For example where did CUXj7DWHSxlMvGDLGSYRI3o come from in step 2 ? As for the card_uri I'm guessing that is the uri that was obtained in the prior tutorial, but guessing makes me a little uncomfortable so it would be nice if that were made more explicit.

I'm also wondering why the balancedpayments documentation emphasizes marketplaces over simple e-commerce sites. Does this mean that balanced is a less appropriate solution for simpler sites (ie. where payments are made directly from a site's users to the site itself) ?

Re:Stripe adds multiple account support by remear on Wednesday January 08, 2014 @09:31PM (#7028393)
Hi there!

Balanced employee here.

You're right. That tutorial could be made much more clear. In fact, this guide and others are being extensively rewritten. The example itself is specific to charging a Card. Therefore, the guide assumes you have an existing Customer since Customer creation is a separate topic. You are correct that the card_uri is an example of one that would be obtained from the previous example. Let me clear up how to charge a credit card.

First, the card needs to be tokenized (information sent to Balanced and securely vaulted), https://docs.balancedpayments.com/current/api.html?language=....

Next, either find an existing Customer or create a new one, https://docs.balancedpayments.com/current/api.html?language=....

Now add the Card to the Customer, https://docs.balancedpayments.com/current/api.html?language=....

Lastly, go ahead and create a new debit, https://docs.balancedpayments.com/current/api.html?language=....

A requirement of the current API is that a Card or BankAccount must first be associated to a Customer before it can be used. This is mainly due to the fact that v1.0 of the API is very Customer resource centric, something that's changing in the upcoming 1.1 release. A Customer resource will no longer be required to charge Cards.

If you have any other questions feel free to hop in #balanced on freenode IRC. We love questions!

Re:Stripe adds multiple account support by zende on Wednesday January 08, 2014 @08:07PM (#7028071)
(ceo of Balanced)

This is great feedback!

Is this essentially what you're looking for?

  require 'balanced'
  Balanced.configure('ak-test-2ficCWmYvpRBBSzC7Me62ZTX0Y2DPGjgt')

  card = Balanced::Card.find('/cards/CC4TsBYO9E4IRQqg0jvrEg9i')
  card.debit(
    :amount => 5000,
    :appears_on_statement_as => 'Statement text',
    :description => 'Some descriptive text for the debit in the dashboard'
  )
Re:Stripe adds multiple account support by rbritton on Wednesday January 08, 2014 @10:28PM (#7028569)
Yes, exactly that. I like having the option to save customers and cards, but I prefer not to be required to for circumstances that don't need it.
Re:Stripe adds multiple account support by steveklabnik on Wednesday January 08, 2014 @07:14PM (#7027858)
Thanks! That makes sense. This process only needs to fully happen the first time, but I bet we can make that a bit easier.

I've made an issue to track this on GitHub, let's talk more over there: https://github.com/balanced/balanced-api/issues/472

Re:Stripe adds multiple account support by ewang1 on Wednesday January 08, 2014 @06:38PM (#7027681)
If you don't have any need to save the customer and card for subsequent charges, then I believe (on Stripe) you can simply pass the token to the payment object API, eliminating 2 of your 4 steps.
Re:Stripe adds multiple account support by rbritton on Wednesday January 08, 2014 @06:52PM (#7027748)
That was my understanding, yes. On Balanced you have to have a customer record with an associated card to do a debit.
Re:Stripe adds multiple account support by ewang1 on Wednesday January 08, 2014 @08:49PM (#7028227)
Ah... I misread and thought you referring to Stripe.
Re:Stripe adds multiple account support by steven2012 on Wednesday January 08, 2014 @05:10PM (#7027132)
Next day deposits? Does this mean Balanced has no reserve policy?
Re:Stripe adds multiple account support by steveklabnik on Wednesday January 08, 2014 @05:18PM (#7027203)
Yup, we don't mandate reserves. Marketplaces are liable for things like chargebacks, so many people do keep reserves and use our escrow functionality.
Re:Stripe adds multiple account support by Axsuul on Wednesday January 08, 2014 @05:52PM (#7027417)
Is Stripe planning on offering next-day/same-day deposits anytime soon (for all accounts)? This is becoming a big problem for us and we're considering switching to Balanced because of it.
Re:Stripe adds multiple account support by pc on Wednesday January 08, 2014 @06:28PM (#7027615)
Yes. Could you drop me a line? [email protected].
Re:Stripe adds multiple account support by jareau on Wednesday January 08, 2014 @08:21PM (#7028125)
Balanced employee here.

Axsuul, thanks for checking out Balanced! Let me know if I can answer any questions.

Re:Stripe adds multiple account support by nicarus1984 on Wednesday January 08, 2014 @04:17PM (#7026715)
I have to say that not only do you have a very good product/service, but I am constantly impressed by your engagement in it and apparent commitment to your customer base.
Re:Stripe adds multiple account support by pc on Wednesday January 08, 2014 @05:03PM (#7027071)
thanks!
Re:Stripe adds multiple account support by jareau on Wednesday January 08, 2014 @04:18PM (#7026734)
@memset who did you end up using for payments?
Re:Stripe adds multiple account support by memset on Wednesday January 08, 2014 @06:18PM (#7027582)
Oh, I just noticed that you are a co-founder of Balanced!

I will say this - and I mean this in the most respectful way possible: it is unlikely I would encourage us to switch to you folks until (frustratingly!) you all are more established!

[Also, I don't mean to single you out specifically: I'm talking about any company who wants to be an integral part of our infrastructure, but the topic at hand happens to be payments.]

I have personally been burned by choosing a neato new startup for critical parts of our infrastructure. Burned in the sense that these startups change their model and pivot quickly, and since we have made them an integral part of our infrastructure, it is frustrating and difficult to change. (Dotcloud, for example, got rid of their free sandboxed tier this past year. This was a great move on their part, but also left a sour taste in my mouth and unexpectedly increased our expenses.) We also get burned when a new company has bugs - because while I personally might understand, our customers are the ones who are affected. It also called into question my ability to evaluate different solutions, and forced me to realize that, for non-personal projects, it is important to use something established.

This is somewhat ironic, since we ourselves are a startup - so I feel the pain of finding customers (or even developers!) every day!

Re:Stripe adds multiple account support by jareau on Wednesday January 08, 2014 @08:16PM (#7028109)
Sorry I didn't disclose that I'm a Balanced co-founder. HN won't allow me to go back and edit now.

Thanks for taking the time to respond, Jay, and I appreciate the honest feedback. I'd be concerned if you didn't take seriously your choices about core pieces of your infrastructure, especially ones that are so closely related to your revenue.

I will say that Balanced has been processing live transactions for over 3 years, works with hundreds of marketplaces and crowdfunding platforms, and has been growing as fast as we can (~780% y-o-y). Unfortunately, there's not much we can do to become more established besides exist longer and continue growing. We're not planning on going anywhere, so we'll keep improving in that dept. as well. :-)

Thanks again!

Re:Stripe adds multiple account support by steveklabnik on Wednesday January 08, 2014 @08:09PM (#7028076)
I think you'll enjoy one of the announcements we're making soon. I bet we're more established than you think.
Re:Stripe adds multiple account support by memset on Wednesday January 08, 2014 @06:09PM (#7027540)
Braintree. Being able to change soft descriptors was useful to us, because we sell merchandise (eyewear) on behalf of different brands. I believe they gave us a better rate. (interchange + basis points, rather than percentage + basis points.)

Because we have these different brands for which we do eyewewar, we found that they had slightly better dashboard and reporting tools. There were also differences in being able to do do "authorizations" separately from "settlements" but I think both now support that process fairly well.

It was also nice that Braintree was able to boast of many established companies, which we already use and trust, for payments. One thing I've learned is to always ask for references!

Between the two, both have a great API. Things have probably changed with Stripe in the intervening year too. Stripe was certainly hungrier - they did a better job returning our calls, understanding our business, etc - but the former ended up having a better rate and the feature set we needed at the time.

But I'm always re-evaluating (fortunately - or maybe unfortunately - if another processor is better for some reason, then given our volume, it is usually worth it for us to switch.) So this is why these kinds of features are exciting to me!