Skip to main content
Account & Settings

Email notifications

Subscribe one or more email addresses to important account events; sales, refunds, disputes, payouts, integration alerts, low key-code inventory and failed license fulfillment.

Written By Tobias Lønnerød Madsen

Email notifications send Moonbase events to addresses you specify. You find them under Account settings > Notifications. You can route different event types to different addresses (for example, send disputes to your finance lead and integration alerts to your developer Slack relay) by configuring multiple subscriptions.

The Email notifications section with hello@acme.audio receiving payment disputes, integration alerts, payouts, low key codes and failed license fulfillment.

Subscriptions and destinations

Each subscription has one destination email address and a set of toggles for which event types it receives. You can configure up to 5 subscriptions, useful when different teams (finance, ops, support, devs) need different event mixes.

To add another subscription, click Add subscription and fill in the email plus the toggles. To remove one, click Remove on the corresponding card. There must always be at least one subscription.

Event types

  • Sale made: sent when an order completes or a subscription renews. Useful for revenue dashboards or just a feel-good "ka-ching" notification.

  • Payment disputed: sent when a customer files a chargeback or dispute with their card issuer. Time-sensitive: you typically have a short window to respond. At least one subscription must have this enabled. The form blocks save otherwise.

  • Purchase refunded: sent when you refund an order in Moonbase. Helpful for accounting reconciliation.

  • Voucher code redeemed: sent when a customer redeems a voucher code, so you can track redemption rate.

  • Integration alerts: sent when Moonbase switches off a connected integration because it failed, or pauses one of your automations. Route these to whoever maintains your integrations.

  • Payout transferred: sent when a payout is sent to your bank account, with the payout invoice attached. Pair with your bank's notifications for confirmation.

  • Key codes running low: sent when fewer than 5 key codes are left for a product, so you have time to upload more before customers can't activate.

  • License fulfillment failed: sent when your own license server, or iLok, would not issue a license and Moonbase has stopped retrying.

A new account starts with one subscription, its support email, with payouts, disputes, integration alerts, key codes and license fulfillment on, and sales, refunds and vouchers off. A subscription you add later starts with everything on. There is no alert for a failed subscription renewal or a failed order: watch Sales > Failed, or use webhooks.

All eight notification toggles switched on, from Sale made to License fulfillment failed.

Frequently Asked Questions

Use a Slack-by-email address as the destination. Most workspaces support this via Slack's email-to-channel feature.

Yes, that is the whole point of supporting multiple subscriptions. Each subscription has its own toggles.