Notifications¶
GIB delivers event information to your team through two complementary systems:
- Webhooks — HTTP POST events delivered to your server in real time. The primary channel for any programmatic workflow.
- Notifications — email, SMS, and the dashboard inbox (bell icon), powered by GIB's notification infrastructure. The primary channel for human-in-the-loop oversight and mandatory alerts.
This page covers the notification system. For webhooks, see Webhooks.
Channels¶
| Channel | Best for |
|---|---|
| Human-in-the-loop oversight; backup for must-act events when no webhook covers them. | |
| SMS (beta) | Urgent alerts for critical events; supported countries listed in the phone number field in profile dialog. Opt-in only. |
| Dashboard inbox | Users who log into the dashboard regularly and want passive visibility into events (bell icon). |
Configuring notifications¶
Each User controls their own opt-in delivery from the in-app notification inbox: click the bell icon at the top of the dashboard, then click the gear icon to open notification settings. Toggle email, SMS, and dashboard inbox delivery per event type.
Note: SMS is opt-in for all workflows and is currently in beta. SMS is only available in select countries; check the phone number field in your profile dialog for the list of supported countries.
Notification schedules¶
Each User can set a notification schedule to control when they receive notifications. Schedules are managed individually by each user and configured via the bell icon in the dashboard.
Important: Optional non-in-app notifications will not be sent at all when outside of the configured schedule window. In-app and mandatory notifications are always delivered regardless of schedule settings.
To set or modify your notification schedule, click the bell icon at the top of the dashboard and access the schedule settings.
Event routing¶
Each notification type exists in one or both of two variants:
- Mandatory — always delivered; cannot be disabled.
- Optional — user-controlled. Items marked (default on) are enabled for all Users by default but can be disabled in notification settings.
Transactions¶
| Event | Mandatory | Optional |
|---|---|---|
| Transaction failed | Yes | Yes |
| Transaction canceled | Yes | Yes |
| Transaction under review | Yes | Yes |
| Transaction under review — decided | — | Yes |
| Return received (ACH / ICL / Wire) | Yes | Yes |
| ACH Notification of Change (NOC) | Yes | Yes |
| Wire IMAD / UETR confirmed | — | Yes |
Subclients¶
| Event | Mandatory | Optional |
|---|---|---|
| Subclient approved | — | Yes (default on) |
| Subclient rejected | Yes | Yes (default on) |
System¶
| Event | Mandatory | Optional |
|---|---|---|
| New release | — | Yes (default on) |
| Upcoming banking holiday | — | Yes (default on) |
Tasks¶
| Event | Mandatory | Optional |
|---|---|---|
| New task | — | Yes (default on) |
| Assigned task | — | Yes (default on) |
| Overdue task | — | Yes (default on) |
| Task reminder | — | Yes (default on) |
Mandatory notifications and the operations recipient¶
Mandatory notification types (marked above) are always delivered — they cannot be disabled in notification settings. GIB sends them to a designated operations recipient User via email and surfaces them in that User's dashboard inbox.
To set or change the operations recipient, contact your GIB team via your program's channel or email operations@gibank.com.
Related concepts¶
- Webhooks, programmatic real-time event delivery to your server
- Returns, ACH return and NOC events that trigger mandatory notifications
- Reconciliation, discrepancy alerts delivered via email and dashboard
- Companies & Users, who designates the operations recipient