#william_implex
1 messages · Page 1 of 1 (latest)
This payment requires additional user action before it can be completed successfully. Payment can be completed using the PaymentIntent associated with the invoice.
Would depend on the test card you used really, but sure that can happen. Do you have an example?
If I've understood correctly, despite the setupIntent, the customer will still have to make another payment using a paymentIntent to finalize the subscription and invoice? What's the point of the subscription if the customer has to make a payment each time he renews?
The SetupIntent will facilitate saving/setting up the card for future off-session payments to optimise against these scenarios. But banks can still request authentication for off-session recurring payments, sure
Okay, I used this test card: 4000000000003220
Which goes like this: "3D Secure 2 authentication must be performed for all transactions. Triggers the authentication flow with a non-Stripe user interface."
Okay, I see, what would be the procedure to follow if this ever happened?
Yup as per the description the 3220 card will require auth for every payment regardless of whether it was saved/setup (with a Setup Intent). You will likely want to use 4000002500003155 for the scenario you originally described
But, as I said, off-session payments can (and do) sometimes require auth by the bank which is ultimately surfaced as a decline. Your integration needs to handle those scenarios
OK, thanks! In the case where authentication is required each time: Is it possible to just have the bank's confirmation window or does the customer have to enter his bank details in a new paymentIntent linked to the invoice awaiting confirmation?
If 3DS is requested on an off-session recurring payment it'll transition to requires_payment_method and will require re-confirmation with either new payment details, or a pm_xxx object they have saved
I'll take a look at it from my side.
thank you and have a nice day!