> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nylon.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Accounts paused for billing

> Why a connected account shows Paused — billing, what still works, and how to restore it.

An account showing **Paused — billing** is connected and its authorization is fine. It is not being served because you have more connected accounts than your billing covers.

## Why it happens

Your first two connected accounts are free. Beyond that, an active subscription is required. If there is not one — never set up, cancelled, or an invoice that failed — the accounts past the free allowance are paused.

Entitlement is re-checked on every read rather than stored, so a cancellation, a failed payment or a lapsed subscription takes effect immediately, and so does fixing it.

## What is paused, and what is not

<AccordionGroup>
  <Accordion title="Publishing is refused" icon="ban">
    An API call targeting a paused account fails with `402`. This is a billing state, not a user problem — do not prompt your user to reconnect, because there is nothing wrong with their account.
  </Accordion>

  <Accordion title="Nothing is disconnected" icon="shield-check">
    The connection, its credentials and its history all survive untouched. Pausing is deliberately not disconnection: a billing state can be temporary, and destroying credentials over one would mean every customer re-authorizing after a card expired.
  </Accordion>

  <Accordion title="The account is still listed" icon="list">
    Paused profiles are returned by the API rather than hidden, marked with `suspended: true`. A profile that vanished from a list would read to your users as a deleted account, which is not what happened.
  </Accordion>
</AccordionGroup>

## Which accounts stay active

The **longest-connected** ones. If you have five accounts and no subscription, the two you connected first keep working and the three newest are paused — which is predictable, and matches which accounts are marked *Free* in your billing breakdown.

## Restoring them

Set up billing at **Settings → Billing**, or settle the outstanding invoice if one failed. Every pause lifts immediately, with no re-authorization and nothing to reconnect.

If you would rather stay within the free allowance, [disconnect](/help/disconnect-an-account) the accounts you do not need. Disconnecting stops billing for them straight away, and brings your count back under the threshold.

## In your own application

Handle `402` distinctly from `reauthentication_required`. They look similar — a post did not go out — but they need opposite responses: one is yours to fix in billing, the other is your user's to fix by reconnecting. Showing a user a "reconnect your account" prompt for a billing problem sends them round a loop that cannot help.

## Related

<Columns cols={2}>
  <Card title="Manage billing" icon="receipt" href="/help/manage-billing-and-invoices">
    Starting billing, and settling a failed payment.
  </Card>

  <Card title="Connection statuses" icon="circle-check" href="/help/connection-statuses">
    How this differs from Reconnect.
  </Card>
</Columns>