Wallet and billing: prepaid credits, top-ups, auto-recharge

Call2Me bills via a prepaid wallet. You add credits, you spend them on voice minutes and chat messages, you top up when you're low. No contracts, no monthly minimums, no surprise invoices.

Where it lives

The wallet is at the workspace level — not per-user, not per-agent. Every call placed by every member of the workspace draws from the same balance.

View it: dashboard → top-right → Wallet, or via API:

Copycurl https://api.call2me.app/v1/wallet/balance \
  -H "Authorization: Bearer YOUR_API_KEY"

Returns:

Copy{
  "balance_usd": 47.23,
  "has_balance": true,
  "can_proceed": true,
  "min_balance": 0.01,
  "margin_percent": 30
}

can_proceed is the field to check before placing a call — it accounts for the minimum balance the platform holds back. margin_percent is returned on every account (the platform margin, currently 30).

For usage breakdowns and history, use GET /v1/wallet/summary and GET /v1/wallet/transactions.

Topping up

Three ways:

1. Dashboard — Wallet → Add Funds → enter amount → pay on the card payment page (iyzico)
2. API — POST /v1/payments/checkout with {amount, currency, save_card}; returns the provider and its checkout details (checkout_url of the iyzico payment page)
3. Auto-recharge — fires automatically when balance crosses your threshold

For one-off top-ups, the dashboard is the path of least resistance.

Auto-recharge

The setup that keeps calls running when the balance gets low:

• Threshold: when balance drops below this, recharge fires
• Top-up amount: how much to add each time
• Card on file: required for auto-recharge to work

Setting threshold to ~10% of your weekly burn rate is typical. Setting it too low risks calls hitting 402; setting it too high front-loads spend you might not need.

Disable any time from Wallet → Auto-recharge → off.

Via API: GET /v1/payments/auto-charge and PUT /v1/payments/auto-charge with {enabled, threshold_usd, charge_amount_usd}.

Where charges show up

Every billable event creates a wallet transaction:

The dashboard's Wallet → Transactions view shows every event with the call/chat/number it ties to.

What 402 Payment Required actually means

When you place a call (POST /v1/calls) and the wallet is below the per-call buffer, the platform returns:

CopyHTTP/1.1 402 Payment Required
{"detail": "Insufficient balance"}

Top up, then retry. If auto-recharge is enabled, this should be rare.

The free credit

New workspaces get $5 in credits at signup. That's roughly:

• 50 minutes of voice base ($0.10/min)
• about 45 minutes of answered inbound phone calls ($0.11/min), about 35 minutes outbound ($0.14/min)
• 500 chat messages ($0.01 per user + assistant pair)

Use the credit to test, then add a payment method and top up when you're ready for production.

What's next

• Pricing — what each minute and message actually costs
• Errors & rate limits — 402 retry semantics
• Calls — the per-call cost calculation