4 ms·

Thanks! We still have a lot of work to do. (Making our integration experience simpler -- now that Stripe's functionality has grown so much -- is an area of curr

by pc 7y ago

Thanks! We still have a lot of work to do. (Making our integration experience simpler -- now that Stripe's functionality has grown so much -- is an area of current focus. If any HN readers happen to have specific suggestions on this front, feel free to email sebas@stripe.com.)

davedx 7y ago
One thing I loved recently was finding a small error in your nodejs docs. I tweeted you and had a response within an hour or two that it would be fixed. Please keep listening like this, it’s greatly appreciated!
eganist 7y ago
Hey, from a security angle, can I express my appreciation for how much your team has worked to make security best practices and shared responsibility extremely clear? https://stripe.com/docs/security https://stripe.com/docs/security Apologies for the hijack, just wanted to say thanks.
simlevesque 7y ago
The best part is that you guys keep the logs for the last events and webhooks you sent with the request and response... this is such a time saver that I can't figure out why you are the only big players doing it.
jchw 7y ago
Honestly, the only problem I ran into with Stripe ever was administrating subscriptions. IIRC even via the API there were a lot of limitations with what state you could put a subscription in, limiting our ability to seamlessly transition from Recurly to Stripe; we ended up duplicating a lot of the subscription logic in the end. I know subscriptions have been significantly rehauled since then, but this was my only gripe. Stripe was absolutely excellent back when I used it.
- kwindla 7y ago
  I think subscriptions are complicated because the surface area of the problem is so large. The Stripe Billing APIs (the recurring revenue/subscriptions part of Stripe) have gotten very good. But the challenges involved in the average subscription implementation are a lot bigger than the challenges involved in implementing simple checkout workflows for non-recurring charges. We wrote a blog post detailing our Stripe Billing implementation: https://www.daily.co/blog/implementing-api-billing-with-stripe https://www.daily.co/blog/implementing-api-billing-with-stri...
markdown 7y ago
FYI while you're here: Your search is broken: https://support.stripe.com/search?q=Countries https://support.stripe.com/search?q=Countries
- dylanvee 7y ago
  Thanks for flagging! We've got a massive search overhaul in the works that will start rolling out in the next week or so. Feel free to get in touch at dylan@stripe.com if you'd like to give it an early spin when it's ready. (Our new search presents this as a result for your query, in case it's what you were looking for: https://support.stripe.com/questions/stripe-feature-availability-by-country https://support.stripe.com/questions/stripe-feature-availabi...)
  - ElCapitanMarkla 7y ago
    Hey in terms of search, one issue I've had a few times now is the inability to find things in certain sections of the docs because of the way everything is presented on a single page. e.g. just now I'm implementing webhook handling for subscriptions. So I drill down to the section that lists all the events - https://stripe.com/docs/api/events/types https://stripe.com/docs/api/events/types this is massive and I don't want to read everything, so I cmd+f to find "subscription"... oh stripes taken over my default search but no worries I can hit cmd+f again and use the browsers search... I type "sub"... now the page has jumped way up to https://stripe.com/docs/api/expanding_objects.. https://stripe.com/docs/api/expanding_objects... ffuuuuu...
Androider 7y ago
I love the backwards compatibility that Stripe provides. Thank you so much! We launched a SaaS product on the 2016-03 API version. Since then[1] the API has basically changed completely around subscriptions (even the top-level objects aren't called the same anymore), to the point it would probably be easiest to just start a rewrite from scratch (which probably would take a week or two). But the fact that the old API continues to work to this day and that we have been able to rely on it and focus on other things has been amazing. New customers get to enjoy the new API while our business continues to chug along with zero modifications to the payment parts. That is impressive from both a technical and from a business point of view, and ensures we will keep using Stripe forever. [1] Stripe provides a very detailed and customized API upgrade guide based on your current API usage https://stripe.com/docs/upgrades?since=2016-03-07#how-can-i-upgrade-my-api https://stripe.com/docs/upgrades?since=2016-03-07#how-can-i-...
- malingo 7y ago
  They had a great blog post on how they manage API versioning a couple years ago: https://stripe.com/blog/api-versioning https://stripe.com/blog/api-versioning
twakefield 7y ago
I'm surprised Quickbooks Online is not listed here [0]. I'm guessing they are the blocker here? I have fallen back on using Zapier but the sync often breaks. Native integration would be preferred. [0] https://stripe.com/partners/apps-and-extensions/accounting https://stripe.com/partners/apps-and-extensions/accounting
wkoszek 7y ago
If you guys could make your docs available for offline/downloadable reading in apps like Dash, it'd be amazing. There's a fundraiser to do it: https://github.com/Kapeli/Dash-User-Contributions/issues/2014 https://github.com/Kapeli/Dash-User-Contributions/issues/201... but this project would be much easier to do by someone inside of Stripe.

by pc 7y ago

davedx 7y ago

One thing I loved recently was finding a small error in your nodejs docs. I tweeted you and had a response within an hour or two that it would be fixed. Please keep listening like this, it’s greatly appreciated!

eganist 7y ago

Hey, from a security angle, can I express my appreciation for how much your team has worked to make security best practices and shared responsibility extremely clear? https://stripe.com/docs/security https://stripe.com/docs/security Apologies for the hijack, just wanted to say thanks.

simlevesque 7y ago

The best part is that you guys keep the logs for the last events and webhooks you sent with the request and response... this is such a time saver that I can't figure out why you are the only big players doing it.

jchw 7y ago

Honestly, the only problem I ran into with Stripe ever was administrating subscriptions. IIRC even via the API there were a lot of limitations with what state you could put a subscription in, limiting our ability to seamlessly transition from Recurly to Stripe; we ended up duplicating a lot of the subscription logic in the end. I know subscriptions have been significantly rehauled since then, but this was my only gripe. Stripe was absolutely excellent back when I used it.

kwindla 7y ago
I think subscriptions are complicated because the surface area of the problem is so large. The Stripe Billing APIs (the recurring revenue/subscriptions part of Stripe) have gotten very good. But the challenges involved in the average subscription implementation are a lot bigger than the challenges involved in implementing simple checkout workflows for non-recurring charges. We wrote a blog post detailing our Stripe Billing implementation: https://www.daily.co/blog/implementing-api-billing-with-stripe https://www.daily.co/blog/implementing-api-billing-with-stri...

markdown 7y ago

FYI while you're here: Your search is broken: https://support.stripe.com/search?q=Countries https://support.stripe.com/search?q=Countries

dylanvee 7y ago
Thanks for flagging! We've got a massive search overhaul in the works that will start rolling out in the next week or so. Feel free to get in touch at dylan@stripe.com if you'd like to give it an early spin when it's ready. (Our new search presents this as a result for your query, in case it's what you were looking for: https://support.stripe.com/questions/stripe-feature-availability-by-country https://support.stripe.com/questions/stripe-feature-availabi...)
- ElCapitanMarkla 7y ago
  Hey in terms of search, one issue I've had a few times now is the inability to find things in certain sections of the docs because of the way everything is presented on a single page. e.g. just now I'm implementing webhook handling for subscriptions. So I drill down to the section that lists all the events - https://stripe.com/docs/api/events/types https://stripe.com/docs/api/events/types this is massive and I don't want to read everything, so I cmd+f to find "subscription"... oh stripes taken over my default search but no worries I can hit cmd+f again and use the browsers search... I type "sub"... now the page has jumped way up to https://stripe.com/docs/api/expanding_objects.. https://stripe.com/docs/api/expanding_objects... ffuuuuu...

Androider 7y ago

I love the backwards compatibility that Stripe provides. Thank you so much! We launched a SaaS product on the 2016-03 API version. Since then[1] the API has basically changed completely around subscriptions (even the top-level objects aren't called the same anymore), to the point it would probably be easiest to just start a rewrite from scratch (which probably would take a week or two). But the fact that the old API continues to work to this day and that we have been able to rely on it and focus on other things has been amazing. New customers get to enjoy the new API while our business continues to chug along with zero modifications to the payment parts. That is impressive from both a technical and from a business point of view, and ensures we will keep using Stripe forever. [1] Stripe provides a very detailed and customized API upgrade guide based on your current API usage https://stripe.com/docs/upgrades?since=2016-03-07#how-can-i-upgrade-my-api https://stripe.com/docs/upgrades?since=2016-03-07#how-can-i-...

malingo 7y ago
They had a great blog post on how they manage API versioning a couple years ago: https://stripe.com/blog/api-versioning https://stripe.com/blog/api-versioning

twakefield 7y ago

I'm surprised Quickbooks Online is not listed here [0]. I'm guessing they are the blocker here? I have fallen back on using Zapier but the sync often breaks. Native integration would be preferred. [0] https://stripe.com/partners/apps-and-extensions/accounting https://stripe.com/partners/apps-and-extensions/accounting

wkoszek 7y ago

If you guys could make your docs available for offline/downloadable reading in apps like Dash, it'd be amazing. There's a fundraiser to do it: https://github.com/Kapeli/Dash-User-Contributions/issues/2014 https://github.com/Kapeli/Dash-User-Contributions/issues/201... but this project would be much easier to do by someone inside of Stripe.