#ryandududu
1 messages · Page 1 of 1 (latest)
Hi
Nope. Here it looks like the bank of a saved payment methods requested a 3ds auth, so the automatic payment attempt was failed then they completed the 3ds auth so that the payment is succeeded.
Alright. We are currently using
stripe.subscriptions.create
Do you think this function auto charges users?
I would like to do the confirmation or pay on the front end SDK
You need to follow this guide in fact in order to have a fully working subscription integration:
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
But again, the behavior above is normal in some cases, if a requiring (off session) payment fails due to 3DS.
so in the logs, you'll see a failure attempt, then a success attempt after completing the 3DS by the customer.