#damonzucconi-elements

1 messages · Page 1 of 1 (latest)

shut cobaltBOT
#

Hello! We'll be with you shortly. 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.

lavish siren
#

No, right now there isn't a way to update the elements provider with a client secret - can you give me some details/context on why you want to do this?

shut cobaltBOT
#

damonzucconi-elements

gray sequoia
#

oh sure, so ive got a stepped form, i need to do some things after i get the clientsecret, if i key the provider it just resets the state, so not good

#

seems like this would be a pretty basic use-case

#

i mean just at it's most basic:

  const intent = await setupPaymentIntent();

  const res = await stripe.confirmCardPayment(intent.clientSecret, {
    payment_method: me.customer.default_payment_method.id,
  });
#

well ok i guess in this case i don't really need it

#

sigh

#

ill figure something out but a question:

lavish siren
#

Yeah backing up for a second here - if you aren't using the Payment Element there's really no reason for you to be setting the client secret when you initialize elements

gray sequoia
#

i mean the reason is that in some instances i AM using the element

#

if you already have a payment method attached though i dont need it so like i just need to branch here

#

but anyway my question is

#

do you get way more support questions with the client secret stuff now?

#

🙂

#

like having to revisit my integrations here i can't help but notice that it's much more complicated

lavish siren
gray sequoia
#

ah interesting