#mahad852-PI
rapid sluice
You have contact with stripe?
copper smelt
correction: the payment intent confirmation has the "requires_action" status. which is well and good, but the payment intents activity still states "3D secure succeeded"
rapid sluice
How do i do that
hushed sky
@rapid sluice please refrain from stepping into other threads
@copper smelt let me take a look
copper smelt
hey @hushed sky, found anything?
hushed sky
I'm still trying to dig into this
copper smelt
Alright, thanks!
hushed sky
could you please describe how you are implementing this please?
on the client-side that is
copper smelt
ah okay
so basically when a user tries to purchase a product, we make a call to our server to create a payment intent for the purchase. The server, after creating the payment intent returns the intents client secret. We then use this client secret to create a stripe.js payment element to collect payment details from the customer. At the end, we send a request via stripe.js API to stripe to confirm the payment intent via the details collected using the payment element
we do also have saved cards, in which case the process is similar other than that a payment element is NOT initialized and instead the client secret is used for payment confirmation
deft sigil
Yeah this is seemingly a decline code from the bank/issuer for the payment that we currently flag as an auth request. In reality its just a generic decline
Which can happen: 3DS can be requested, succeed and then the bank will decline it regardless of 3DS outcome for other reasons
copper smelt
ohh, so we dont need to worry about this?
we were wondering if there was something wrong on our end
deft sigil
Nope! Nothing seems wrong with your integration
Just be sure to handle those decline errors accordingly
copper smelt
alright! thanks a lot!