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

# Pay as you go

> Buy credits up front and spend them as services run

Some organisations are set up to pay for credits directly instead of subscribing to a plan. If yours is one of them, the Billing page looks different: there are no tabs, no plan picker and no recurring plan credits. You buy credits when you need them, and each completed service run draws them down.

<Info>
  Pay as you go is arranged with the Borg team, and you can't switch to it from inside Odin. If you see the plan tabs described in [Billing](/platform/billing), your organisation is on a plan instead.
</Info>

## Prepaid credit balance

The top of the page shows two figures:

* **Available balance**: the credits you have left, with an approximate cash value alongside
* **Credit rate**: what one credit costs your organisation, fixed for the account and shown again before every top-up

Credits don't expire while your organisation is active. They are deducted when a completed service event is recorded, not when a run starts.

If your balance reaches zero, a banner tells you to add credits before starting or scheduling billable work. You can still sign in and look around Odin; only billable services are held back. A separate banner appears if a payment failed and the outstanding amount is still being recovered; new billable work stays paused until it clears.

## Adding credits

The **Add credits** card takes an amount in your account currency rather than a number of credits. Pick one of the preset amounts or type your own, and the card shows roughly how many credits it buys before tax.

<Steps>
  <Step title="Choose an amount">
    Presets cover the common cases; the input accepts any amount above zero.
  </Step>

  <Step title="Pay">
    If your billing details are already on file, the card charges your saved payment method. If they aren't, you're sent to Stripe Checkout, which collects your billing address and tax ID first.
  </Step>

  <Step title="Wait for confirmation">
    Credits land once the payment confirms, so the balance may take a moment to move.
  </Step>
</Steps>

Applicable tax is added on top of the amount you enter.

## Auto Top-Up

Auto Top-Up buys credits for you when the balance runs low, so a scheduled run doesn't stall overnight. Both of its fields are amounts of money, not credit counts:

* **When balance falls below**: the balance that triggers a purchase
* **Automatically add**: how much to charge each time it triggers
* **Payment method**: which saved card to charge (add one under Payment methods first)

A failed charge pauses Auto Top-Up and shows an alert on the card. **Retry now** clears the pause and tries again after the next deduction; you can also top up by hand in the meantime.

<Note>
  Plan-based organisations have a similar feature called Auto Deposit, which works in credits rather than cash. See [Billing](/platform/billing#auto-deposit).
</Note>

## Top-up history

The **Top-up history** card lists your five most recent credit purchases with the date, the amount paid and the credits received. Each one is labelled by how it was triggered: **Manual top-up**, **Auto Top-Up**, or **Balance recovery** for a charge that cleared an outstanding amount. Service usage isn't listed here.

## Payment methods and seats

Both cards behave as they do on a plan. You can add and remove cards under **Payment methods**, where Stripe handles the card details so they never reach our servers. The **Seats** card shows how many seats are in use and lets an admin invite members.

## Invoiced usage

Older pay-as-you-go accounts are billed after the fact rather than from a prepaid balance. That version of the page shows a **Usage history** list instead of the top-up cards, with one row per completed service event: what ran, when, the credits it consumed and the amount charged.

Each row carries a status:

| Status                         | Meaning                                                                |
| ------------------------------ | ---------------------------------------------------------------------- |
| **Pending collection**         | Recorded, waiting to be invoiced                                       |
| **Open**                       | Invoiced, not yet paid                                                 |
| **Covered by balance**         | Paid out of credits you already held                                   |
| **Deferred small amount**      | Too small to charge on its own; carried forward rather than rounded up |
| **Added to customer balance**  | Rolled into your Stripe customer balance                               |
| **Paid**                       | Settled                                                                |
| **Action required**            | Your bank needs to confirm the payment                                 |
| **Payment failed**             | The charge didn't go through                                           |
| **Voided** / **Uncollectible** | Written off; no payment is expected                                    |

Where a charge failed, admins get a **Retry payment** button on the row, and any row with an invoice behind it links out to Stripe's hosted invoice page.