Live data from Hacker News

Stripe Billing

stripe.com

321–330 of 364 posts

Re: Stripe Billing

#321

Earlier quoted context omitted.

Any information on support for Europe? And if support for Europe were to be in the pipeline, would it be for the whole of Europe or only specific countries? We'd love to use Stripe for billing as well, but because Stripe is an American company, we feel like as Europeans we're constantly an afterthought and would therefore prefer a European provider. What's your opinion on this? Btw, I was at the Stripe offices 2 year…

The core Stripe Billing features actually work in the EU: flexible billing, our recovery tools, and invoicing. You can use subscriptions with all of the payment methods on Stripe, including SEPA DD, ideal, and more. But as Patrick mentioned, there's a lot we can do to make the experience great for European companies and that's what we're focusing on right now. We're thinking about ways to localize the invoices, add E…

Heya! Would like to be in beta for this. I'm mike, at certsimple dot com.

Re: Stripe Billing

#322

Earlier quoted context omitted.

Thanks for the reassurance on the current subscriptions integration. A first look at the API suggested that updating to the latest Stripe API was now going to involve some breaking changes, e.g., introducing products and requiring one to set up a plan. On the decline rates, we actually have dropped you (Stripe) a line -- many times, in fact, and via multiple channels. In some cases, we never received a reply at all.…

I'm a manager on Stripe support. I'm incredibly sorry that happened. Can you email me at edwin@stripe.com and I can look into this further?

Thank you for the invitation, but as this happened several times over a period of years, there's not really any specific communication worth following up at this stage.

If you'd like to help, I'd suggest that the online documentation pages would be the most effective area you could look into. As Stripe has grown, gaps have appeared from time to time, where dashboard features or API calls weren't fully described. In this case, the entire feature set seem to be missing at the moment, so if there's anything you can do to fill in that gap and provide the kinds of specific details I mentioned in my previous comment, that could help others in a similar position to us as well.

Re: Stripe Billing

#323
post #318

Earlier quoted context omitted.

Let's back up a second. The silence isn't because I/we don't want to talk about this, it's because it was 2am here in Boston and I was sleeping at that point (coincidentally after leaving the office around 1130pm pouring over our new GDPR paperwork). The short answer is 100%, absolutely no - we do not , have not , and will not ever sell your data. We say this pretty clearly at the top in our terms and services, which…

You should resolve the discrepancy between this comment and your Privacy Policy. A message board comment is not legally binding, and what I linked to has substantial wiggle room in interpretation.

Yup - a HN comment is definitely not legally binding. Given some of the flame wars on some of the threads over the years, that would definitely be a scary world.

Based on a number of lawyers (we've gone deep on this over the past several years), I'm confident this is resolved through the combination of our terms and privacy policy - the EU/Swiss privacy shield stipulations, which drove the privacy policy encompasses the specific data there that's shared (check out the section entitled "Collection", which is then what's referenced in the shared section). These are common information to engage in internet commerce like email, billing info, etc. This is actually specifically why we had language in our Terms to encompass the actual financial data. The ironic part of all this is we repeatedly told our legal folks we needed to simplify, simplify, simplify.

All that being said - you clearly came to the page and thought the worst based on the language, so I guess it doesn't really matter if we're legally doing the right thing, we need to make sure you (and other folks who reach us) are interpreting and seeing what we're doing as intended.

Give me/us a little bit of time to figure out how to make this instantly obvious. As I mentioned, we're in the midst of clearing up our house based on GDPR requirements, so it's a good time to revisit. Really appreciate the feedback - only way we get better. :)

Re: Stripe Billing

#324

Earlier quoted context omitted.

Hey Dictum - we're free for non-basic usage, basic usage, and everything in-between. I explained a lot of why this is the case in the blog post link below (when we went all in for free), but it really comes down to the following: PHILOSOPHICAL 1. In software (and the subscription economy) we're moving away from function based pricing to outcome based pricing. Putting this simply in the context of analytics/reporting…

Hey Patrick, thanks for this comment. "Plus, we're able to show our customers they have a problem that we can then sell an add-on for." - I really like that part.

Great. :)

We don't plan on stopping. Admittedly this gets us in some trouble being a growing company, because we need to make sure our free product is the best for our customers AND we offer up stellar paid products. A whole lot of surface area, especially for a bootstrapped company (although we're past the Ramen stage - $10M+ ARR and 45 folks :)).

There's a lot of work we did to make sure we're learning as quickly as possible that really helps advance the mission on all fronts.

Re: Stripe Billing

#325

Earlier quoted context omitted.

Any information on support for Europe? And if support for Europe were to be in the pipeline, would it be for the whole of Europe or only specific countries? We'd love to use Stripe for billing as well, but because Stripe is an American company, we feel like as Europeans we're constantly an afterthought and would therefore prefer a European provider. What's your opinion on this? Btw, I was at the Stripe offices 2 year…

I wonder why the EU is an afterthought when you need to spend millions on compliance for every new feature

From a tax point of view, EU is a lot easier to deal with than the US if you have to collect sales tax in the US.

There are two big differences.

Let's say I'm selling some digital good online. Consider three purchasers, one in the US in the state of Washington, one in Germany, and one in France.

First, how much tax do I have to collect from each?

For the German customer, that is easy. It is 19% VAT. I don't have to care where in Germany they live.

For the French customer, that is easy. It is 20$ VAT. I don't have to care where in France they live.

For the US customer in Washington...it is not easy. There is a state wide 6.5% sales tax, but there are also county, city, and other sales taxes that I have to collect. For example, if the customer is in the city of Seattle, I'm supposed to collect the 6.5% state tax, plus a 2.7% city tax, plus a 0.4% for something called the "Regional Transit Authority"...that's 9.6%. If that person is over in Bellevue instead of in Seattle, it would have been 10% (6.5% state, 3.5% Bellevue).

For the US customer, I have to care where in their state they live. Also, tax boundaries are not guaranteed to line up with postal code boundaries, so to do that tax accurately I really would need to collect their full postal address (which since I'm selling a digital good I have no use for except for calculating taxes).

Second, what do I do with the tax I collect?

For the EU, I sign up for the VAT MOSS system in a single EU country. Then each quarter I have to file a simple form with the tax authorities in that single EU country that simply lists each EU country, what my total taxable sales were in that country, the VAT rate I used, and the amount of VAT collected. I turn the collected VAT over to that single country's tax authorities. Then they deal with distributing it to all the other countries.

For the US...I have to deal with each state I collect tax for separately. Each has its own forms. Each has its own place to file them. Each has its own place to pay.

If you have to deal with more than just your own state and maybe a handful of others in the US, you pretty much have to use a third party service that specialized in handling all of this. For companies in lines of business that are only barely profitable, this could be prohibitively expensive.

If Congress ever decides to require online companies to collect tax for all states, instead of just those that they have a presence in, and they do not require that the states use something like the VAT MOSS system, and they do not require that each state has a single rate for out-of-state non-present sellers, it's going to be nightmare for small companies, and possibly drive many out of business.

Re: Stripe Billing

#326
post #102

Stripe cofounder here. For anyone wondering about pricing, here's our approach. - For new Stripe customers, this is free up to the first (lifetime) $1M of payments. - For existing customers, there's no pricing change. You just get more functionality than before for free. This is what we generally try to do: we want Stripe to continually become better value for you over time, as you get more functionality for the same…

This looks great, but I also see a lot of functionality being restricted to USA. That would be quite limiting for us as we are based in Europe and have the vast majority of our customers there. :(

Re: Stripe Billing

#327
post #318

Earlier quoted context omitted.

You should resolve the discrepancy between this comment and your Privacy Policy. A message board comment is not legally binding, and what I linked to has substantial wiggle room in interpretation.

Yup - a HN comment is definitely not legally binding. Given some of the flame wars on some of the threads over the years, that would definitely be a scary world. Based on a number of lawyers (we've gone deep on this over the past several years), I'm confident this is resolved through the combination of our terms and privacy policy - the EU/Swiss privacy shield stipulations, which drove the privacy policy encompasses…

For greater context, the reason why I’m saying your Privacy Policy needs to be revised for precision is because:

1. I have experience acquiring data for the financial industry, and your privacy policy looks like the kind used to discreetly allow data brokering for free apps that have a lot of user data, and

2. I’ve seen executives who do sell data deny that they sell data by being overly literal and obtuse about what users mean when they ask if their data is sold. When users ask if their data is sold they’re usually including “data sharing with affiliates”, even if they aren’t savvy enough to use that terminology. The concern there is that user data collected by third parties is allowed to be reshared by their affiliates and under opaque terms that do not preclude monetization.

Re: Stripe Billing

#328
post #318

Earlier quoted context omitted.

Let's back up a second. The silence isn't because I/we don't want to talk about this, it's because it was 2am here in Boston and I was sleeping at that point (coincidentally after leaving the office around 1130pm pouring over our new GDPR paperwork). The short answer is 100%, absolutely no - we do not , have not , and will not ever sell your data. We say this pretty clearly at the top in our terms and services, which…

You should resolve the discrepancy between this comment and your Privacy Policy. A message board comment is not legally binding, and what I linked to has substantial wiggle room in interpretation.

In EU, you need to write something like "...share data with third-party service providers..." already if you use AWS, because customer data will not only be held at your premises, but also held by another company (Amazon).

It seems to be difficult to phrase the Privacy Policy in a way that will satisfy this condition, and at the same time remove the 'wiggle room' you see.

Re: Stripe Billing

#329
post #102

Stripe cofounder here. For anyone wondering about pricing, here's our approach. - For new Stripe customers, this is free up to the first (lifetime) $1M of payments. - For existing customers, there's no pricing change. You just get more functionality than before for free. This is what we generally try to do: we want Stripe to continually become better value for you over time, as you get more functionality for the same…

Its not just a communication problem, it's a pattern. You guys did the same thing last year when you stopped returning fees on refunds. I couldn't believe my eyes when I read that you weren't returning fees anymore. I get not returning the flat 0.30 transaction fee, but not returning the % fees smacks of being more worried about the corporate bottom line than customers. Many processors refund the % fees, and there's…

Which payment processor would you recommend now?

Edit: See also https://news.ycombinator.com/item?id=16772655

Re: Stripe Billing

#330
post #328
post #318

Earlier quoted context omitted.

You should resolve the discrepancy between this comment and your Privacy Policy. A message board comment is not legally binding, and what I linked to has substantial wiggle room in interpretation.

In EU, you need to write something like "...share data with third-party service providers..." already if you use AWS, because customer data will not only be held at your premises, but also held by another company (Amazon). It seems to be difficult to phrase the Privacy Policy in a way that will satisfy this condition, and at the same time remove the 'wiggle room' you see.

Call out the third party service providers explicitly.
Post reply on HN