The problem:

When a SaaS sub-account's payment fails and the account is paused, the connected custom domain(s) are not disconnected — they stay live. So a client who has stopped paying keeps their website, funnels, and domain fully served with no interruption. The pause hits internal functionality, but the most public-facing asset — the live domain — keeps running for free. There's currently no way to automatically pull the domain when payment fails.

The ask:

An agency-configurable setting — attached to the SaaS home sub-account — that automatically disconnects (or takes offline) the sub-account's connected custom domain(s) when a payment fails. Ideally:

Trigger on payment failure, on the agency's own timeline (e.g. immediately, or after a configurable grace period).

Handle all connected domains on the sub-account, not just the primary.

Optionally redirect the disconnected domain to a "please update your billing" page instead of leaving a dead/live site.

Why it matters:

Right now there's no leverage on the one asset the client actually cares about staying up. A non-paying account can keep its public site live indefinitely, which removes urgency to resolve billing and effectively gives away the most visible part of the service for free. Auto-disconnecting the domain (with an optional billing-update redirect) gives agencies real recovery leverage and closes an obvious gap in the SaaS dunning flow.