#frankp_21403

1 messages · Page 1 of 1 (latest)

dire topazBOT
#

Hello frankp_21403, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• frankp_21403, 0 days ago, 7 messages

stuck arch
#

You stopped responding to me

#

So we close threads after some inactivity

rotund raptor
#

I was pulling the docs, please reopen

stuck arch
#

Let's continue here

rotund raptor
#

These are the guides that our team used

#

Using this test card - I can reproduce the same experience that we see in prod //4000 0025 0000 3155 -- "requires auth"

#

Using this test card - I see a diff 3DSecure experience 4000000000003220

dire topazBOT
weak sonnet
#

HI 👋

I"m stepping in as my colleague needs to go soon. What is the current state of your question? What is it you are trying to achieve?

rotund raptor
#

Thanks Snufkin

#

Please review this thread which was closed after a short time.

#

Ultimately I am eager to understand how to better control the experience our customers are having when 3dsecure/auth is triggered within our app.

weak sonnet
#

I'm not going to re-read the old thread.

Beyond 3D Secure being triggered whenever an issuing bank determines it is needed, what are you looking to control?

rotund raptor
#

There are only 2 messages from me in the thread, it was just opened.

#

And you'll need to check the video example if you want to understand the probem.

#

I can also go back to our AE and find another route for support if this isn't the right place.

weak sonnet
#

That depends, can you provide a crips and clear description of the behavior you are seeing and what about it you want to change?

rotund raptor
#

Sure but please don't close this thread -

#

This is the experience that we are recieving today that makes our customers feel uneasy because it is not clear what is actually going on. All we get at the end of this "hooks.stripe" popup is "Auth Complete" - we'd like to be able to customize the experience so they know what is happening -- is it possible to keep the hook inside our app's frame? Or provide a message? "We're checking with your bank. Please wait until it says Complete!"?

#

Can you confirm what is actually happening with this "Auth Complete" workflow?

#

I can reproduce this same experience using this test card --> 4000 0025 0000 3155

weak sonnet
#

Can you share the payment intent used for this?

#

Specifically the ID

rotund raptor
#

Do you want an example payment intent from dev?

weak sonnet
#

I want a Payment Intent that went through the process you are describing

rotund raptor
#

sure 1 sec

#

pi_3O3KZ0KzGpQ7khdc1yd5l3pG

#

and here is an example PI for the other experience that I was describing above where the nicer looking 3DSecure window pops up #1164950697557639218 message -- pi_3O3KcWKzGpQ7khdc1S7PUQaE

weak sonnet
#

Hmmm... both appear to have used the same challenge authentication flow

rotund raptor
#

do you see the difference in screenshots though?

#

the experiences were totally different

weak sonnet
#

Yes, that is what is confusing me too

rotund raptor
#

looking at my dashboard, I actually see a difference

#

the first one that we do not like looks like was 3DSecure1 where the other one is 3DSecure2

weak sonnet
#

I am seeing 3D secure network conversations for both

rotund raptor
weak sonnet
#

Ah, right! One was 3DS1 (which is deprecated now) and the other was 3DS2

rotund raptor
#

but we don't have any control over that do we?

weak sonnet
#

No, this is entirely controlled by the issuing banks and all traffic is moving to 3DS2 anyway

rotund raptor
#

the "Authentication Complete" window cannot be changed at all?

#

or the workflow

#

I did see in the react native sdk documentation that there was a way to give styling to the StripeProvider element

#

but this doesn't change the way the 3dsecure2 flow looks?

weak sonnet
#

No, not at all. Neither Stripe nor you have access to the content within that window. It is entirely controlled by the issuing bank for security purposes

rotund raptor
#

Is there a way to configure the app to keep the flow inside our frame?

#

rather than it leaving the app?

weak sonnet
#

There is but it is very manual, we do not offer much in the way of support, and we don't recommend it.

rotund raptor
#

🙂

weak sonnet
#

These steps discuss how to trigger the 3DS flow within the Stripe Provider but we cannot offer any support here beyond what is shown in this doc directly

rotund raptor
#

Why isn't it recommended?

weak sonnet
#

Because we have built a lot of edge case handling into our automated approach and you don't get the benefit of it if you chose to display 3DS yourself.

rotund raptor
#

Is there documentation around those edge cases?

weak sonnet
#

Nope

rotund raptor
#

BTW - adding those params to my stripe provider doesn't change anything. Is there something else that must be configured for displaying this ourselves?

weak sonnet
#

Which is why we don't have much support offered here. Knowing those edge cases and how to handle them isn't something anyone that staffs this Discord server will know.

#

Oh wait, you're right I'm not seeing the manually dispaly option...in any docs

rotund raptor
#

yeah - it's confusing since the link you shared is seemingly what we want

#

and there is no mention of it not being supported

weak sonnet
#

Ah I don't think it is supported in the mobile platforms. I do see it when I switch the platform tab to Web

#

Along with one of the reasons we don't recommend doing this yourself

Stripe.js collects basic device information during 3D Secure 2 authentication and sends it to the issuing bank for their risk analysis

rotund raptor
#

what if ONLY styling is applied? i.e. nav bar header

#

threeDSecureParams={{
backgroundColor: '#FFFFFF', // iOS only
timeout: 5,
label: {
headingTextColor: '#0000',
headingFontSize: 13,
},
navigationBar: {
headerText: '3d secure',
},
footer: { // iOS only
backgroundColor: '#FFFFFF',
},
submitButton: {
backgroundColor: '#000000',
cornerRadius: 12,
textColor: '#FFFFFF',
textFontSize: 14,
},
}}

#

it doesn't seem like this would change anything else

#

I need to drop for now but will come back later in case there is more information you can provide on the documentation front. I will begin to summarize this thread to share back with our AE who is helping us track this ticket. Please don't delete this thread.

weak sonnet
#

Threads are not deleted, only closed due to inactivity

#

You will be able to find this thread for reference later on