#alpamayo-subscription-sepa
1 messages ยท Page 1 of 1 (latest)
Hey there ๐ please bear with me a moment while I think through this, as the scenario is a touch complex.
Note : our Customer can switch to SEPA when we detect a "past_due", they can update the PM with a Checkout in setup mode
Thanks for your patience! I was able to confirm that the behavior you're experiencing is expected, and that there isn't a way to force the subscription back into an active state. That being said, if you want to give the customer access to your services again while the payment is processing, then you can listen to the payment_intent.processing to determine when the payment has begun processing.
https://stripe.com/docs/api/events/types?lang=python#event_types-payment_intent.processing
Ok thanks, but sometimes we setup active manually for some customers but the webhook raise suscription.udpate event and crush our "fake" active status
Do you know why ?
Can you elaborate on how you're forcing the active status? If you have the ID (evt_xxx) of a sample event showing the described behavior, that would also be helpful.
We force it in our database, for each customer we have his Subscription status, and we set it to "active" and our system think that everything is OK
But the webhook sometimes is raised and set it back to "past_due" because it's the "real" status
But we do not know why the webhook is raised in this windows
Sounds like you're talking about a customer.subscription.updated event, which are triggered when an update is made to a subscription.