#bruno-pending_if_incomplete
1 messages · Page 1 of 1 (latest)
Just to clarify why I want to do this: my app kinda knows that the customer abandoned the "payment confirmation" page. For example, the customer is creating new local resources or attempts another payment.
So we actually have built in behavior to expire the pending updates https://stripe.com/docs/billing/subscriptions/pending-updates-reference#events
We set it to 23 hours from when the update was created or to the end of the current billing/trial period end, whichever comes first.
Does that basically do what you want here?
Yes, that's great. However I would like to manually expire pending updates BEFORE the 23 hour mark.
As mentioned above - the customer may silently abandon the SCA "payment confirmation" page (leave the browser window open). Then they starting other resources in another browser window.
It would be nice to prevent race condition behaviors by manually expiring pending updates when this happens.
Gotcha. You can cancel before then by voiding the invoice that the updates created https://stripe.com/docs/billing/subscriptions/pending-updates#canceling-changing
Great to hear! Happy I could help