#martin-gaibisso_error
magic baneBOT
👋 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/1229797227720085566
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rose ventureBOT
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.
- martin-gaibisso_error, 6 days ago, 7 messages
formal pollen
Hi 👋 that error usually indicates that different values were provided for setup_future_usage when setting up Stripe Elements and creating the intent. Where are you currently setting setup_future_usage to off_session?
formal pollen
No, you should probably add it when initializing stripe.js. Just making sure though, you're using a flow like the one described here, where you create the intent last after rendering the Payment Element?
https://docs.stripe.com/payments/accept-a-payment-deferred
worldly plaza
correct
formal pollen
Perfect, then you'll also want to set setupFutureUsage, and any other options you're leveraging, when initializing Elements:
https://docs.stripe.com/js/elements_object/create_without_intent#stripe_elements_no_intent-options-setupFutureUsage