#oleksandr_api
cinder anchorBOT
👋 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. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
🔗 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/1214889528008122448
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
dark nymphBOT
limber mountain
👋 happy to help
the client_reference_id you mentioned is only available for Checkout Sessions
and not with Payment Elements
weak granite
Hello, thank you for your response.
I was going to use the client_reference_id to share the order id with the program code that processes webhooks.
Is there something similar that Stripe Elements proposes for such stuff?
limber mountain
you can use metadata on the PaymentIntent if you like
weak granite
Can I get them from the webhook data then?
It seems like there is it: \Stripe\Checkout\Session::@$metadata
Right?