#meisei81-Subscription
1 messages · Page 1 of 1 (latest)
If you collect the card info and authorized it on the first cycle, in the next renewal date you should able to collect the payment seamlessly. But you also need to have to logic , just in case customer's bank requires authentication again, to notify Customer and let them authenticate again
From this customer's timeline, I can see stripe try to make the payment but the bank return a code authentication_required, it says that the card holder has open a 3D secure authorize
this happens in test mode and use stripe test card "4000 0027 6000 3184"
this payment method's cvc checked is successfully
Yes because that 3184 card is for simulating that situation, when customer bank require 3DS on every single transaction. It's not common in real-world use case, but it could happen. We prepare that card for you to test such scenarios
this 3184 card would need customer check their 3DS in the every renew cycle, right?