Reserve prepaid headroom for support traffic, then verify payment readiness before treating configured auto recharge as a continuity control. The deciding constraint is whether the customer contract requires a hard spend ceiling or permits additional funding to keep support requests moving.
TL;DR: If service stopped despite API auto recharge being configured, check the billing account, its required default payment method, the funding attempt, the usable balance, and the traffic admission decision in that order. Treat a missing default payment method as a hypothesis to verify against the account's actual requirements; a saved payment credential alone is insufficient evidence that the intended account can fund another request.
For a customer support system that meters per-customer usage for an invoice, recovery has two obligations: restore only traffic the budget permits, and preserve the usage records needed to explain the eventual bill.…