#lconer-paymentintent
1 messages · Page 1 of 1 (latest)
it's the easiest way for me to work with existing system, I'm creating a PI for option A and need to update it when user change selected option to option B. Update will happen with API call
What do you mean by Option A and B? And the update API call is done on the backenend I suppose?
I'm charging a user for a service, and that service can have two prices: A and B, A is preselected by default and PI is created for that price. When user selects price B I will update PI with new price and refresh frontend Payment element (that's the plan advice by other stripe moderator).
I think it should be okay to expose the PaymentIntent ID on the frontend.
For example, when using the Payment Element, Stripe does show the PaymentIntent ID in the query parameter of the return_url as shown here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment