Notifications
Configure notification preferences for in-app, email, SMS, and webhook alerts
Notifications
LYNKS provides a notification system that keeps users informed about important platform events through multiple channels. Users can configure their notification preferences to receive alerts via in-app notifications, email, and SMS based on their roles and responsibilities.
The notification system supports various scenarios including payment approvals, counterparty updates, user management events, and transaction status changes. Additional webhook integrations enable API users to automate processes based on platform events.
Prerequisites
Users must have the appropriate permissions to access and configure notification preferences.
Permissions
| Permission | Description |
|---|---|
USER_NOTIFICATION_PREFERENCE | Access and modify personal notification preferences |
In-app notifications
The notification bell icon provides quick access to all notifications related to pending actions and important platform events.

In-app notification panel accessed via the bell icon
In-app notifications appear in real-time and provide immediate visibility into events that require attention. The notification panel displays:
- Pending actions requiring user input
- Updates on items the user created or is involved with
- System notifications and reminders
- Status changes for payments and counterparties
To access in-app notifications:
- Locate the notification bell icon in the upper right corner of the screen
- Click the icon to open the notification panel
- Review notifications and click individual items to navigate to the relevant content
Configuring notification preferences
Users can customize which notifications they receive and through which channels based on their role and responsibilities.

Notification preferences configuration screen
To access notification preferences:
- Click on your name in the upper right corner of the screen
- Select Notification Preferences from the dropdown menu
- Configure preferences for each notification scenario by enabling or disabling channels
- Save changes to apply your preferences
Available channels
| Channel | Description |
|---|---|
| In-app | Notifications displayed in the notification panel within LYNKS |
| Notifications sent to the user's registered email address | |
| SMS | Text message notifications sent to the user's registered phone number |
Channel availabilityEmail and SMS channels must be enabled for your user account by an administrator. If these options are not visible in your preferences, contact your administrator to enable the communication channels.
Notification scenarios
Notification preferences are organized by category based on the type of platform activity. Users receive notifications based on their assigned permissions and roles.
Credit transfer notifications
| Scenario | Description | Default channels |
|---|---|---|
| Credit transfer waiting for authorisation | When payments are created and waiting for your signature | Email, SMS, In-app |
| Transaction authorised and waiting to be sent to bank | When payments you created are signed and ready for bank submission | In-app only |
| Transactions waiting authorisation for 24h | Reminder when payments await your signature for more than 24 hours | None (configurable) |
| Credit transfers pending execution by bank | When payments delivered to the bank have not been confirmed for more than 7 days | Email, SMS, In-app |
| Transaction rejected by a signatory | When payments you created were rejected | Email, SMS, In-app |
| Credit transfer cancelled | When payments were cancelled | None (configurable) |
| Credit transfers have not been executed | When payments failed at the bank | Email, SMS, In-app |
Standing order notifications
| Scenario | Description | Default channels |
|---|---|---|
| Standing order submitted and waiting for authorisation | When a standing order is created and waiting for your signature | Email, SMS, In-app |
Counterparty notifications
| Scenario | Description | Default channels |
|---|---|---|
| Counterparty created and waiting authorisation | When counterparties are created and waiting for your approval | Email, SMS, In-app |
| Counterparty authorised | When counterparties you created are approved | In-app only |
| Counterparty rejected | When counterparties you created were rejected | Email, SMS, In-app |
User management notifications
| Scenario | Description | Default channels |
|---|---|---|
| User created | When a new user is created | Email, SMS, In-app |
| User updated | When a user's details are modified | Email, SMS, In-app |
| User reactivated | When a deactivated user is reactivated | Email, SMS, In-app |
Role-based notificationsThe notification scenarios available to each user depend on their assigned permissions. Users only see notification options relevant to their role.
Resetting preferences
Users can reset their notification preferences to default settings for any category.
To reset notification preferences:
- Navigate to Notification Preferences
- Open the tab for the category you want to reset
- Click the Reset default notifications button
- Confirm the reset in the dialogue
The reset applies only to the currently selected tab, allowing users to restore defaults for specific categories while preserving custom settings in others.
Webhook notifications
For API integration and automation, LYNKS supports webhook notifications that trigger HTTP callbacks when specific events occur. Webhooks enable external systems to react to platform events in real-time.
Supported webhook events
| Event | Object type | Description |
|---|---|---|
| Payment processed by bank | Credit transfer | Payment successfully executed by the bank |
| Payment approved by signatories | Credit transfer | Payment received all required signatures |
| Payment failed | Credit transfer | Payment failed during processing |
| Payment rejected by bank | Credit transfer | Bank rejected the payment |
| Payment cancelled | Credit transfer | Payment was cancelled |
| Direct debit batch completed collection | Direct debit | Direct debit batch collection completed |
| Direct debit batch failed | Direct debit | Direct debit batch failed during processing |
| Direct debit batch rejected | Direct debit | Direct debit batch was rejected |
| Account statement received | Account statement | New bank statement received for an account |
Webhook payload
Webhook notifications are delivered as HTTP POST requests containing event details:
{
"id": "01946f4c-88e8-7dd4-8179-6bfc3b873e4e",
"event_object": "CREDIT_TRANSFER",
"event": "TRANSACTION_PROCESSED_BY_BANK",
"timestamp": "2025-01-16T14:30:00Z",
"data": {
"paymentId": "123"
},
"links": {
"self": "https://tenant.lynks.lu/v2/credit-transfers/123"
}
}Signature verification
Each webhook request includes an X-Signature-SHA256 header containing an HMAC-SHA256 signature for authenticity verification. Subscribers can verify webhooks by:
- Extracting the signature from the
X-Signature-SHA256header - Computing an HMAC-SHA256 of the request body using the shared secret
- Comparing the computed signature with the header value
Webhook setupWebhook configuration requires setup by Finologee's support team. Contact [email protected] to assess infrastructure requirements and configure webhook subscriptions for your tenant.
Configuration
Notification channel availability is configured at the user level by administrators.
User notification channels
Administrators can enable or disable email and SMS notification channels for individual users through the User & Groups settings. Users can only configure preferences for channels that are enabled for their account.
For information on managing user notification channels, see User & Groups - User management and access configuration.
LYNKS mobile app notifications
Users with the LYNKS Mobile App enabled receive push notifications for signing requests directly on their mobile device. These notifications work alongside other channels and enable:
- Real-time push notifications for pending signatures
- Direct access to transaction approval from the mobile app
- Biometric authentication for signing
For information on the LYNKS Mobile App, see LYNKS Mobile App - Mobile authentication and push notifications.
Technical specifications
Notification channels
| Channel | Delivery method | Configuration |
|---|---|---|
| In-app | Real-time via web interface | Always available |
| SMTP delivery to registered address | Requires admin enablement | |
| SMS | Text message to registered number | Requires admin enablement |
| LYNKS Mobile App | Push notification | Requires app enablement |
| Webhooks | HTTP POST to subscriber endpoint | Requires support team setup |
Webhook specifications
| Property | Value |
|---|---|
| Protocol | HTTPS |
| Method | POST |
| Content type | application/json |
| Authentication | HMAC-SHA256 signature |
| Retry policy | Exponential backoff (1, 2, 4, 8 minutes) |
| Maximum retries | 5-8 attempts |
| Data retention | 1 year |
Related documentation
Explore related sections for more information:
- Support - Customer support portal and assistance - Customer support portal and assistance
- Action Center - Centralized task and approval management - Centralized task and approval management
- User & Groups - User management and access configuration - User management and notification channel configuration
- LYNKS Mobile App - Mobile authentication and push notifications - Mobile authentication and push notifications
Support
For assistance with notification configuration or webhook setup, contact [email protected].
Updated 3 days ago
