#nicolas
prisma iron
echo relic
Hmm, I think it'd depend on a couple of things:
- How they change their card (i.e. via what surface/UI).
- Why it's in a
past_duestate.
For example there's this revenue recovery email you can enable for failed payments: https://stripe.com/docs/billing/revenue-recovery/customer-emails#manage-failed-payment
That will collect new payment details from the customer and re-attempt invoice payment (which will than update the sub).
foggy sky
There are mostly two cases "insufficient funds" or "expired card"..
echo relic
But if they just update their details via your UI, then I think you'd need to initiate re-confirmation of the PI associated with the unpaid invoice
foggy sky
Yes, it's through our interface for the moment
We plan to move to Stripe Checkout in the coming weeks
echo relic
Well, Checkout doesn't support recovery flows like this currently (it's only good for initiating new subscriptions)
So I think you'd need to manually bring the user on session, collect new payment info and re-confirm the PI. You can/should test this flow with a clock: https://stripe.com/docs/billing/testing/test-clocks
