#raffi23_docs
gritty wingBOT
đ 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/1238025072732536843
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
solid sparrow
The fixture of checkout.session.completed event is hard coded in Stripe CLI: https://github.com/stripe/stripe-cli/blob/master/pkg/fixtures/triggers/checkout.session.completed.json
The confirm amount is hard coded in 3000, which is different the price from price_1PEQLOL53dUV0i9Ynnm7ZnjU (2000 * 2 = 4000)
I'd recommending creating your own fixture for CLI by modifying from the default checkout.session.completed fixture: https://docs.stripe.com/cli/fixtures
last comet
oh I see thanks for the clarification.
I also have a different question regarding best practices,
Let's say i am selling x amount of products and a customer tries to checkout
should i create a draft order before starting stripe's checkout session or
send the product Ids as metadata of a string key for the id of the product and a number value for the quantity or
should i just use the items i get on the session?
solid sparrow
Any of them will work. I'd recommend creating an order in your system and give it an identifier. This order ID can then set under metadata, which you can retrieve the order information later
last comet
awesome thanks a lot mate, can i ask more questions in this thread in the future if I need to?