#niteeshvparticipant

1 messages · Page 1 of 1 (latest)

echo horizonBOT
ivory cargo
#

Hi. Let me help you with this.

#

Where are you typing the card number in?

lone wasp
#

here only

ivory cargo
#

Could you please share the PaymentIntent ID pi_xxx?

lone wasp
#

yes

#

pi_3NxmnjIJbJroK8xx1sky6OqV

ivory cargo
#

This PaymentIntent requires confirmation, have you tried confirming it?

lone wasp
#

not getting your point here

#

you mean the confirm api ?

ivory cargo
#

What Stripe guide are you following?

lone wasp
#

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 ?

ivory cargo
#

Perhaps this surface doesn't support 3DS(1), just 3DS2

lone wasp
#

is there any other "3DS Required" test cards

#

and how to support the 3DS, do you mean surface as app

ivory cargo
lone wasp
#

one sec

#

card element ji

ivory cargo
#

But what happens exactly when you provide this card?

#

And again, what guide are you following?

lone wasp
lone wasp
ivory cargo
lone wasp
#

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

ivory cargo
lone wasp
#

actually, In our app, if the card has 3DS we are not gonna allow those cards

ivory cargo
#

Why?

lone wasp
#

I will check the reponse of confirm api , if it is like thee_d _secure I am blocking it

lone wasp
#

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

ivory cargo
#

What you should look out for is status: "requires_action", this means that the card required 3DS.

lone wasp
#

no

ivory cargo
#

What do you mean?

lone wasp
#

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 ...

ivory cargo
lone wasp
#

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

ivory cargo
#

What's the status when you use the card above?

lone wasp
#

and I am getting "status": "succeeded" for that card

ivory cargo
#

That's good, no?

lone wasp
#

but without 3DS modal , I am getting status as succeeded

#

for 3DS card

#

4000000000003063 for this particular card only

ivory cargo
lone wasp
#

ok

#

pi_3NxmnjIJbJroK8xx1sky6OqV ...... its same

#

took it from create_intent api response

#

I am taking status and next_action values from confirm api

ivory cargo
#

I see the status is status: "requires_confirmation",

lone wasp
#

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

ivory cargo
#

But that's a SetupIntent.

lone wasp
#

I mean the confirm endpoint and create_intent endpoint,,,yes the 1st one is setup_intents

ivory cargo
#

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.