#learner-confirmsetup

1 messages · Page 1 of 1 (latest)

idle thistle
fierce obsidian
#

Got it. Thank you. I think this should be specified in the Docs as well

#

Or is it already specified and I missed it?

idle thistle
#

The Payment Element is mentioned in that doc, yes

fierce obsidian
#

I mean when we we use CardNumberElement instead of PaymentElement - it seems this use case is not documented in this guide and is also a common use case?

idle thistle
#

Most of our guides/docs have been re-written to use Payment Element now (it's the recommended integration path)

fierce obsidian
#

Thank you. Kind feedback. A small note in the documentation for same will still help

#

@idle thistle how should we handle this error response type? By creating a new SetupIntent or something else?

idle thistle
#

Can you paste that id for me please?

fierce obsidian
#

you mean setup_intent.id ? it's "seti_1K1sIcSCTc5Q7Oo30WLweq7z"

idle thistle
fierce obsidian
#

which code in the response would suggest that setup intent is already confirmed and we would need to create a new setup intent?

idle thistle
#

The status: 'succeeded' field

fierce obsidian
#

ok, what are the other possible error use cases? Would need to handle them in client code

idle thistle
#

The doc_url field will help you

#

What specifically do you need to handle?

#

You can localise the Stripe.js error if that's what you mean?

fierce obsidian
#

What specifically do you need to handle?
All error scenarios for stripe.confirmCardSetup

#

One scenario I understood is when the Payment Intent has already been created and we need to create a new one

idle thistle
#

Right, but we handle that for you. Why do you need to account for every error variant

#

You'd just have a catch block to handle them all