Skip to content
YepstaYepsta Help Centre

Buy and Monitor Notification Credits

Notification credits fund supported paid-channel sending. The Credits tab shows the current wallet, approximate per-message cost, warning thresholds, purchase history and usage ledger.

Check balance and usage

Section titled “Check balance and usage”

Open Communication → Notification Centre → Credits. Review:

  • the WhatsApp balance and approximate credits per message;
  • the low-balance warning;
  • credit, refund, adjustment and debit entries;
  • balance after each entry and its related channel;
  • purchase status and available invoice action.

SMS wallet information can appear, but SMS sending is disabled. Email is included and does not consume notification credits.

What consumes credits

Section titled “What consumes credits”

Supported paid sending includes transactional WhatsApp notifications. Campaign 2.0 also checks and debits notification credits per eligible recipient when the owner has enabled Campaign 2.0 enforcement. Manual text replies sent from WhatsApp Inbox do not consume notification credits.

The displayed rate and available packages are configured by Yepsta and can change. Use the current values shown in your workspace rather than planning from an old receipt or screenshot.

Purchase credits

Section titled “Purchase credits”
Complete a credit purchase
  1. On the Credits tab, review the current package cards and choose one.
  2. Confirm the credits, price and applicable GST shown at checkout.
  3. Continue through Razorpay and complete payment.
  4. Return to Yepsta and wait for the purchase status and wallet balance to update.
  5. Open the invoice for a paid purchase when needed.

If online checkout is not configured, the screen directs you to Yepsta instead. Do not transfer funds using payment details received from an unverified message.

Failed and skipped messages

Section titled “Failed and skipped messages”

Yepsta debits a paid message before its provider attempt. If no provider message is created, that debit is restored and appears as a refund entry. If the provider accepted the message and delivery later fails, the UI does not promise a refund.

A message can be skipped before debit when the provider, template, destination or credits are not ready. Review the related log instead of repeatedly triggering the same event.

Last reviewed: