#abignalet

1 messages · Page 1 of 1 (latest)

vast otterBOT
hazy compass
sage hill
#

In case there is a 3ds chalenge, you'll see it in your dashboard, on the timeline of the PaymentInent

hazy compass
#

stripe should let my app the opportunity to do the pm authentication if required on confirm no?

sage hill
#

If there was a 3DS attempt, then you'll see something like this in the timeline

hazy compass
#

I know thank you
I just want to know what to do when I receive this error code - should I retry the confirm?

sage hill
hazy compass
#

I do the confirmation using stripe js

#

I have this integration, what am I missing about authentication on payment method creation?

sage hill
#

How are you collecting the Payment details?

hazy compass
#

using CardElement + stripe.createPaymentMethod

sage hill
hazy compass
#

We cannot migrate to payment element, our UI won't support it

sage hill
hazy compass
#

Not a little change by our side, could you explain why it would change something?

sage hill
#

Actually, you are using an old integration that's why I invited you to migrate to the new integration.

Not a little change by our side, could you explain why it would change something?
stripe.confirmCardPayment will create the payment_method, authenticate it and if needed will carry out 3DS or other next actions if they are required. SO that the PaymentMehtod is fully authenticated.
in your flow you are just creating the payment_method without authenticating it when using just stripe.createPaymentMethod

hazy compass
#

but i call confirmCardPayment with the paymentMethodId just after

#

It is this call that fails instead of authenticating my pm

sage hill
#

Honestly this is an old integration and not very familiar with,
Could you please share a snippet code that reproduce this issue ?

hazy compass
#

<CardElement>
<button submit>

submit() {
const {error, paymentMethod} = await stripe.createPaymentMethod({ type: 'card', card: cardElement });

const {clientSecret} = await myApi.pay(whatever)

const {error, payment_intent } = await stripe.confirmCardPayment(clientSecret, {payment_method: paymentMethod.id, return_url: 'https://our-website.url/3DS'})

const is3DS = payment_intent.next_action.type === 'redirect_to_url';
if (is3DS) window.redirect(action.redirect_to_url.url)
}

sage hill
#

Thanks for sharing let me check

swift remnant
#

Hi! I'm taking over this thread.

#

Can you try to summarize your question, while I catchup with this thread?

hazy compass
#

how can I avoid authentication_required on confirmCardPayment

swift remnant
#

What do you mean? Do you have an example of this happening? Is this the PaymentIntent you shared earlier? pi_3LswDrDlpLzq27jH2DGE9VkP

hazy compass
#

exactly

swift remnant
#

Do you get a lot of PaymentIntent in that state? To me this simply looks like the bank declined that specific payment.

hazy compass
#

Like more than 30 this previous weekend

#

I just wanted to know if it was possible to avoid them

#

It represents nothing big but we are looking to get rid of it if possible

#

But we usually get less than this number

swift remnant
#

Sorry for the delay, looking into this.

mellow reef
#

@hazy compass you wrote to our enterprise support team about this too and are in touch with them, let's keep the conversation there