#CamperCat-3DS
1 messages · Page 1 of 1 (latest)
heya @pallid snow! i think you're looking for a test card that requires 3DS? If so, you'd want to refer to this page : https://stripe.com/docs/testing#regulatory-cards
Hey thanks for your answer. I am using a test card and the status of the paymentIntent also says that I need to do the 3D Secure. But how can I do it?
if you're using Payment Elements, it'd automatically display the pop up if 3DS is required : https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure
is it even possible with it ?
it should be, you can look for tutorials/samples online on how to implement it
The docs are not that big. We tried much, the documentations says "SCA-Ready: The SDK automatically performs native 3D Secure authentication if needed to comply with Strong Customer Authentication regulation in Europe."
The thing is that we want to pay with an existing card on the customer account. But when we try to confirm the payment in the app it needs card details. Where is the sense behind that ? If we understood right the "ClientSecret" is for confirming the payment.
Hey there! Just catching up here. Can you share some more details of your integration?
The Flutter library isn't an official library, we can offer limited support here
Ah okay I thought it is.
The integration is as followed:
- Creating Customer Account backend with paymentMethod
- App is confirming setupIntent
- App trys to buy sending request to the backend
- Backend creates a paymentIntent
- Backend returns clientSecretKey
- App trys to confirm payment but we fail
Can you share the ID of a failing Payment Intent?
We think this is the right method for confirming the paymentIntent but it needs card details. But we don't want to fetch the card details for every payment from our customers
yeah one moment
pi_3JvopeBMbWm4jDkM1HLlBCxd
Thanks, let's see what's going on!
Seems you're using the tokens endpoint to create the payment method, which don't support 3DS flows: https://stripe.com/docs/payments/payment-methods/transitioning
Oh yeah I think the method i posted above is the wrong one. The naming is not good. "confirmPayment" its not confirming the payment its creating a paymentMethod
But its okay if you guys don't support this package I fully understand that you can't help me with the implementation. Thanks for your answer and your help. We will try to get this working