4 ms·

I've noticed Stripe products tend to be buggy and/or half-finished. What's the deal with that? Anyone know why a company with so much talent and great product t

I've noticed Stripe products tend to be buggy and/or half-finished. What's the deal with that? Anyone know why a company with so much talent and great product that seem polished seem to have critical issues?

gjsman-1000 5y ago
I thought I was crazy looking at their API and thinking it was crap because everyone seems to praise the Stripe API. I ran into undocumented sections around line items for Checkout objects, and the whole loop-around to go from Checkout Session -> Payment Intent -> Charge Information -> Order Information -> Line Items (or whatever order the 4 separate, synchronous requests our app has to do to get cart line items) is overly complicated. Like, why do we even need Payment Intent? I just want to make a Checkout session, set a few variables, and have it return whether the same Checkout session was successful or not, how much was charged, and the line items for it in one request, not four, five if unoptimized.
- wnevets 5y ago
  > Like, why do we even need Payment Intent? Could be to support payment methods in Europe and countries other than the US?
  - gjsman-1000 5y ago
    I am referring here to Stripe Checkout. https://stripe.com/payments/checkout https://stripe.com/payments/checkout It's supposed to make payments easier with a Stripe-hosted payments page. However, creating a server-side Checkout session, and then getting line items from an order, is an unnecessarily convoluted series of requests.
    - WillPostForFood 5y ago
      You can use "expand" to get multiple queries into a single request, kind of like a SQL join. I don't know if this is exactly your use case, but when we get a Checkout session, and want the customer and purchase line items, it looks like this (using the Stripe Ruby library). Stripe::Checkout::Session.retrieve({ id: session_id, expand: ['line_items', 'customer'] })

gjsman-1000 5y ago

I thought I was crazy looking at their API and thinking it was crap because everyone seems to praise the Stripe API. I ran into undocumented sections around line items for Checkout objects, and the whole loop-around to go from Checkout Session -> Payment Intent -> Charge Information -> Order Information -> Line Items (or whatever order the 4 separate, synchronous requests our app has to do to get cart line items) is overly complicated. Like, why do we even need Payment Intent? I just want to make a Checkout session, set a few variables, and have it return whether the same Checkout session was successful or not, how much was charged, and the line items for it in one request, not four, five if unoptimized.

wnevets 5y ago
> Like, why do we even need Payment Intent? Could be to support payment methods in Europe and countries other than the US?
- gjsman-1000 5y ago
  I am referring here to Stripe Checkout. https://stripe.com/payments/checkout https://stripe.com/payments/checkout It's supposed to make payments easier with a Stripe-hosted payments page. However, creating a server-side Checkout session, and then getting line items from an order, is an unnecessarily convoluted series of requests.
  - WillPostForFood 5y ago
    You can use "expand" to get multiple queries into a single request, kind of like a SQL join. I don't know if this is exactly your use case, but when we get a Checkout session, and want the customer and purchase line items, it looks like this (using the Stripe Ruby library). Stripe::Checkout::Session.retrieve({ id: session_id, expand: ['line_items', 'customer'] })