3 ms·
Before stripe, I used paypal and it was sooo painful! There are so many terrible APIs out there that waste so much time needlessly. Then I found stripe. What
by thorwasdfasdf 7y ago
Before stripe, I used paypal and it was sooo painful! There are so many terrible APIs out there that waste so much time needlessly.
Then I found stripe. What a treat. Everything was documented and the documentation itself was both readable and didn't go in endless circles like the paypal ones. The error messages were helpful. And every api endpoint had an example, which is hugely helpful: HUGELY! All the other API developers out there can learn from this: you can't underestimate the value of having a working example. Not only that but the testing is much easier in stripe, and there's no need for a bunch of seperate accounts and sandboxes that don't make sense.
Oh and did I mention that the variables describe themselves: the first 3 or 4 letter of an ID says what it is (subscription or etc). Genius! It's little things like this which make Stripe stand out orders of magnitude above the rest of all the APIs in the world.
I hope you guys rule the marketplace for payment processing and wish you all the success you deserve.
Stripe's success in payment processing sends a clear signal to the Paypals and API developers of world: If you're producing an API that sucks, it creates an opportunity for someone else to come eat your lunch. :)
- adventured 7y ago> Before stripe, I used paypal and it was sooo painful! Almost no matter what Stripe does from here, that they disrupted the PayPal monster (and the rest), will always reserve them a place in my developer heart. It really was an atrocious experience; there's pre-Stripe and post-Stripe.
- forgot-my-pw 7y agoI wonder if that's the reason they launched Braintree with a more sane API. Nevermind, Braintree was acquired by Paypal in 2013.
- enahs-sf 7y agoI definitely consider stripe to be the canonical example when it comes to both API and documentation design. Really an excellent benchmark and point of reference for anyone who's making a published API.
- theturtletalks 7y agoPaypal also came out and said they will no longer refund seller fees when a customer is refunded. Before, they used to just keep the $0.30, but now they will keep the 2.9% as well. More the reason to switch to a new processor like Stripe.
- theunixbeard 7y agoStripe keeps your 2.9% also [1]. > Stripe supports the ability to refund charges made to your account, either in whole or in part. If the original charge underwent currency conversion, the refunded amount is converted back using the same process. There are no fees to refund a charge, but the fees from the original charge are not returned. [1]: https://stripe.com/docs/refunds https://stripe.com/docs/refunds
- nickjj 7y ago> More the reason to switch to a new processor like Stripe. For a lot of merchants it's not a matter of switching to Stripe. It's using Stripe but also including PayPal as an option because a huge percentage of buyers want to use it to pay for things -- especially 1 time purchases of digital goods. About 40% of my course sales are through PayPal. By the way if anyone reading is curious, that new PayPal refund policy goes into effect October 11th 2019 (you probably got the User Agreement email to notify you of this too if you're a merchant).
- aloknnikhil 7y agoI know Stripe is in beta in India, but I don't see any other alternative better than PayPal. Or is there something?
- anandchowdhary 7y ago> Or is there something? Razorpay. It’s also a YC company. I think of it as essentially an India-focused Stripe clone, with UPI, netbanking, etc.
- aloknnikhil 7y agoThat's awesome! Thanks.