Custom Account Notifications for Low-Latency Fraud Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing notification systems in financial institutions apply a uniform set of settings for various account activities, leading to latency and inefficiency in delivering pertinent notifications, particularly for potentially fraudulent activities, and lack communicative coupling with third-party systems.
Innovation Solution
A computing system that receives requests for account activities, determines notification policies based on user-defined settings, retrieves contextual information from third-party systems, and generates customized notifications with haptic and visual feedback.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a same set of notification settings is applied regardless of activity type, then system complexity is reduced, but notification effectiveness and fraud detection capability deteriorate
Solution Approach 1:
The notification system segments notification settings by activity type, creating separate notification policies for different account activities (e.g., login, transaction, fraud alert). Each activity type has its own customizable notification settings, allowing the system to send appropriate notifications for each activity without requiring a single complex unified configuration system.
Solution Approach 2:
The system applies local quality by customizing notification parameters (delivery method, timing, content) according to the specific activity type and associated risk level. High-risk activities like potential fraud receive immediate alerts with detailed information, while routine activities receive standard notifications, optimizing both security and user experience without uniform complexity.
2Device complexity
If notification systems are not communicatively linked to third-party systems, then system complexity is reduced, but notification latency increases
Solution Approach 1:
The system establishes communicative coupling with third-party systems in advance through pre-configured APIs and data exchange protocols. When account activities occur, the system can immediately retrieve relevant contextual information from linked third-party systems without establishing connections at notification time, thus reducing latency while maintaining manageable integration complexity through upfront setup.
3Ease of operation
If uniform notification settings are used for all activities, then ease of operation is improved, but personalization and user experience deteriorate
Solution Approach 1:
The notification system implements dynamic configuration where notification settings are not fixed but adapt based on activity type, user preferences, and risk assessment. The system automatically adjusts notification parameters such as delivery method (push, SMS, email), timing, and content details according to the specific activity context, providing personalization without requiring manual configuration for each scenario.
Data Source
AI summary
A computer-implemented method includes: receiving, by a computing system, from a first device, a request to perform an activity associated with an account of a plurality of accounts of a provider institution; determining, by the computing system, based on the activity, a notification policy based on a notification setting of the account associated with a user; transmitting, by the computing system, a request for information regarding the activity to the first device; receiving, by the computing system, information regarding the activity from the first device; generating, by the computing system, a data payload comprising the received information regarding the activity and initial information associated with the request to perform the activity; retrieving, by the computing system, an address associated with the account; and providing, by the computing system, a notification comprising information from the data payload to a second device associated with the user based on the retrieved address.