4 ms·
I guess this article sums up why we've had a rather bad experience with stripe so far: the API constantly changes, and the documentation or even Googling for a
by LeonM 6y ago
I guess this article sums up why we've had a rather bad experience with stripe so far: the API constantly changes, and the documentation or even Googling for a solution seems to be more confusing than ever since most articles you'll find are about some older API.
It initially took us much more engineering hours to integrate Stripe into our processes then expected. Granted, we do worldwide sales, with multiple tax-flows and we accept multiple payment methods in both euros and USD. This was during the Charges/Sources days.
Then this year we had to go through all that again to migrate from the Charges/Sources model to the PaymentIntent model. This was a pain as the popular payment method in our own country was still very much in beta for the PaymentIntent flow. Documentation was all over the place and customer service often did not know answers to implementation questions (though I must say, they always followed up eventually with some good pointers).
Now we are receiving scary emails about how much money we'll lose if we are not SCA compliant. But following the link in that email shows we are SCA compliant... Confusing stuff. Let's just hope we don't have to go through a migration again.
Disclaimer: I don't have any meaningful experience with other payment providers, so a can't really tell if Stripe is better or worse than others. I guess accepting payments is just really hard if you want to do anything beyond the 'hello world' (which is: credit cards in the US only).
- mastre_ 6y ago> I guess this article sums up why we've had a rather bad experience with stripe so far: the API constantly changes, and the documentation or even Googling for a solution seems to be more confusing than ever since most articles you'll find are about some older API. Just a note, one of the things they got right with their API is versioning. Until you decide to upgrade to a newer version of their API, nothing changes for you, and you can test out compatibility in dev/staging by simply specifying a flag on each API call (which is easy to do if they all go thru a central class that handles the Stripe API calls for your app). Their changelog also takes a "from -> to" flag which will show you the exact changes that are between the version you're on and the latest (or any other). All in all, for this specific part of it, I wish more places handled evolving APIs the way Stripe does.
- novaleaf 6y agoagree on that. I haven't changed my stripe api calls in about 3 years, and everything is still working.