Hello,
I’m encountering challenges while testing the Subscription API in Sandbox, specifically related to simulating different failure scenarios. I’ve noticed there isn’t an option to assign a failing card to a subscription, which complicates testing how the API handles scenarios like expired or lost cards.
Could you advise if there’s a method to deliberately trigger a failure for a recurring charge associated with a card on file? This functionality is crucial for testing the webhook that manages failed subscription events.
Additionally, I’m curious about the behavior of the subscription.updated webhook event when a subscription is paid via an invoice after a card failure. Is subscribing to invoice webhook events also necessary?
Another concern is the handling of paused subscriptions. They are scheduled to pause at the end of the billing cycle, but since this typically coincides with failed payments, does the pause take effect immediately? We need to ensure that the service is inaccessible to delinquent subscribers immediately after a payment failure. Currently, the system still marks the subscription as ‘active’ despite payment delinquency.
Ideally, I believe a delinquent subscription should be automatically paused, but that’s a separate enhancement request.
Thank you for your assistance.
3 posts - 2 participants