#eapollo
candid robin
Hi River! 😄
jovial coral
Can you share the subscription ID (sub_xxx)?
candid robin
sub_1N3Vh3Gn*********
This was said to be possible by Karbi when I asked in this discord a while back:
"You technically could do a one-time charge first and after success you could create the Subscription on a trial period until it's next renewal time
But really the best thing to do would be to switch over to using webhooks - can you elaborate on this a bit more:
our endpoint would return the correct error which I dont think can be done with webhooks" - Karbi
This was so that I can achieve 3D Secure while still continuing to make charges on the backend
Any ideas @jovial coral ?
candid robin
No worries 🙂
jovial coral
In the subscription creation, I can see that the default_payment_method was set: https://dashboard.stripe.com/test/logs/req_BGiD4Oc5GYADEt
The test card used in pm_1N3VgqGneVlO9kvBYDrnAb04 was 4000000000003063. In the invoice (https://dashboard.stripe.com/test/invoices/in_1N3VisGneVlO9kvB59qiI0cO) that the payment failed, the payment was declined with generic_declined.
The behaviour does seem strange. Could you try a different test card to check if it works?
candid robin
I specifically need a 3D Secure test card
I tried with the 42424 card and it was fine
I guess there is only 1 3DS test card?
jovial coral
Can you try 3DS test card - 4000000000003220 from https://stripe.com/docs/testing#three-ds-cards?
candid robin
That seemed to work better now but gives the error: "payment was initiated which requires an additional user action"
Additional user action is required if 3D Secure already was verified on first charge?
sub_1N3WQSGneVlO9kvBurKIqlaY
@jovial coral
jovial coral
It's possible that the issuing bank requires authentication again on the invoice even if the authentication has been performed before
Could you share the subscription ID (sub_xxx), so that I can double check?
In https://dashboard.stripe.com/test/invoices/in_1N3WR4GneVlO9kvBuALcQwyQ, the payment method requires 3DS again. It can also happen in live mode as well. Customer should complete 3DS authentication in the invoice hosted page
nova ivyBOT
candid robin
Really strange that 3Ds would be required again especially for the first renewal payment. Would imagine it would cause a lot of missed or cancelled subscriptions due to this
But I guess thats out of Stripe's control?
placid dome
Hi @candid robin I'm taking over
candid robin
Hey @placid dome ! Thanks for the help so far @jovial coral
placid dome
Is your latest question about 3DS?
placid dome
Ok. The card issuer and your radar rule determine if a 3DS is required for a transaction.
So your integration should be always ready to handle the scenario when a paymentIntent is in requires_action status
candid robin
It's normal for a monthly subscription to require 3D Secure authentication more than once?
Or is this kind of rare cases
I guess my question is more is this an issue with my implementation or expected
placid dome
It's possible.
candid robin
So my implementation is fine?
I would imagine the team at Stripe has tested a 3DS stripe test card with a test clock attached. Does it always ask for 3D secure as well on first renewal? Not sure if u would know that @placid dome
placid dome
Which test card?
candid robin
4000000000003220
placid dome
This is a card to request 3DS
3D Secure 2 authentication must be completed for the payment to be successful. By default, your Radar rules request 3D Secure authentication for this card.
Is this the scenario that you want to test?
candid robin
Yeah, but what im interested in is what happens on renewal when u guys test it? 3D Secure is required again?
Im mostly trying to rule out that its not an issue with my implementation
placid dome
So you want to test out a flow where 3DS is required for subscription renewal?
candid robin
yeah
placid dome
4000002760003184 you can use this card, it would always authenticate