With a working default card, a falling balance is not a problem you have to solve. It is the mechanism by which the card gets charged.
Saving the card itself is not a charge. Stripe attaches it through a SetupIntent for future use. On a new hourly deployment with no available credit, the first charge is exactly one month of credit for the selected plan and must succeed before provisioning is queued.
How it fires
When the balance drops below the auto-charge threshold ($1.00 by default), the default card is charged for one month of the account's current metered services, plus enough to bring a balance below the threshold back up to it. The calculation includes servers, Managed Services, and reserved floating IPs, and is subject to the top-up limit shown in the portal. The payment is posted as credit and you receive a receipt.
Why you stop getting low-credit warnings
A working saved card silences low-credit warnings while automatic recharge is ready to use it. Accounts with no usable card receive low-credit warnings as their runway shortens. If an automatic charge is declined, you receive the failure notice and low-credit warnings resume on later checks until a charge succeeds or you add credit another way.
When a charge fails
- The failure is recorded and low-credit warnings restart.
- Nothing is suspended on the failure alone. Suspension follows the balance, not the card.
- Fix or replace the card under Billing. The next pass tries again.