#hao-3ds-csp

1 messages · Page 1 of 1 (latest)

brittle pondBOT
torpid stream
#

I checked my own app. We don't have CSP configured. I think this actually might be the CSP in the Stripe elements iframe itself

rustic stag
#

hello, I'm not the most informed on CSP but the first thing I wanna ask - I assume you're displaying the 3DS authentication iframe in your own iframe (in your integration)?

or letting Stripe.js / Elements handle it

torpid stream
#

We use Stripe.js / Elements

rustic stag
#

ok, in live mode when you tested, what does it block for you? like what do you see on the webpage?
an empty modal? no modal? a model but something on it missing?

torpid stream
#

no modal

#

I see 3DS is not triggered and the card is set up directly

#

and I see the error message in the JS console

rustic stag
#

the card is set up directly
what do you mean? like the SetupIntent (or PaymentIntent) is in status: succeeded ?

#

hao-3ds-csp

torpid stream
#

Let me check

#

This is the log

#

I believe we call setup_intent on the server side, and have Stripe JS handle the rest of the flow

#

The Stirpe program is atob-fleet

sour surge
#

Just catching up as my colleague needs to step away

#

This request created a SetupIntent successfully. The current status of the SetupIntent is requires_payment_method, so payment details are missing.

#

I see this is in live mode though. Have you tested 3DS in test mode with test card numbers?

torpid stream
#

Yes, in test mode everything works correctly

sour surge
#

I see. Do you have a SetupIntent ID where 3DS was not correctly displayed? It's possible that this particular SetupIntent did not require additional authentication.

#

The SetupIntent that was created by req_aZYuE69sKTKNrR won't be much help at the moment, as card details haven't been collected

torpid stream
#

Let me check around it

#

I am also testing to display the iframe 3DS myslef, however, the response is different with the documentation

#

I will open a new thread on this to discuss

#

For this thread, I will find you a more relavant log on the 3DS in Stripe JS

#

So I found a few things:

#

Does that mean that the 3DS v2 is run and no additional log is needed for the debit card?

sour surge
#

Taking a look at the details

#

I see a reference on my end to 3DS for that SetupIntent

#

3DS appears to have succeeded in this case

torpid stream
#

oh

#

3DS runs successfulyl without any user input? I was under impression that it will pop up some dialog from the issuing bank?

sour surge
torpid stream
#

Great thanks

#

Do you know any bank that will runs the 3DS v1 way?

sour surge
#

Not off the top of my head, no. I believe most support 3DSv2 now

torpid stream
#

Cool thanks

#

I will ask another question now

#

Right now we use Stripe elements to handle the 3DS flow. What if we want to implement 3DS flow our sevles?

#

Context: we are using a tokenization service to collect cards info and add the debit cards to multiple Stripe programs we own, so that we might not be able to use Stripe elements.

#

The response is very different with the documentation on 3DS

#

How to handle the next action if it is use_stripe_sdk?

sour surge
#

I see there's a value for three_ds_method_url under next_action

#

Digging into whether this is what should be followed

torpid stream
#

Does that mean I have to use Stripe.js to load this?

#

Is there any documentation on that?

remote sun
#

👋 stepping in as roadrunner needed to step away

#

Can you summarize the question here?

#

Sounds like you are talking about handling 3DS?

torpid stream
#

Yes

#

My question is that when I request 3DS when calling 3DS

#

I am not sure how to handle next_action

#

Because it is very different with the documentation

remote sun
#

Gotcha

#

Yeah there are two ways

#

With your example above, you didn't pass a return_url so you would call stripe.confirmCardSetup client side

torpid stream
#

OK let me try quickly

#

Oh great, it works! THANK YOU!