#quentinnprt
neat sealBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- quentinnprt, 2 hours ago, 12 messages
round mesa
I think the way I'd expect this to work is you add a card to a Customer and enter exp_month:12 exp_year:2023 for example when creating the PaymentMethod; then you create a monthly subscription for the Customer and advance a clock to like Feburary 2024 and hopefully observe that some of the Invoice payments failed.
bleak willow
Oh ok, I'll try this way, thanks 🙂
round mesa
I haven't tried it myself so not sure if that works(it's quite possible that inside the test clock when we process the actual underlying payment we are comparing the real "wall time" against the card expiry and not the TestClock time) but if this is supported that's what I'd epxect to work
bleak willow
Any other solution if it doesn't work ?
round mesa
hmm can't think of one
lunar onyx
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
bleak willow
okok, thank you 🙂
lunar onyx
I am not sure card expiry works with test clocks.
Test clocks only apply to a subset of functionality, like Subscriptions and Invoices.
bleak willow
So is there any way to test that ?
lunar onyx
I would replace the test card with one that produces the expired card decline: https://stripe.com/docs/testing#declined-payments
bleak willow
I can't attach a expired card to the customer
lunar onyx
Oh, right, makes sense.
I don't think there's another way to test this, unfortunately. You should rely on generic errors that you can get with "Always authenticate" card https://stripe.com/docs/testing#regulatory-cards
bleak willow
Okok, thank you
lunar onyx
Happy to help.