Live

Safeguarding cashflow from subscriptions

We changed how subscription payments work for teams billed on a Pay As You Go basis, requiring a payment card to keep subscriptions active.

Progress

Exploring (completed)
Building (completed)
Live (current)
ThemePayments and billingForOperator

What's new

Pay As You Go teams can add, manage, and delete a payment card in team settings in Hub. A card is now required for new subscriptions on these teams, otherwise the subscription is paused. Previously, subscription payments came from the team wallet, which could go negative and leave subscriptions unpaid. Personal and Private Default teams pay subscriptions with their default card. This does not apply to teams on Operator Transaction or Invoicing, or to subscriptions priced at 0 per month. If a subscription payment fails, team admins are reminded during a grace period. If it stays unpaid, the team is frozen until the payment is made.

Why it matters

Subscriptions are paid from a card instead of a wallet balance that could go negative, so teams avoid unpaid subscriptions and interruptions.

Who it's for

Team owners and admins on Pay As You Go billing with active subscriptions.