Live data from Hacker News

Stripe raises $600M at nearly $36B valuation

axios.com

271–280 of 463 posts

Re: Stripe raises $600M at nearly $36B valuation

#271
post #254
post #239

Adyen: $25b market cap, with 2019 full year net revenue being $538m, up 43% year-on-year. https://www.adyen.com/investor-relations/news/h2-2019-financ... Stripe: Significantly less than Adyen, as many have reported. ---- Same business model, with Adyen having a higher operating margin. This should be interesting to see how this plays out. Either Adyen will skyrocket in value, or Stripe will decrease in value.

Isn’t adyen cheaper too?

They also return interchange fees on refunds.

Re: Stripe raises $600M at nearly $36B valuation

#272

Earlier quoted context omitted.

>However, Stripe offers SEPA direct debit, which is usable with any European bank account and may work better for you. 1) SEPA has an 8-week no-questions no-appeal refund model, which is fundamentally incompatible with a SaaS business 2) Stripe doesn't support SEPA on Checkout 3) Stripe doesn't support SEPA on non-EU/US accounts

Regarding points 2) and 3), I wasn't aware of those limitations. I admit to never having tried to use SEPA direct debit with Stripe, I just saw it in their docs. Regarding 1): is it? Credit card payments can also be charged back, often for a period longer than 8 weeks. And both "aaS" products as well as certain retailers selling and shipping physical goods, do offer direct debit. I can't quote any fraud rates, but it…

Credit card payments have an appeals/dispute resolution process.

SEPA doesn't. You have to sue your customer if you want the money back.

https://www.williamfry.com/newsandinsights/news-article/2013...

Re: Stripe raises $600M at nearly $36B valuation

#273

Earlier quoted context omitted.

Living in Germany and my company is based here. We tried SEPA but it’s a PITA to charge customers with it. Especially B2C which we are. Customers can arbitrarily chargeback even after several days. Not only that, they can ask for a refund, get the refund and then charge back. So we end up paying them! And there’s no way to prevent it. At least that’s the way it was a few years ago when stripe sepa was still beta. The…

> Customers can arbitrarily chargeback even after several days. You are aware that this is possible with credit cards as well, right?

Credit card chargebacks have an appeals / dispute resolution process. SEPA does not.

Re: Stripe raises $600M at nearly $36B valuation

#275

Earlier quoted context omitted.

I don't understand this idolization of small over large (or vice versa for others). The thing that matters most is that businesses best satisfy their customers, whether they are small or large. There's no benefit to having a small business that provides inferior products or inferior service relative to a large company. I buy from small companies all the time and many of those that I do will likely survive because the…

> There's no benefit to having a small business that provides inferior products or inferior service relative to a large company. Sure there is - in terms of where the profit goes. The profit in a small business goes to the owner(s), who usually live somewhere in the local community, and in turn that money stays within the community to be spent on other businesses there. When a Walmart comes along, the profits all mov…

And that wealth goes into people's pension funds, and gives them more money to spend in their community in retirement. Why the assumption that money magically disappears once it gets to Walmart?

Re: Stripe raises $600M at nearly $36B valuation

#276
post #146

Earlier quoted context omitted.

My top issues running my business on Stripe: 1) Many countries still only allow depositing a single currency (i.e. Aus/AUD), doubling the cost of transaction due to the currency conversion, even tripling when we have to convert it back to pay our bills. I always get told either "soon", or "not possible due to the law", despite competitors doing it. 2) If we were an EU company, we'd get charged 1.4%+25c on transaction…

Great feedback... thank you. In case it's useful, some context on them: On (1), we started an FX team this year. (There are a lot of legal complexities here around how the funds move, who has title to what at which moment, and so on.) But we're investing significantly in improving it and it should get better soon. On (2), the core issue is card network pricing rules -- by design, they discriminate on the basis of whe…

>(3), refunds aren't free for Stripe, and we were previously in a position where businesses with a lot of refunds were being subsidized by those who didn't. We want to give this margin away more sensibly.

I understand they're not free, but I also understand Stripe does get a considerable portion back that they are no longer passing on?

Couldn't this just have been applied to the problematic businesses then rather than all?

Re: Stripe raises $600M at nearly $36B valuation

#277
post #162

Earlier quoted context omitted.

I use Stripe and PayPal currently but on the next platform I'm currently building I'm strongly (and very seriously) considering Braintree. With PayPal, the fraud experience has been nothing short of amazing. Out of many many thousands of transactions, I've only had about 3 or 4 transactions get flagged as high risk by PayPal. What this means is PayPal will hold the funds, review the transaction and then either give y…

> Their docs are typically good, but the SCA / Payment Intents docs are not really at the same standards as the rest of their documentation yet. Stripe PM on the Payment Intents API here. You're right that there were some rough edges when we started rolling out this new API last year. SCA is complex and we want to help make it easy to navigate this regulation: we designed the new APIs to abstract away as much of the…

FWIW, one thing you could usefully do is have someone double-check the code snippets in the online guides. They looked very helpful (and much needed) when I was reading them recently, but I remember almost immediately running into examples where something just didn't make sense. Then if I followed through to the corresponding code in the samples repo, it really was slightly different to what was shown in the guide on your docs site. The guide to setting up a new subscription using the new API definitely had some instances of that problem. The more recent guides would also benefit from more explanation of why the sequence of actions shown was what it was and what each API or webhook used was actually for. Either that or some concise, big picture overview would be good (or ideally both).

Re: Stripe raises $600M at nearly $36B valuation

#278
post #214
post #153

Earlier quoted context omitted.

Completely agree on #3. Felt like a big blow to have Stripe do this. A lot of subscription based businesses were built around "no-hassle refunds" as a core feature enabled by Stripe and will now need to rethink this.

Stripe isn’t being transparent on refunds. The issuing bank returns interchange on a refund. The true cost to stipe is a fraction of a penny to put the request on to the network. Other processors will refund interchange, this is unique to stripe. I am sure stripe is refunding interchange for their larger merchants that are on interchange plus billing. There is no way target is eating interchange on refunds. They are…

This is actually what prompted us to start looking at interchange plus processors, plus the issue that our negotiated deal in Canada (where we're based) doesn't apply to our US clients. We went with Stripe for "simple" pricing knowing there were better deals out there, but it's no longer that simple for us at least.

Re: Stripe raises $600M at nearly $36B valuation

#279
post #146

Earlier quoted context omitted.

Great feedback... thank you. In case it's useful, some context on them: On (1), we started an FX team this year. (There are a lot of legal complexities here around how the funds move, who has title to what at which moment, and so on.) But we're investing significantly in improving it and it should get better soon. On (2), the core issue is card network pricing rules -- by design, they discriminate on the basis of whe…

>(3), refunds aren't free for Stripe, and we were previously in a position where businesses with a lot of refunds were being subsidized by those who didn't. We want to give this margin away more sensibly. I understand they're not free, but I also understand Stripe does get a considerable portion back that they are no longer passing on? Couldn't this just have been applied to the problematic businesses then rather tha…

It varies based on the card type, country, and other things. We could expose all of that more directly but the trade-off there is obviously pricing complexity, which we'd like to avoid.

In our analysis in making this change, we saw that this simply makes little difference for the vast majority of businesses. For example, if you're processing $100k/year and refund 5% of your payments (which would be on the high end of normal), it works out to about $12/month.

While refund rate of course is not definitively coupled to the quality of a business, we do see across our portfolio that it is strongly correlated. Given a basket of possible fees (for example, higher fees on Amex, which most other providers have), we prefer the fees that, on the margin, are least consequential for the businesses that are doing the best job of serving their customers.

Having said all of that, none of our pricing is cast in stone, and we always genuinely appreciate feedback, including contrary views.

Re: Stripe raises $600M at nearly $36B valuation

#280
post #75

Stripe cofounder here. This isn't really new -- it's an extension of our last round ( https://www.cnbc.com/2019/09/19/fintech-start-up-stripe-notc... ). That said, we've seen a big spike in signups over the past few weeks. If any HN readers have integrated recently and have feedback, we're always eager to hear it. Feel free to email me at patrick@stripe.com and I'll route to the right team(s). As always, thank you to…

i'm asking in a very unofficial position.

The company I work for is in the travel industry and we've received a large number of charge backs compared to normal. Our agents are working as best as they can, but our tools were never really designed for 5000+ tickets to be active at 1 time, so it's slow going for them as they contact the guest, then contact the provider, then talk to the guest, etc.

Are you going to offer some lenience to companies who have gotten a huge spike in charge backs just due to an increase time in support tickets?

We are trying to find ways to just refund the guest where we know the hotel has closed, but there's no master list of that so we can't just blindly refund everybody

Post reply on HN