#si_best-practices
1 messages ยท Page 1 of 1 (latest)
๐ 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/1285940521977778258
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there!
Additionally, it looks like in the at least typescript types for the stripe sdk, when I supply fixed_amount.currency_options it still expectsfixed_amount.currency and fixed_amount.amount, which seems like it's a bit clashing?
hi!
PI but it looks like I have to either create a
shipping_options.shipping_rate_datafor each possible destination
not really. you cannot create a shipping rate for a specific destination. once a shipping rate is created, it applies to all destinations.
if you want more control over this, you might want to provide an UI for this before redirecting users to the Checkout Session.
aha, so i should capture beforehand where the customer wants it shipped to?
and then the currency options is to just allow us to mainly capture currency conversion costs i guess?
correct
Additionally, it looks like in the at least typescript types for the stripe sdk, when I supply fixed_amount.currency_options it still expectsfixed_amount.currency and fixed_amount.amount, which seems like it's a bit clashing?
to me it makes sense to have a "default price", and then additional currencies. it works the same when creating Price objects: https://docs.stripe.com/api/prices/create?lang=node
Yeah it makes more sense to me if itโs not to capture final shipping destinations. Thanks!
happy to help ๐