jokamax

[spare summit]

Hi there!

Can you share an example PaymentIntent ID (pi_xxx)?

[civic brook]

I used two test card :
-- 4000002500003155 --> pi_3NhXDHHagJ8u1cfk17Uqovb7
-- 4000003800000446 --> pi_3NkT4mHagJ8u1cfk1yKQwnEW
These 2 cards are 3D secure test card but stripe support by mail indicate I have to use the second. I did that but... not work (required_action too)

In test env

[spare summit]

Everything looks expected to me. 3DS is required, so you need to ask your users to come back to your website/app and then confirm the PaymentIntent on the frontend to trigger the 3DS flow.

[civic brook]

No, I want to pre-configurate / registered the card for Offline Usage as subscription (internally coded - no stripe subscription). The documentation indicate that we can do that :

1. User register the card - with the 3D secure validation
2. We can use the card for futur buy of the client without asking to revalidate 3DS flow

I coded the "card registration" as indicated here : https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=checkout#use-payment-method

Save and reuse card

This is indicated here : https://stripe.com/docs/testing?testing-method=card-numbers#regulatory-cards

@spare summit

[spare summit]

Yes it's a two step process:

1. Confirm the card on the frontend once to trigger the 3DS flow
2. Then the next payments of the subscription won't trigger 3DS

But I don't understand why you are creating a PaymentIntent here if your goal is to test subscriptions? I'm confused.

[civic brook]

This is not stripe subscription. This is redundant payment mensually for internal product. So we coded the batch which call : payment_intent mensually.
The user pre-register his card and have validated 3DS flow.

That doesn't work in production
That doen't work in dev mode with test card too...

So...

(Without 3DS : everything work)

We can't do that without using "stripe subscription" ?

[spare summit]

Got it. Then for the first payment 3DS is required, that's why you see status: "requires_action".
So the enxt step is to ask the user to come back to your website/app and confrim the payment on the frontend to trigger 3DS. There's no other way, unless you change the test card for one that don't require 3DS.

[civic brook]

OH, I understand... the real flow is :

1. Register the card (optionnal)
2. Pay something with the card and validate 3DS card one time
3. The card can be used in the futur out of session next month wihtout ask something to user ???

Is that OK ?

[spare summit]

The card can be used in the futur out of session next month wihtout ask something to user ???
For that test card, yes. But in real life that's not how it works. The bank can ask for 3DS at any time in the future. So your integration needs to handle this.

[civic brook]

So impossible to use 3DS card with our personnal subscription system ? Because we can't ask user to revalidate each payment, each month...
In production (real life) : no way to use 3DS card in redundant payment mensually without re-validate 3DS code ??????

[spare summit]

So impossible to use 3DS card with our personnal subscription system ? Because we can't ask user to revalidate each payment, each month...
Yes it is possible. It's just that you system needs to handle the case where a recurring payment becomes status: "requires_action". It won't happen every time, but it may happen sometimes.

[civic brook]

When the status encounter is required action : what we have to do ?
Have you a link to the documentation ? (stripe-java api used).
I have to send a mail (async payment) with a link to validate the 3DS flow I suppose.

[spare summit]

When the status encounter is required action : what we have to do ?
I already answered that question multiple time. Confirm the PaymentIntent on the frontend (and not the backend) using this: https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached

[civic brook]

Thanks a lot.
I'll read this.
Have a good day$

[spare summit]

Happy to help 🙂