Payment & Event Notifications in IZI

Payment & Event Notifications in IZI

The Notifications section lets you define which channel receives which events — payments, new clients, and system alerts — and for which clubs. You pick a channel from your already-connected integrations (see Integrations overview), choose which clubs in your network should be covered, and tag the event types you care about. An empty Clubs field means all clubs in the organisation; an empty Types field means every supported event type. The rule takes effect immediately: as soon as a matching event occurs in IZI, the notification is dispatched to the selected channel. Find this section at Organisation → Management → Billing → Notifications.

For multi-club networks this is especially powerful: you can route one club’s events to its own chat, another club’s events to a separate chat, and system errors to a dedicated technical channel — keeping each stream clean. For context on how payments and providers work, see Payments and Providers.

---

Notifications Table

The section’s main screen shows a table of all created settings. Each row is one combination of channel + clubs + event types.

Column	What it shows
Channel	The integration name through which the notification is sent
Clubs	The selected clubs, or “All Clubs” if no filter was set
Notification Types	One or more event type labels; blank means all types

If no settings exist yet, the table shows an empty state with a prompt to add the first entry.

Supported Event Types

IZI supports four event types, combinable in any mix:

Event Type	When it fires
Successful Payment	A payment completes without errors
Failed Payment	A payment fails — acquirer error or cancellation
New Client	A new client is registered in the system
System Notification	A technical event at the platform level

---

How to Add a Notification Setting

1. Open Organisation → Management → Billing → Notifications.
2. Click Add in the top-right corner.
3. In the New Notifications modal, fill in three fields:
   • Channel — choose from the dropdown. The list is built from integrations connected to your organisation. If the list is empty, first add an integration in the Integrations section.
   • Clubs — select one or more clubs. Leave blank to cover all clubs in the organisation.
   • Notification Types — select one or more event types. Leave blank to receive notifications for all event types.
4. Click Add.

The new row appears in the table immediately. The setting starts working right away.

---

Editing and Deleting Settings

Edit: click any row in the table — the Edit Notifications modal opens with the same three fields. Change what you need and click Save.

Delete: click the trash icon on the right side of the row. A confirmation dialog appears showing the channel name. Click Delete — this action cannot be undone.

---

Routing Strategies for Multi-Club Networks

The notifications table is designed for layered routing: multiple rules can coexist, each handling a different slice of events.

Network-wide financial monitoring. Create one setting with no club filter and no type filter. All payment and new-client events from every club flow into one channel — useful for an owner or finance lead who needs full visibility.

Per-club separation. Create one setting per club, each pointing to that club’s manager channel. Club A admins see only Club A events; Club B admins stay in their own stream.

Technical monitoring. Create a setting for System Notification only and route it to a technical channel. Financial events go to their own channel without noise from platform alerts.

Failed-payment alerting. A setting scoped to Failed Payment only lets your team react to acquirer issues immediately — without the signal getting lost among successful transactions. For more on payment providers, see Providers.

---

Audit Trail

Every change to notification settings — creation, edit, deletion — is recorded in the Audit Log. This lets you trace who changed a notification configuration and when, which is useful if alerts unexpectedly stop arriving or land in the wrong channel.