#Austin_Truthifi
plucky granite
Hi there 👋 can you point me to the guide that you're following so I can take a closer look at what you're referring to?
solemn lightBOT
plucky granite
Thank you for that clarification!
I'm not the most familiar with React, so please let me know if this doesn't work out, but I believe you should ensure whatever elements will rely on Elements to be wrapped by the provider.
We also have a newer flow that allows you to create and render a Payment Element without first creating a Payment Intent, removing the need to provide a client_secret up front. This guide walks through building that flow:
https://stripe.com/docs/payments/accept-a-payment-deferred
quasi garnet
I appreciate your help toby, but is there any chance you can patch someone in who's familiar w/ react?
cinder pike
👋 stepping in here
solemn lightBOT
cinder pike
Toby had to step away anyway so it works out
I'm familiar with React, let me take a look at your question above
quasi garnet
Awesome! Thanks
cinder pike
Yep so overall if you can use render the Elements Provider at the root then it allows Stripe to be accessible everywhere. That said, with our newer flows (like with Payment Element) which requires a client_secret up front it may not be reasonable to actually render this right at the root. Mostly my colleague hit on it perfectly -- ideally you render at the root but really you just need to wrap any of your Stripe stuff within the Elements Provider.
quasi garnet
I see, I figured I would need to wrap a little more closely, but just wanted to check! Thank you to you both!