#akdj16
1 messages · Page 1 of 1 (latest)
hi! that's normal if you are using any test card that is not specifically the ones that simulate working unauthenticated for off-session payments.
i.e if you want this to not need 3DS every time, you have to use a card like 4000002500003155 which simulates that. https://stripe.com/docs/testing#authentication-and-setup
in any case, you shouldn't create a SetupIntent and then immediately create a Subscription that way, if that's what you're doing. You should create the Subscription first, and then pass the subscription.latest_invoice.payment_intent.client_secret to the mobile app, which can collect the payment details and confirm the PaymentIntent in one step which activates the subscription. Same idea as https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements, we don't explicitly document how to do it on mobile unfortunately, but it works the same way.
I used this one. In fact, i tested several cards, 4000002500003155, 4000003800000446, 4000000000003220, 4000000000003063. and this one 4000000000003055.
only 4000000000003055 this one doesn't triggered the 3ds process, but it doesn't triggered at all... I need one time
yeah the thing is those cards simulate exemptions from 3DS for off-session payments. Creating a subscription while the customer is present in your app is not an off-session payment.
ok
hence why you shouldn't do a two step process of SetupIntent -> Subscription, you should just create the Subscription and use its PaymentIntent for the on-session process, as described above.
ok I see