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.
I completely agree - I consider Stripe the gold standard for an API. Best I've ever used.
At least you get some cash back from expenses.
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 was able to accept donations in all the ways I wanted:
- using Netlify (free hosting, includes lambda)
- custom amounts
- one-time payment or recurring
- form on my own site
code is here:https://github.com/revddit/revddit/blob/master/lambda-src/do...
https://github.com/revddit/revddit/blob/master/src/pages/com...
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.
I documented how I implemented Stripe for the SaaS I run quite extensively at https://blog.checklyhq.com/our-stripe-billing-implementation...
The distinction between high risk consumer sales & B2B low risk sales is not drawn by 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?
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.
SignalWire too should be able to use 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."
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.
Thank you for the t-shirt and the most enjoyable ctf I had a chance to play!
I love the copy on Stripe's website. Who wrote it?
Godspeed.
It's not available at Stripe's home page. Would you mind sharing it? Thx
So yes, it is available on the home page - it's the most important thing there!
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
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?
The problem is with their libraries, sandbox and testing tools. Also, their support is a complete and utter clusterfuck.
But the API is OK.
Can't wait for Stripe to integrate PayPal as one of the options. Seems unlikely to happen, but I keep my fingers crossed.
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.
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): [email protected].
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.