---
name: billing
description: "Manages fleet billing: recent billing events, balance adjustments, low-balance thresholds, cost outliers, and Stripe Connect payouts and disputes. Use when the operator asks about billing, invoices, charges, balance adjustments, payout status, chargebacks, or which subscribers cost the most."
argument-hint: "[events|balance|topup|payouts|configure] [subscriber/account]"
---

# Billing

Manage money movement across the fleet. Keep the three money domains distinct:

| Domain | Tools / command | Purpose |
|--------|-----------------|---------|
| Platform credit | `credit_balance`, `balance_topup_form` · also `/carrier:credits` | Carrier platform runway |
| Stripe Connect | `stripe_connect_status\|balance\|payouts\|dispute_list` | Operator payouts / disputes |
| Managed prepaid wallet | `wallet_*` · **`/carrier:wallet`** | Atlas prepaid drawdown (managed mode) |

- **events** → `billing_events` (recent charges, renewals, adjustments).
- **balances** → `credit_balance` (platform credit), `modify_subscriber_balance` / `modify_account_balance` for adjustments. Generate a customer-facing top-up with `balance_topup_form`.
- **thresholds / config** → `configure_billing` to set low-balance alerts and auto-renew behavior.
- **cost watch** → `high_cost_subscribers` to find the fleet's most expensive SIMs.
- **payouts (Stripe Connect)** → `stripe_connect_status`, `stripe_connect_balance`, `stripe_connect_payouts`, `stripe_connect_dispute_list`.
- **managed wallet** → do not use Connect or platform credit tools; use `/carrier:wallet` (`wallet_balance`, `wallet_topup_checkout`, `wallet_auto_topup`).

Any balance modification is money movement — state the exact amount, account, and direction, and confirm before executing. Never adjust a balance without explicit confirmation.