Jeremy T.

[warped dome]

To not show? Why would you want that?

[potent karma]

I understand the sentiment but we have a requirement where it's "better" for us not to show the challenge flow because it breaks our "user experience". And I guess its fine (for now) if the transaction fails if it requires 3DS2.

Also, just so I understand it correctly. "confirm = true" means our server (for example) does the creation and confirmation of the PaymentIntent, right?

[warped dome]

I guess you'd just check the status of the Payment Intent returned form your backend and if requires_action (i.e. 3DS/auth) then throw an exception. Alternatively you could configure Radar to block any payments that request 3DS. But this seems bizarre, especially if you're operating in Europe, as you'd be squandering a lot of potential revenue

[warped dome]

Yes, confirm: true means we'd attempt to confirm on the creation request. If the bank requests 3DS, then the PI status is updated to reflect that

[potent karma]

Gotcha.

Is there a way to do this with your mobile SDKs using the confirmPayment() or confirmPaymentIntent() ?

[warped dome]

Do what?

Can you share an example PI?

[potent karma]

Not showing the challenge flow using the mobile SDKs confirmPayment() or confirmPaymentIntent().

Or is the best way to handle this is, by checking the requires_action during the PI creation from our server before we forward to the client app to confirmPayment()? Am I making sense?

[warped dome]

Well, it depends on how you're creating the Payment Intent. Are you passing a pm_xxx or are you collecting payment data in the UI before confirmation

This is why I asked for an example pi_xxx

[potent karma]

Can you help me check this one pi_3LmZEZBd8PxzBU0N1PtN1OcF?

Currently, I have this flow.
Server creates PI -> Mobile confirmPayment() -> 3DS challenge flow is shown -> Confirm/Fail/Cancel -> Server checks the webhook status.

The flow I want to achieve is.
Server creates PI -> Mobile confirmPayment() -> DO NOT show the 3DS challenge flow -> Server checks the webhook status (if needed?)

[warped dome]

Do you always pass payment_method when creating your Payment Intents? https://dashboard.stripe.com/test/logs/req_sB2eLt8nfzeBqc

i.e. are they saved on file already?

Or do you collect payment details during the payment flow sometimes?

[potent karma]

We saved the payment_method already and should be attached the Stripe customer details.

So we have a functionality to save the payment method. Then using that saved payment method we try to collect the payment later (not a subscription based).

[warped dome]

In that case, you just need to pass confirm: true during PI creation and check the status field on the response

There's no need for confirmPayment at all

[potent karma]

Gotcha. I know how to proceed now. Thank you for the help @warped dome. 🙇‍♂️