#bono_docs

1 messages ยท Page 1 of 1 (latest)

wispy forgeBOT
#

๐Ÿ‘‹ 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/1445349908264783883

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

molten slate
#

๐Ÿ‘‹ Hi there! Let me take a look

storm prairie
#

Hi. Thanks for your time ๐Ÿ‘‹
Is there a way for us to identify this within the FE without reaching for BE to retrieve the charge object?

wispy forgeBOT
storm prairie
#

Perhaps I should elaborate more on what I am expecting

Before the payment intent or the charge is captured or fulfilled, is there an internal indication that is accessible for us to use to identify whether the 3DS challenge popped up or will be popped up or something along that line

proud hazel
#

I'm assuming your integration just calls the confirmPayment function from Stripe.js once customer has entered their payment details?

storm prairie
#

yes, we make use of Stripe Elements and go through elements.submit() and stripe.confirmPayment()

proud hazel
#

got it. there's nothing really in Stripe.js for the info you want. it is sort of possible with confirmCardPayment in that you can set handleActions: false and then you can infer from the response whether 3DS was requested

storm prairie
#

I havent seen any callback available from the doc regarding this from elements nor stripe, and was inspecting whether elements already knows of this status before it calls confirmPayment

proud hazel
#

confirmPayment only resolves after the 3DS challenge flow is complete, be that successfully or not

storm prairie
#

so I am guessing confirmPayment internally calls confirmCardPayment with its respective presets and resolves the confirmPayment layer? Is that correct?

proud hazel
#

not really, no

#

not really sure why that matters

#

confirmCardPayment can't be used with the Payment Element so it's irrelevant in your use case

storm prairie
#

I see

#

so it is not possible to acquire this info at this point in FE using Payment Element

proud hazel
#

it's not no