#niteeshvparticipant
1 messages · Page 1 of 1 (latest)
here only
Could you please share the PaymentIntent ID pi_xxx?
This PaymentIntent requires confirmation, have you tried confirming it?
What Stripe guide are you following?
actually for that particular test card only I am not getting 3DS modal ji ,for every card is working
is there any isssue with that particular test card ?
Perhaps this surface doesn't support 3DS(1), just 3DS2
is there any other "3DS Required" test cards
and how to support the 3DS, do you mean surface as app
Is this a Card Element or Payment Element?
But what happens exactly when you provide this card?
And again, what guide are you following?
I am not sure , It got setup before 4 years
I expected to show the 3DS authentication modal, but without the modal the payment got completed
What's the issue with this? Not all cards require 3DS.
Also, I would recommend updating your setup to the newest standard with Payment Element and PaymentIntents: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
This will allow you to turn on any new payment method types and simplify support in the future.
all are working fine... But I am afraid the particular card is not working...may be it can lead to issue if the app is live
If the payment is successful then it's working. That's the goal of the card, isn't it?
actually, In our app, if the card has 3DS we are not gonna allow those cards
Why?
I will check the reponse of confirm api , if it is like thee_d _secure I am blocking it
that is the requirement ji
so I am getting response for all cards as 3D secured in the next_action , but for this particular card , I am getting null as next_action and also the 3DS is not getting trigeegred
What you should look out for is status: "requires_action", this means that the card required 3DS.
no
What do you mean?
I am looking for next_action:null, If it is not null I am blocking it...In my app the next action only get value when I use 3DS ...
I am suggesting the right way to do this ☝️
Okay, but I also checking for the both condition "next_action is not qual to null" and "status is not equal to succeeded"
if the both condition is true I am blocking it
What's the status when you use the card above?
and I am getting "status": "succeeded" for that card
That's good, no?
but without 3DS modal , I am getting status as succeeded
for 3DS card
4000000000003063 for this particular card only
The PaymentIntent you shared had a different status. Could you please share the PaymentIntent ID that was successful? pi_xxx
ok
pi_3NxmnjIJbJroK8xx1sky6OqV ...... its same
took it from create_intent api response
I am taking status and next_action values from confirm api
I see the status is status: "requires_confirmation",
ok will send another one
{
"id": "seti_1NxnaUIJbJroK8xxyHh73myG",
"object": "setup_intent",
"automatic_payment_methods": null,
"cancellation_reason": null,
"created": 1696497078,
"description": null,
"last_setup_error": null,
"livemode": false,
"next_action": null,
"payment_method": "pm_1NxncVIJbJroK8xxAsd9RfqE",
"payment_method_configuration_details": null,
"payment_method_types": [
"card"
],
"status": "succeeded",
"usage": "off_session"
}
response from confirm api
Actually In this only I checking if that condition is true ,, I won't call for create_intent api
{
"requires_confirmation": true,
"stripe_payment_method_id": "pm_1NxncVIJbJroK8xxAsd9RfqE",
"stripe_payment_intent_id": "pi_3NxnceIJbJroK8xx1kFihnEr",
"setup_intent": {
"id": "seti_1NxnaUIJbJroK8xxyHh73myG",
"object": "setup_intent",
"automatic_payment_methods": null,
"cancellation_reason": null,
"created": 1696497078,
"description": null,
"last_setup_error": null,
"livemode": false,
"next_action": null,
"payment_method": "pm_1NxncVIJbJroK8xxAsd9RfqE",
"payment_method_configuration_details": null,
"payment_method_types": [
"card"
],
"status": "succeeded",
"usage": "off_session"
}
}
It is from create_intent
But that's a SetupIntent.
I mean the confirm endpoint and create_intent endpoint,,,yes the 1st one is setup_intents
I don't think this will cause any problems in production. If you run into any actual issues, please reach out and we will investigate.