Independent orchestration layer, not bundled middleware

It works alongside it, not instead of it. Fyno's SDK manages FCM for Android and APNs for iOS through a single integration. For logged-in users, the SDK opens a WebSocket connection that delivers notifications with sub-second latency. When the user closes the app or goes offline, push notifications deliver via FCM for Android or APNs for iOS. Same SDK, same bank-owned tokens. Your engineering team does not maintain separate integrations for each push service. Fyno handles token generation, device routing, and lifecycle management. If you deploy Fyno on-premise, every push token stays in your infrastructure and moves with you if you migrate away.

You configure a digest window per notification type. For UPI transaction alerts, the system collects all notifications within that window and delivers a single summary: "You received money from 10 transactions, total Rs 20,000." Urgent messages like OTPs and fraud alerts bypass digesting entirely and fire immediately. The window length, summary format, and bypass rules are all configurable per notification category. End-of-day PDF summaries are also possible, where Fyno batches the day's alerts and delivers one consolidated report.

Yes. The notification tray is fully white-labelled. You control colours, layout, typography, and interaction patterns. No Fyno branding appears anywhere in the user experience. For BFSI customers, this is a regulatory and trust requirement: end users should never see third-party branding inside a banking application. The SDK ships with default styles that you override during integration.

The system checks every outbound message against a configurable window. If a customer triggers an OTP and another request arrives within the active OTP's expiry window, Fyno blocks the duplicate and returns an explicit error code to your upstream system. This prevents both accidental duplicates from retry logic in your backend and intentional OTP abuse where attackers trigger bulk requests to exhaust SMS quotas. The window length and blocking behaviour are configurable per message type.

Most push notification setups handle delivery to offline devices well. They do not handle real-time in-app delivery to active users, unified batching across channels, cross-channel de-duplication, white-labelling, or token portability. Fyno adds a socket-based layer for instant delivery when users are in the app, digesting to reduce notification fatigue, duplicate blocking at the platform level, and a branded notification centre that looks native to your app. You also gain token ownership: with direct integrations through most tools, your push tokens are tied to the vendor's platform. With Fyno's on-premise option, tokens live in your infrastructure.

Yes. Fyno provides native SDKs for iOS and Android, plus a web SDK for browser-based applications. The SDK is lightweight and handles device detection, token assignment, and connection management automatically. Integration typically takes days, not weeks. The SDK works alongside your existing app framework without requiring architectural changes.

Fyno App Notifications and TOTP share the same SDK. When TOTP is enabled, the in-app notification layer doubles as an OTP delivery channel. OTPs appear inside your banking app's notification tray without touching the SMS network. This eliminates SIM swap and SS7 interception risks. Customers configure their preference to receive OTPs via in-app instead of SMS through Fyno's Preference Manager. For users who have not downloaded the mobile app, SMS OTP continues as a fallback through the same Fyno API.