> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexprice.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Low Balance Alert
> Configure Wallet Sentinel Alerts to get notified when a customer's wallet balance crosses configurable Info, Warning, or Critical thresholds.
Wallet Sentinel Alerts in Flexprice let you monitor wallet balance with **three alert levels** so you can act before balance becomes critical. You can enable or disable alerts per wallet and set a custom threshold and trigger condition for each level.
**Benefits:**
* **Proactive management** — Get notified at Info and Warning levels before balance reaches critical
* **Granular control** — Separate thresholds for informational, warning, and critical states
* **Flexible conditions** — Trigger when balance is above or below a value (e.g. "below" for low balance)
* **Per-wallet settings** — Enable or disable alerts and configure thresholds per wallet
## Alert Levels
| Level | Purpose |
| ------------ | ------------------------------------------------------------ |
| **Info** | Informational alert when balance crosses a defined threshold |
| **Warning** | Early warning level before critical |
| **Critical** | Critical alert level requiring immediate action |
Each level can be configured with:
* A **threshold value** (in the wallet’s currency, e.g. USD)
* A **trigger condition** (e.g. **below** — alert when balance is below the threshold).
Flexprice supports two conditions for thresholds: **Below** and **Above**.
Alerts are turned on or off for a wallet using **Enable Alerts** (`alert_enabled` in the API).
## Configuring Wallet Sentinel Alerts
* Go to **Billing** in the main navigation
* Select **Customers**, then the desired customer
* Open the **Wallet** tab in the customer profile
* Click the **three-dot menu (⋮)** in the top right corner of the wallet section
* Select **Alert Settings** from the dropdown
In the **Wallet Alert Settings** dialog, turn **Enable Alerts** **on** to activate monitoring against your configured thresholds
* Set **Critical**, **Warning**, and **Info** thresholds. For each level set **Threshold Value** and **Condition** (e.g. **Below** — alert when balance is below the threshold).
* Use **Remove** to drop a level you don't need.
* Click **Save Changes** to apply.
## Alert Behavior
Once configured and enabled, the sentinel will:
* **Monitor balance** — Evaluate wallet balance against your thresholds (e.g. after top-ups, debits, and accounting for usage)
* **Trigger by level** — Raise **Info**, **Warning**, or **Critical** alert based on which threshold is crossed
* **Update state** — Reflect current state (e.g. ok, info, warning, in\_alarm) on the wallet and in alert history
* **Notify** — Send webhooks when alert state changes
Webhooks are sent when alert state changes (e.g. ok → warning, warning → in\_alarm). Configure your webhook endpoint to receive these notifications.
## Managing Alert Settings
### Viewing Current Configuration
Open the customer’s **Wallet** tab, click the **three-dot menu (⋮)** → **Alert Settings**. The dialog shows **Enable Alerts** and all threshold levels (Critical, Warning, Info) with their values and conditions.
### Changing Thresholds or Condition
In the **Alert Settings** dialog box, adjust **Enable Alerts**, any threshold value, or condition per level, then click **Save Changes** to apply.
### Disabling Alerts
Set **Enable Alerts** to **off** in the **Alert Settings** dialog and click **Save Changes** (or set `alert_enabled` to `false` via API).
The wallet will no longer generate real time balance alerts until you enable them again.
## Use Cases
### SaaS and Usage-Based Billing
* **Low balance warnings** — Info at 5, Warning at 0, Critical below 0 so you can top up before going negative
* **Prepaid credits** — Notify when credits are running low at multiple levels to avoid running out of credits unexpectedly
* **Service Continuity**: Prevent service interruptions due to insufficient funds
### E-commerce Platforms
* **Wallet monitoring** — Different severities for different teams or workflows
* **Promotional or prepaid wallets** — Alerts when balance is low relative to typical usage
* **Payment Processing**: Ensure sufficient funds for transactions
### API and Credit-Based Products
* **Usage vs balance** — Early Info/Warning so support or automation can act before Critical
* **Multi-wallet** — Per-wallet sentinel settings so each wallet has its own thresholds
* **Rate Limiting**: Prevent service disruption due to insufficient credits
* **Customer Support**: Proactive customer communication
## Best Practices
💡 **Set realistic thresholds** — Choose values that give enough time to top up (e.g. Warning above zero if you want to avoid negative balance)
💡 **Use all three levels** — Use Info for early notice, Warning for action soon, Critical for immediate action
💡 **Match condition to goal** — Use **below** for “low balance” alerts; use **above** if you want alerts when balance exceeds a cap
💡 **Review periodically** — Adjust thresholds based on usage patterns and top-up behavior
💡 **Combine with auto top-up** — Use sentinel alerts together with auto top-up so critical levels can trigger automatic top-up when configured