Runbook — Company card changed
When a company credit card is replaced (expiry, fraud reissue, new provider), every service with auto-pay needs the new card or it will silently lapse — and we won’t find out until something breaks.
The checklist
Work Subscriptions & Vendors top to bottom, in tier order (🔴 first). For each:
- Log in (credential location is in Access & Ownership).
- Update the payment method to the new card.
- Confirm auto-renew / auto-pay is ON.
- Note the date you updated it.
Priority order (do the 🔴 ones first — these take the site down)
- Domains — GoDaddy and Squarespace (
hellobellocdn.com). A lapsed domain = NXDOMAIN = hard outage. See Domains. - Hosting — Vercel, Render, AWS.
- DNS / CDN — Cloudflare.
- Payments & commerce — Shopify, Recharge, Braintree, Stripe.
- Databases — MongoDB/MySQL/Redis providers.
- Then 🟡 / 🟢 — comms, analytics, monitoring, the rest.
Why this runbook exists
The registrar for hellobellocdn.com lapsed and took all site images down (2026-06-29). The
underlying cause was a payment/renewal that didn’t go through. A disciplined card-change checklist is
the cheapest insurance against repeating it.
✅ After a card change, the subscriptions page should have every 🔴 row updated the same day. Leaving one for “later” is exactly how these lapses happen.