#Alex Iglesias
1 messages ยท Page 1 of 1 (latest)
๐ happy to help
would you mind sharing the request ID?
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Thanks! Yes, of course: req_wWAJyO7Ttrg8JF
I'm working with PHP and I'm following this documentation: https://stripe.com/docs/api/checkout/sessions/object#checkout_session_object-line_items-data-price-tax_behavior
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
taking a look
when you specify a price the tax_behavior should be configured on the price itself
price_data is used to create on-the-go prices
Yes, I also tried that, but then, where I put the price ID (ex. price_1LsV0EFby9V9SaNDxh287lru)?
I just have done a test, could you take a look? I added id inside of price object.
req_4OwYywehh4nNEc
that's not what I meant when I said "tax_behavior should be configured on the price itself", I meant you need to update the price and change it's tax_behavior
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
If I got you well, should I update the price right after to create the session?
Like this?
no you need to update the price regardless of the session
and prior to creating the new checkout session
Okay, done!
But now the logs throw me the following: You cannot update tax_behavior field once it has been specified.
Why is that?
ID: req_X3Y5SC5eJHft6b
you don't have to do the price update each time
this is done once
the red box code shouldn't be part of the "checkout creation workflow"
Ohh, I get you. It has to be executed only once to change the price properties. That's all. I get you.
But well, it is not even executed once and I don't know does it means that error in the logs (You cannot update tax_behavior field once it has been specified)
maybe you have already specified the behavior on creation
once the tax_behavior is set you can't change it
Ok, to change it I have to remove the price and create another one, right?
What happens if someone is using the product (subscription for example) associated with that price? If I remove the price to create a new one, will the customer lose the subscription?
Ok, to change it I have to remove the price and create another one, right?
correct
What happens if someone is using the product (subscription for example) associated with that price? If I remove the price to create a new one, will the customer lose the subscription?
even after you "soft" delete the price it will still be used for ongoing subscriptions
the price will be archived
and can't be used in new sessions
Good! Thank you for all! You can finish this ticket. Have a good day