#od
cobalt basalt
tall crescent
It seems strange that this can happen when the portal actually prevents customers from deleting their payment methods if their subscription is active. But by canceling it, they can bypass this and delete all payment methods
drowsy portal
Can you share with me the subscription ID?
tall crescent
sub_1N2t7NLGhCVMvqQK9A7nL6c4
drowsy portal
Based on the events https://dashboard.stripe.com/test/events/evt_1N2t7OLGhCVMvqQKFyk60Nyh and
https://dashboard.stripe.com/test/events/evt_1N2t7OLGhCVMvqQK9rqDSb6j, the invoice was created and paid immediately, where did you see the 1 hour delay?
tall crescent
The invoice is in a draft state. But there are no payment methods attached to the customer.
In customer portal, if subscription is "active", customer cannot delete payment methods. This is good. However, suppose the customer has made API requests (we charge per API request). If the customer wants to avoid paying, the customer could first cancel the subscription on the portal. This moves the subscription to a canceled state. Moreover, it creates a draft invoice where payment isn't attempted to an hour later. But in between this time, the customer can delete all payment methods.
drowsy portal
Just want to understand the problem that you want to solve, so basically you don't want to let your customer to delete payments through billing portals, am I right?
tall crescent
Want to make sure there is always at least one payment method on file that can be attempted to resolve any outstanding invoices / unpaid subscriptions. We only subscribe our customers to a product after they have entered their card details through a Stripe checkout page - when we do so, we attach the entered card details to the subscription using the default_payment_method parameter.