Billing Wallet Top-up and Payment Methods

Summary

Wallet liquidity is critical for uninterrupted AI and subscription operations. This guide explains top-up and payment method setup flows. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Add funds without validation errors.
• Prepare payment method for auto-billing.
• Maintain minimum operating balance.

Before you start

• Minimum top up is $5.
• Starter activation needs at least $20 equivalent in wallet context.
• Choose card path when crypto backend is unavailable.

Step-by-step workflow

1. Open Billing Overview.
2. Choose preset amount ($50/$100/$250/$500) or custom amount.
3. Validate amount and start recharge flow.
4. Complete checkout and return to billing.
5. If needed, open Add payment method setup flow.
6. Confirm wallet balance updates after completion.

Key states and error handling

• Validation errors: 'Enter a valid amount.' and 'Minimum top up is $5.'
• Top-up failure fallback: 'Unable to start top-up'.
• Crypto notice: 'Crypto top-ups will be enabled after wallet backend is connected.'

Best practices

• Use presets for faster low-risk funding.
• Keep a payment method configured before high-volume periods.
• Avoid running close to minimum balance during campaigns.

Troubleshooting

• If top-up fails, retry with preset amount.
• If payment setup fails, retry setup-payment-method flow from billing.
• If balance does not update immediately, refresh and re-open overview tab.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Overview tab shows wallet balance and funding controls.
• Subscriptions tab applies plan changes per bot.
• History tab supports status/type filtering for financial audits.
• Information tab provides policy context and operational reminders.
• Top-up validation enforces minimum amount requirements.
• Auto-recharge requires payment method readiness and explicit settings save.
• Displayed plan pricing is visible in UI and should guide operator expectations.
• Billing toasts are primary diagnostics for top-up and subscription failures.

Operator checklist (before shipping changes)

• Keep wallet above safety margin before high-volume campaigns.
• Validate bot selection before changing subscription tier.
• Use preset top-up values when rapid funding is required.
• Enable auto-recharge only after payment method is confirmed.
• Review history filters weekly for anomaly detection.
• Re-test Bots/Fan Inbox behavior after major billing actions.

Real-world scenario

AI actions stop during a high-traffic period. The operator finds low wallet balance, tops up using a preset amount, confirms subscription health per bot, and verifies inbox composer availability returns immediately.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.