#Maher
stark briar
versed granite
pulsar ibex
Hey thanks !
this was the transaction tested in test mode
pi_3MjialCquaDiaULj1nniVsAe
which is similar to the issue happened in production with one of our clients with this trsnaction ID pi_3Mc5S3CquaDiaULj07btsVPo
reef hull
I see, and what exactly is the issue/question you have? On our end you have created this PaymentIntent normally on the server side. The next step is to confirm it on the client side to handle 3D Secure.
pulsar ibex
but we got an error it seems our payment form needs to be updated it is not accepting 3D secure
reef hull
your flow overall here is not the recommended one on Stripe(as you are collecting the raw card details on your backend server and calling our API yourself with them requiring your business to be PCI compliant)
reef hull
but we got an error it seems our payment form needs to be updated it is not acce...
yep! is there a guide overall you're using? If you use any of our documented Elements/Checkout solutions they all support 3D Secure natively https://stripe.com/docs/payments/accept-a-payment
so you should be using one of those approaches really.
pulsar ibex
this is our issue we didnt initially developed our checkout page using Elements we have used the customization method
not sure it was called Rest API
reef hull
yep, was there a reason you didn't use Elements?
if you're doing something custom it requires a lot more indepth knowledge and comfort understanding our API.
pulsar ibex
we needed to have a specific design for the checkout page
what do you suggest we can do in this case to solve this issue in the most appropriate way
reef hull
migrate to using the recommended/documented Elements or Checkout payment solutions
pulsar ibex
so we should change our checkout page to Elements