3 ms·

Wow, Stripe is the best developer experience? When I integrated a few months ago their documentation was so confusing I ended up giving up and not using it at a

Wow, Stripe is the best developer experience? When I integrated a few months ago their documentation was so confusing I ended up giving up and not using it at all, relying on using a library for laborious guess and check, and watching the JSON responses. I suspect my product can still be purchased for free if you use that EU security feature because nothing could help me figure out when I need to use it or how to do so, so it just looks like the payment succeeded. So much documentation recommends you use a totally different system I felt like I was caught in a loop.

nemothekid 7y ago
Your experience isn’t invalid, but it’s by and far the best developer experience compared to everyone else. Stripe was “bleeding edge” in their desicion to use JSON when I first integrated with them which was a hell of a lot easier than integrating with PayPal’s SOAP API
NicoJuicy 7y ago
Euh, you are talking about EU security features? So, if(IsInEurope(Customer.Country) || IpAnalyzer.IsInEurope(visitor.Ip)) { //Enable something } Should do it. But fallback method should be implemented, took me 3 minutes of reading documentation + googling. Between all those tax regulation differences, I think this one is mostly straightforward for handling global payments. Ps. Don't forget to encrypt your actual data, I think you will be amazed at what needs to happen for selling in EU ;)
- hawkice 7y ago
  Nah there's some credit card security thing in the EU they talk about in the Stripe API. No comprehension of what it is, but I'm not talking about GDPR or anything, just weird credit cards.
  - NicoJuicy 7y ago
    GDPR, I think, is the root cause for the more complex PSD2 flow. https://www.insideprivacy.com/financial-institutions/overlap-between-the-gdpr-and-psd2/ https://www.insideprivacy.com/financial-institutions/overlap...
- shaneprrlt 7y ago
  Or just extend the same privacy protections to all your users globally and implement the same functionality once. Honestly, the PaymentIntent API is not difficult to wrap your mind around when you dive into the documentation, and it has you covered on 3D secure payments.
mcpeepants 7y ago
I thought the Payment Intents and associated information about SCA had a learning curve, but was well documented. I think the aspect you're missing is that you don't need to decide, necessarily, when to use Payment Intents. You use only that API, and if there's an additional step required on the user's end, you'll get a different "state" in the response https://stripe.com/docs/payments/intents https://stripe.com/docs/payments/intents

nemothekid 7y ago

Your experience isn’t invalid, but it’s by and far the best developer experience compared to everyone else. Stripe was “bleeding edge” in their desicion to use JSON when I first integrated with them which was a hell of a lot easier than integrating with PayPal’s SOAP API

NicoJuicy 7y ago

Euh, you are talking about EU security features? So, if(IsInEurope(Customer.Country) || IpAnalyzer.IsInEurope(visitor.Ip)) { //Enable something } Should do it. But fallback method should be implemented, took me 3 minutes of reading documentation + googling. Between all those tax regulation differences, I think this one is mostly straightforward for handling global payments. Ps. Don't forget to encrypt your actual data, I think you will be amazed at what needs to happen for selling in EU ;)

hawkice 7y ago
Nah there's some credit card security thing in the EU they talk about in the Stripe API. No comprehension of what it is, but I'm not talking about GDPR or anything, just weird credit cards.
- NicoJuicy 7y ago
  GDPR, I think, is the root cause for the more complex PSD2 flow. https://www.insideprivacy.com/financial-institutions/overlap-between-the-gdpr-and-psd2/ https://www.insideprivacy.com/financial-institutions/overlap...
shaneprrlt 7y ago
Or just extend the same privacy protections to all your users globally and implement the same functionality once. Honestly, the PaymentIntent API is not difficult to wrap your mind around when you dive into the documentation, and it has you covered on 3D secure payments.

mcpeepants 7y ago

I thought the Payment Intents and associated information about SCA had a learning curve, but was well documented. I think the aspect you're missing is that you don't need to decide, necessarily, when to use Payment Intents. You use only that API, and if there's an additional step required on the user's end, you'll get a different "state" in the response https://stripe.com/docs/payments/intents https://stripe.com/docs/payments/intents