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

PermissionDescription
USER_NOTIFICATION_PREFERENCEAccess 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:

  1. Locate the notification bell icon in the upper right corner of the screen
  2. Click the icon to open the notification panel
  3. 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:

  1. Click on your name in the upper right corner of the screen
  2. Select Notification Preferences from the dropdown menu
  3. Configure preferences for each notification scenario by enabling or disabling channels
  4. Save changes to apply your preferences

Available channels

ChannelDescription
In-appNotifications displayed in the notification panel within LYNKS
EmailNotifications sent to the user's registered email address
SMSText message notifications sent to the user's registered phone number
📘

Channel availability

Email 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

ScenarioDescriptionDefault channels
Credit transfer waiting for authorisationWhen payments are created and waiting for your signatureEmail, SMS, In-app
Transaction authorised and waiting to be sent to bankWhen payments you created are signed and ready for bank submissionIn-app only
Transactions waiting authorisation for 24hReminder when payments await your signature for more than 24 hoursNone (configurable)
Credit transfers pending execution by bankWhen payments delivered to the bank have not been confirmed for more than 7 daysEmail, SMS, In-app
Transaction rejected by a signatoryWhen payments you created were rejectedEmail, SMS, In-app
Credit transfer cancelledWhen payments were cancelledNone (configurable)
Credit transfers have not been executedWhen payments failed at the bankEmail, SMS, In-app

Standing order notifications

ScenarioDescriptionDefault channels
Standing order submitted and waiting for authorisationWhen a standing order is created and waiting for your signatureEmail, SMS, In-app

Counterparty notifications

ScenarioDescriptionDefault channels
Counterparty created and waiting authorisationWhen counterparties are created and waiting for your approvalEmail, SMS, In-app
Counterparty authorisedWhen counterparties you created are approvedIn-app only
Counterparty rejectedWhen counterparties you created were rejectedEmail, SMS, In-app

User management notifications

ScenarioDescriptionDefault channels
User createdWhen a new user is createdEmail, SMS, In-app
User updatedWhen a user's details are modifiedEmail, SMS, In-app
User reactivatedWhen a deactivated user is reactivatedEmail, SMS, In-app
📘

Role-based notifications

The 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:

  1. Navigate to Notification Preferences
  2. Open the tab for the category you want to reset
  3. Click the Reset default notifications button
  4. 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

EventObject typeDescription
Payment processed by bankCredit transferPayment successfully executed by the bank
Payment approved by signatoriesCredit transferPayment received all required signatures
Payment failedCredit transferPayment failed during processing
Payment rejected by bankCredit transferBank rejected the payment
Payment cancelledCredit transferPayment was cancelled
Direct debit batch completed collectionDirect debitDirect debit batch collection completed
Direct debit batch failedDirect debitDirect debit batch failed during processing
Direct debit batch rejectedDirect debitDirect debit batch was rejected
Account statement receivedAccount statementNew 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:

  1. Extracting the signature from the X-Signature-SHA256 header
  2. Computing an HMAC-SHA256 of the request body using the shared secret
  3. Comparing the computed signature with the header value
📘

Webhook setup

Webhook 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

ChannelDelivery methodConfiguration
In-appReal-time via web interfaceAlways available
EmailSMTP delivery to registered addressRequires admin enablement
SMSText message to registered numberRequires admin enablement
LYNKS Mobile AppPush notificationRequires app enablement
WebhooksHTTP POST to subscriber endpointRequires support team setup

Webhook specifications

PropertyValue
ProtocolHTTPS
MethodPOST
Content typeapplication/json
AuthenticationHMAC-SHA256 signature
Retry policyExponential backoff (1, 2, 4, 8 minutes)
Maximum retries5-8 attempts
Data retention1 year


Related documentation

Explore related sections for more information:



Support

For assistance with notification configuration or webhook setup, contact [email protected].