#dale_best-practices
median auroraBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1268425804145229897
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
humble portal
In case it's still not clear, my customer starts from creating the organizational unit by giving it name, description and other stuff not related to payment. Then, the customer needs to fill billing information and payment information. Then, the customer needs to configure the number of hosting plans he wants (i.e. starter plan x2, pro plan x4). And, at this step, I would like to provide "order summary" for the customer, as he is configuring the subscription/plans.
I'm unsure if this whole idea is best-practice, to be honest. It's my first time using Stripe, as well. 🙂
cunning tiger
Thanks for waiting!
Payment Element with Payment Intent only collect the final amount computed. It doesn't support automatic tax and discount directly.
Automatic tax and discounts are only supported in Checkout Session in both embedded and hosted versions. The automatic tax and discounts calculation depend on the information that the customer fills in in the Checkout Session itself, which is after the order summary at the point of payment collection
humble portal
Okay. Thank you for quick answer! So, what do you suggest? Customer fills organizational unit data, then configure the plans, then show embedded checkout? Or I can implement my own order summary, but without tax obviously?