#theglobe-subscription
misty elm
sure
"sub_1L5sjoDa8Si35vWqcyBCgkiK"
sorry, I think this is the event ID evt_1L5sjtDa8Si35vWqY1fYYTxg
sharp fox
So what you're seeing is expected because you're using payment_behavior: allow_incomplete (see https://stripe.com/docs/api/subscriptions/create#create_subscription-payment_behavior). With allow_incomplete we still create the Subscription with an incomplete status if it cannot be paid, and the Subscription will transition to incomplete_expired (equivalent to cancelling it) after 23 hours.
You'll want to change your integration to check whether status: active from the customer.subscription.created event, and also listen for customer.subscription.updated event to check if the status becomes active within those first 23 hours
misty elm
oh okay, so I new event will be triggered if the payment is still incomplete after 23 hours.
do you know which event will be triggered?
and do you know if the user receive any email related to the wrong cvc?
sharp fox
The customer.subscription.updated event will be triggered.
I don't believe they'd receive an email related to the wrong CVC - if your customer is on-session the expectation would be that you surface that to them in the UI
misty elm
and if the user does not update their cvc number and the payment fails again (after 23 hours) is there a new event that will be triggered?
Because I have an automation for customer.subscription.deleted that cancells the users account
sharp fox
The payment wouldn't fail again after the 23 hours because the Subscription would be canceled at that point - you'd need to create a whole new subscription to have them retry payment.
and no, the expiration after the 23 hours wouldn't trigger a customer.subscription.deleted event
misty elm
ok I will see what I can do here. Thank you for your help