#vincent_multiple-elements-fraud-detection
unreal duneBOT
👋 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/1329508459107975169
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- vincent_react-update-elements, 16 minutes ago, 23 messages
mossy citrus
hello again my old friend
deft cobalt
Hi 👋
The issue you can run into with creating multiple <Elements> instances is that all actions and web elements created by one instance of <Elements> can only be handled by that instance.
If you create a Payment Element within one <Elements> provider but tried to confirm the payment with another, that would fail
mossy citrus
if they would never be rendered simultaneously, then it should be okay?
deft cobalt
IT's a little harder to wrap my mind around with React but it's pretty straightforward with vanilla JS where you can do const elements = stripe.elements() multiple times
But yes, if you are only ever rendering one or the other, that should be fine
mossy citrus
one checkout experience is in a flyout sidebar that follows you around, that only has teh express checkout, then there is the checkout page
so i will wrap the checkout page and the flyout sidebar
deft cobalt
As long as all the "checkout" options are handled entirely within those separate components, then I think you should be fine
mossy citrus
no sidebar on the checkout page
hell yeah
thank you again for your help
ah, so fraud prevention
am i missing out on that if the reset of the website is not wrapped?
deft cobalt
Well it means we won't be able to track the customer activity on the parts of your site that aren't wrapped so it does reduce the input we get to detect bots.
But I think we should still notice if elements of your website are being activated and toggled with zero mouse movement or the occasional missed keystroke
mossy citrus
i see
good to know
i will discuss with the rest of my team and get back to you if we have more questions.
deft cobalt
Okay cool 😎