Skip to content
FluxusDocs
Fluxus DocumentationFluxus Documentation

Push Notifications

Push notificationsPush notifications

Fluxus can send browser push notifications so you know about incoming payments, requests, and .pay name expiry without keeping the tab open. Notifications go through the Web Push standard via a service worker and are delivered by your browser’s push infrastructure.

How to enable

1

Open notification settings

Navigate to Settings → Notifications from the app menu, or go directly to /app/settings/notifications. The page is only visible when the push notification feature flag is active.

2

Click Enable

Your browser prompts you to allow notifications. Fluxus requests the minimum permission scoped to this origin.

3

Confirm the browser prompt

Once you allow, the app subscribes via the Web Push API using a VAPID public key and registers that subscription with the Fluxus backend.

4

Stay subscribed

The subscription is stored server-side and associated with your wallet address. You can turn notifications off at any time from the same Settings page.

Notification types

  • Payment received. Fires after a successful incoming transfer lands on-chain.
  • Payment request. Fires when someone sends you a payment request link and the payer completes it.
  • Stream completed. Fires when a streaming payment you initiated finishes all ticks naturally.
  • Name expiring. Fires once per session when one of your .pay names expires within 30 days.

All notification types are toggled together. Per-type controls are not available yet.

Technical details

  • Service worker. A service worker at /sw.js handles incoming push events and displays notifications even when the tab is closed.
  • VAPID. The subscription uses a VAPID key pair. The public key is exposed via NEXT_PUBLIC_VAPID_PUBLIC_KEY. The private key lives server-side only.
  • Subscription store. Active subscriptions persist in Upstash Redis under a per-address key. Unsubscribing or switching devices removes the old endpoint.
  • Feature flag. Push notifications are gated behind NEXT_PUBLIC_FF_PUSH_NOTIFICATIONS=1. Both the flag and the VAPID public key must be set for the settings page to show the Enable button.

Delivery is best-effort: Web Push delivery depends on your browser vendor’s push service. Notifications may be delayed or dropped if the browser is offline or if the push service is unavailable. Fluxus does not guarantee real-time delivery.