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 to build".) I always appreciate hearing from HN users (even if I don't always have time to respond): patrick@stripe.com.
For anyone thinking about what they should work on: I started building developer tools when I was 15 and "tools for creation" is still, IMO, one of the most interesting areas to work in.
> 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 hitch.
> 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.
Its the basis upon which I form my opinion as to what "good docs" look like. It makes you incredibly spoiled when trying to use some of Stripe's competitors.
I've integrated 8+ payments APIs over my career. IMO, Stripe's "secret sauce" is the quality of the API and the documentation. It's so compelling that I repeatedly choose Stripe over other payments systems that offer network effects like PayPal and Amazon.
I sometimes get asked by customers if we take PayPal. I tell them truthfully "no, it's just too much trouble".
It doesn't seem like "better developer experience" is much of a moat, but based on how bad the competition is - year after year - it sure seems to be. I wonder what other services could be "disrupted" the same way.
> I repeatedly choose Stripe over other payments systems that offer network effects like PayPal and Amazon.
For one of the first SaSS products I ever worked on, I (naively) chose Amazon payments. Within six months, Amazon introduced backwards incompatible changes. Six months later, they did it again. For another project I started 5 years ago, I used Stripe. We're still using the same 5 year old API and it works perfectly, even though Stripe has added new features and bells and whistles in their newer versions. Their commitment to backwards compatibility is probably the best I've seen of any fast moving API.
And thank you also for your CTFs. I almost finished CTF 2 (I had the 3/4 of last password) and I learned a lot during this CTF. I am very proud of my T-Shirt.
Wanted to hop in and say thank you for starting Stripe. At my first startup, we had to integrate with an old merchant processor for payments and it was a nightmare. With my current startup, we were able to setup Stripe in the first week of operations and take payments seamlessly without too much hassle. Freeing us up from thinking about how to take payments allows us to focus on our product and building out our company. I'd imagine this is a similar story for thousands of other startups too. Hats off to you, your brother, and all the Stripes.
Stripe has a slick API, but their banned merchant categories (anything telecom or networking related) have caused trouble for many potential clients, esp. as Ubiquiti integrated them as their first payment processor.
The distinction between high risk consumer sales & B2B low risk sales is not drawn by Stripe.
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).
Support told me that our business could not continue to use Stripe 2 years ago, we've been with Payment.ninja since (and pay a little under half what we used to pay Stripe).
I took what Stripe Support told us very literally, and we ceased using DigitalOcean and one other service since their only recurring billing options were Stripe.
We don't want to break Stripes ToS or do wrong by our clients, hence our contract-less, B2B only, monthly prepaid business model. Apparently this is too high risk for your company?
I'm 90% certain Stripe has had a few fly by night calling card companies sign up with them, and gotten burned when the calling card company gets a ton of chargebacks for not delivering everything promised.
Thus, a blanket ban on Telecom and anything vaugely related (like ISPs). Certain flagship clients like Twilio get a pass, but smaller players like SignalWire, Telnyx, Teli, etc do not.
The Ubiqiti forums are also littered with ISPs that signed up with Stripe (since Ubiquiti integrates with them) used it for a few months w/o chargebacks or any fraud, but got an email one day saying they were not allowed to use Stripe. Appeals are consistently rejected or go unreplied to.
I emailed Edwin at Stripe 4hrs ago, have not heard back from him.
That's true that ISPs and WISPs can't really use Stripe (many use Adyen), but pure-VOIP companies offering hosted PBX and such are welcome at Stripe based on feedback I received from several people who work at Stripe.
When I asked Stripe Support about servicing VoIP companies last year they referred me to the prohibited businesses section and said:
"Historically we have seen that the telecommunications industry is one with too high of a likelihood of customer chargebacks. These need not necessarily be chargebacks in fact; the likelihood of potential chargebacks is also a deciding factor in our deliberations."
> Thanks to everyone here who took a chance on us in the beginning ...
Stripe is one of the few successful silicon valley companies that provided a service of real value, with enormous efficiency gains, upfront pricing, and don't screw over people as part of their business model. They may have "disrupted" the online payments market in SV parlance, but they didn't actually disrupt anything, they found a nascent but fast-growing market (online payments), and built a product targeted just for it.
Mastercard and Visa are each worth 10X as much as Stripe. Stripe is one of the few unicorn companies that's probably under-hyped.
Developers rightly praise Stripe's API documentation, but their approach to versioning and backwards compatibility is a gold standard that is not sung enough. What other fast-moving startup that constantly tweaks and changes their APIs also provide backwards compatibility with their earliest versions?
Stripe understands that handling payments is critical, scary, and hard to get right. When a company builds a payment solution that works, there is strong resistance to mess with it. The fact that Stripe is so backwards compatible means that they do not have to.
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.
Take for example all thecredit unions in OR, CO, CA
Like north bay credit union in santa rosa.... their requirwments list for opening an account is RIDICULOUS!!
Other companies want either 3% of your deposits or $3,000 a month for a checking account whichever is higher.
Other banks AND companies will cancel your account if you even have the word “canna” in your name.
Ive literally sat there looking at $160,000 in cash with bills needed to be paid and no way to pay the bills...
You know how fun it is to go to seven different post offices with four employees in tow to buy as many money orders as you can so you can pay bills, such as a $25,000 software bill?
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!"
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 ...
I built opalang.org many years ago - introducing a mix of functional programming, strong static typing for the web, fixing the independence mismatch between client/server/db etc. in 2009, and although we were not able to make it a big success, I'm still spending all my time in this area and am convinced that there is a lot to fix.
Please can you make your update PIN flow a bit different to your view PIN flow ta? If you are developing an app it's nice to be able to confirm that someone has got their OTC correct before they move to setting their PIN - so perhaps give us an ephemeral key for updating PIN we can use to do this as opposed to it being a one step process
Thanks for all that you, John and Stripe have done for startups. Question for you, how will you continue to remain focused on helping startups if/when you go public and have shareholders to appease?
Hi Pat. Do you have archives of the original /dev/payments around anywhere? The internet doesn't seem to have any and it would be great to see what Stripe version 0 looked like.
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 to build".) I always appreciate hearing from HN users (even if I don't always have time to respond): patrick@stripe.com.
For anyone thinking about what they should work on: I started building developer tools when I was 15 and "tools for creation" is still, IMO, one of the most interesting areas to work in.