Live data from Hacker News

Stripe’s new funding round values company at $35B

wsj.com

221–230 of 263 posts

Re: Stripe’s new funding round values company at $35B

#221
post #66

Earlier quoted context omitted.

Not OP but I've used the Stripe API extensively (I know it nearly end to end due to implementing one of the framework client libraries) and to me the parts that come to mind if I think "bloat"/"unintuitive" are SKUs, Coupons, and most likely what GP is talking about the new payment intent APIs, even though I don't think there's a real way you could implement them any better given the PSD2 requirements. By far Stripe…

> ... most likely what GP is talking about the new payment intent APIs, even though I don't think there's a real way you could implement them any better given the PSD2 requirements. Yes, definitely this. Payment intents is so much more complicated and convoluted than the previous "Charges" API. Stripe went from one of the easiest bits of my app to develop to one of the most difficult, to the point where I'll admit it…

I agree with everyone else re Payment Intents. I started using them in "beta3" last December(?) and did my last "upgrade" to PaymentIntents (really a full replacement of the Stripe integration) 2 weeks ago.

As others have said, the documentation is the major issue. PI takes time to understand, particularly if used to the old way. The documentation is improving but still a mess. Code examples miss steps, and I only made progress when I found this page: https://stripe.com/docs/payments/payment-intents/web-manual which 2 weeks ago wasn't clearly linked in the documentation (and https://stripe.com/docs/payments/payment-intents/migration where I kept ending up had contradictory code for the last stages). The split between automatic and manual confirmation isn't helpful.

Like others, each integration took longer than the 1 day I expected. I resorted to reading the API documentation at times to work out which JS method I needed - something I don't normally need with Stripe! handleCardPayment() vs handleCardAction() vs createPaymentMethod()... there's so many code snippets floating around in the docs for contradictory flows.

If Stripe really want to improve matters, a "What do you want to do?" wizard that asks questions like "When do you want to confirm?" and "Do you need to store the card?" and produces the right code snippets at the end would be helpful.

I also feel Stripe has dropped the ball in Europe. I was consulting with a client with not-insignificant turnover, and I recommended they switch to Stripe. The sales team took a week to reply to his enquiry, then didn't answer the questions but returned a boilerplate response. And this went on. It's not a good impression and made me look bad. I'm going to be less open to recommending Stripe to existing, established businesses now.

4-6 years ago Stripe was a shining example of a motivated sales and support team. Now - old and painful-to-integrate competitors like SagePay are doing better. Or shudder Braintree, who have arrived with discounted rates, terrible documentation, but an easy-to-drop-in JS widget for all payment methods.

Re: Stripe’s new funding round values company at $35B

#222
post #54

[Stripe cofounder] Thanks to everyone here who took a chance on us in the beginning and shared helpful feedback over the years! How to serve startups/developers more effectively at scale is still the main thrust of our product focus. We've fixed and improved a lot of things since we launched here in 2011, but we also still have a lot of work to do. (Both "obvious things we want to fix" and "new functionality we want…

I’m going to ask a favor on behalf of a multi billion dollar industry: please figure out how to service cannabis companies. I build cannabis tech. Its reall stressful when doing over $1 million in sales in a month and it’s literally all freaking cash and we have to spend hours even with a counting machine counting $20 bills. Please tell me what your plan is to support legal cannabis. Thanks

Federal legislation is required.

Re: Stripe’s new funding round values company at $35B

#223
It's not that I don't like Stripe, but was it really so difficult to process payments before? When I start working with online payments in 2007/2008 we had multiple easy to use solutions for processing at least credit and debit cards.

You could have a test account in less than an hour, and be ready to process real transactions in less than a week.

Stripe has plenty of competition, most of which have been around longer. You could argue that Stripe have a better API and that certainly has value.

Re: Stripe’s new funding round values company at $35B

#224

Earlier quoted context omitted.

Most of those categories are from financial institutions or card networks. Stripe has been working with them so we can support more businesses, and I know of quite a few networking equipment businesses that run on Stripe today. If you're still seeing any trouble, we'd love to take another look—our support team's at support@stripe.com (and my email's edwin@stripe.com).

Are the telecom and networking sectors subject to significantly more fraud than average? That seems... surprising

Grey market VoIP fraud

Re: Stripe’s new funding round values company at $35B

#225

Earlier quoted context omitted.

Not OP but I've used the Stripe API extensively (I know it nearly end to end due to implementing one of the framework client libraries) and to me the parts that come to mind if I think "bloat"/"unintuitive" are SKUs, Coupons, and most likely what GP is talking about the new payment intent APIs, even though I don't think there's a real way you could implement them any better given the PSD2 requirements. By far Stripe…

Email sent! I'm pretty nostalgic, so I do miss the old Charges API sometimes. But Charges assumed payments were binary—and we all know they're most definitley not. This also doesn't help with the new SCA regulations that started rolling out last Saturday ( https://stripe.com/sca ). We've built Payment Intents to be future-proof. It tracks your customer's checkout flow, actually provides logic for retrying payments (s…

I agree that Payment Intents is a lot more complicated than Charges - it's like a snowball effect where a small amount of extra complexity in an underlying API (SCA) gets exaggerated into ever more complexity with each API that added on top of it.

By the time it gets to our implementation it's horrible and occasionally (2% of the time?) we get a payment attempt that the client has handled and submitted to our server but isn't in succeeded state. We temporarily fix this by redirecting them back to the payment page but this time in 'Charges' mode. Which seems to work about 50% of the time I wonder how much of this complexity is necessary - inevitable given SCA - and how much is because of Stripe's desire to support DD / bank-based payment methods in one integration. I guess we will see if, once SCA becomes widespread, other payment processors have simpler integrations...

Speaking of SCA, I really don't understand the motivation - it's not like higher fraud rates were hurting consumers, since those costs were borne by the merchants. My suspicion is that it is in the interest of card-alternatives like Sofort to add some friction to card payments, after all if every customer has to visit their bank for authentication anyway, why bother with a card payment at all?

That said, it is infuriating that after wasting all that time re-developing, SCA doesn't seem to have gone live at all. It reminds me of GDPR - the law abiding god-fearing types spend weeks worrying about compliance, disrupting their business; whereas the cowboys just take no notice - and get away with it.

It seems to be how the EU rolls: sweeping changes with terrifying penalties and sudden deadlines followed by minimal or selective enforcement.

Re: Stripe’s new funding round values company at $35B

#226

Earlier quoted context omitted.

Besides your product, I thank you all at Stripe for setting an example of what real API/SDK documentation is.

> I thank you all at Stripe for setting an example of what real API/SDK documentation is. It's not just their documentation, Stripe's versioning, backwards compatibility support, and fast improvements probably make it the single best API I've ever worked with. I have new projects that use the latest and greatest Stripe API and features, but also older projects that use their 5 year old APIs, and both work without a h…

Meanwhile, PayPal’s CSV transaction export feature is still underdocumented and shows that an account’s transaction history is not immutable: https://money.stackexchange.com/questions/65917/calculating-...

Re: Stripe’s new funding round values company at $35B

#227

Earlier quoted context omitted.

Besides your product, I thank you all at Stripe for setting an example of what real API/SDK documentation is.

> I thank you all at Stripe for setting an example of what real API/SDK documentation is. It's not just their documentation, Stripe's versioning, backwards compatibility support, and fast improvements probably make it the single best API I've ever worked with. I have new projects that use the latest and greatest Stripe API and features, but also older projects that use their 5 year old APIs, and both work without a h…

> It's not just their documentation, Stripe's versioning, backwards compatibility support, and fast improvements probably make it the single best API I've ever worked with.

I completely agree - I consider Stripe the gold standard for an API. Best I've ever used.

Re: Stripe’s new funding round values company at $35B

#228

Earlier quoted context omitted.

Congratulations! Stripe has consistently made my life as a developer and entrepreneur significantly easier. I still remember that feeling of relief some 5-6 years ago thinking, "Yes! I don't have to use PayPal's API!"

Customers still want PayPal though :( Can't wait for Stripe to integrate PayPal as one of the options. Seems unlikely to happen, but I keep my fingers crossed.

I use paypal because their arbitration (buyer protection) has worked very well for me as a buyer when a vendor tries to screw me over (which does happen from time to time). I do otherwise prefer stripe. I've always hyped it to my friends as a well made and reliable service.

Re: Stripe’s new funding round values company at $35B

#229
post #96

Earlier quoted context omitted.

I respect the scale of your ambition and the suite of services/products you guys offer to realize it. I love the copy on Stripe's website. Who wrote it? Godspeed.

> I love the copy on Stripe's website. Who wrote it? It's not available at Stripe's home page. Would you mind sharing it? Thx

"Copy" in this context is the text: https://en.wikipedia.org/wiki/Copy_(written)

So yes, it is available on the home page - it's the most important thing there!

Re: Stripe’s new funding round values company at $35B

#230

Earlier quoted context omitted.

Customers still want PayPal though :( Can't wait for Stripe to integrate PayPal as one of the options. Seems unlikely to happen, but I keep my fingers crossed.

I use paypal because their arbitration (buyer protection) has worked very well for me as a buyer when a vendor tries to screw me over (which does happen from time to time). I do otherwise prefer stripe. I've always hyped it to my friends as a well made and reliable service.

The vendor experience with PayPal is appalling though. They'll randomly take money back off you when a customer hasn't even complained, frequently they'll just freeze you out of your account for months at a time. Better not rely on that seasonal income, half the time it'll be delayed by three months ...
Post reply on HN