#Sharvari96

1 messages · Page 1 of 1 (latest)

spark spruceBOT
indigo prairie
sage quest
#

oh, ok...

indigo prairie
#

What's the specific issue that makes you need a pi_xxx on session creation?

sage quest
#

well, I need to tracker either session id or payment intent id on our application to update data based on events in webhook.

I currently have these two flows:

  • payment using invoice.
  • payment using checkout sessions.

it would be simpler to track payment intent for both have common logic, instead of having to track sessionID for one and paymentIntent for another...
nothing as a blocker, it just become more complex

#

its alright, I will try to handle it seperately

#

also because payment_intent.processing is triggered in both the cases...

#

hope that wasn't confusing

indigo prairie
#

Sorry, wasn't sure if there was a question there?

sage quest
#

did you get why I need pi_xxx on session creation?

#

it was a reply to the question

indigo prairie
#

Yeah, but then you said you'd handle it separately

#

I mean you can rollback your API version to predate the change if you prefer (not really recommended). I assume it used to work this way for you

sage quest
#

oh, ok. its alright, will handle seperately