Wallet

Prepaid organisation balance used to pay for accepted SMS.

  1. Docs
  2. Wallet

Each organisation has a prepaid wallet. When POST /v1/sms/send is accepted, Netnaunse debits the wallet by message segments × unit price and records a ledger transaction. Customer balances are a liability — not revenue.

Balance

GET /v1/wallet
curl https://api.netnaunse.com/v1/wallet \
  -H "Authorization: Bearer YOUR_TOKEN_OR_API_KEY"

Transactions

GET /v1/wallet/transactions
curl https://api.netnaunse.com/v1/wallet/transactions \
  -H "Authorization: Bearer YOUR_TOKEN_OR_API_KEY"

Returns ledger entries for top-ups and message charges. Use the dashboard Buy SMS flow for customer-facing top-ups.

Charges

  • Debit happens when the message is accepted (202), not when the handset receives it.
  • Segment count depends on language: 160 characters (English) or 70 (Unicode).
  • Insufficient funds → 402 with INSUFFICIENT_BALANCE.
Top-up APIPOST /v1/wallet/top-up exists for controlled/dev credit flows. Production customers should top up through the dashboard payment experience. Do not expose manual top-up to end users.

Related: SMS API · Errors