#MonkeyD.Luffy - 3DS
1 messages · Page 1 of 1 (latest)
hi there! Could you elaborate more? Do you mean you're already displaying the 3DS modal to the customer already and you're wondering if you need to confirm the payment after the user authenticates?
no you shouldn't need to do anything else after the user authenticates. But i suggest you try it out using our test cards in case you're doing something unusual which i'm not aware of : https://stripe.com/docs/testing#regulatory-cards
can you provide an example of what you mean by display T&C of stripe for saving card Info.?
what t&c would you like to display and where do you want to display it?
Yes. T&C of stripe while saving cards
I wanted to display when user chose to save card Info from checkout
if you're using the Payment Element, this is how it'll look like
this doesn't look like the Stripe Checkout page. Are you using a third party such as Shopify or Woocommerce?
Its not shopify we are devoloping one fashion site. we are using stripe as payment gateway
This is our checkout page. we wanted to display T&C for customer when he wants to save his card for future payments.
alright, if it's your own checkout page, then you can code the T&C in as necessary
adding in the T&C to your own website isn't dependent on Stripe.
Okay, Understand.
I am still facing an Issue with 3D secure payment here. Even though I attached the card to the customer and did authentication it's still returning the client_secrete_key to authenticate again.
can you share the PaymentIntent id?
ah okay, it's cause you're using confirmation_method=manual
is there a reason why you're using this parameter?
Yeah because for 3D cards for authentication purposes I am passing the client secret to the client side to authenticate. once authentication done they are calling back same API to complete payment
confirmation_method=manual requires you to use your secret key to confirm after each action. We generally don't recommend doing manual confirmation because :
- Manual confirmation requires more API calls, compared to our default flow.
- If a customer drops off (e.g. closes their browser) after completing authentication in a manual confirmation flow, that leaves the PaymentIntent in a status: requires_confirmation status. Your integration integration has no way of knowing about this as there are no webhooks to inform you of the PaymentIntent changing its status from status: requires_action → status: requires_confirmation.
- When a manually confirmed PaymentIntent is authenticated (i.e in status: requires_confirmation, there is a 1 hour duration within which the PaymentIntent has to be confirmed server-side, otherwise it expires and the PaymentIntent goes back into status: requires_payment_method.
- Only card payment methods properly support manual confirmation.
If you don't use confirmation_method=manual You can confirm via the frontend client instead of passing it to your backend server.
if you want to continue using confirmation_method=manual, then you can refer to this guide : https://stripe.com/docs/payments/accept-a-payment-synchronously. You can see after step 5 : where you handle authentication, you need to confirm again in step 6