STRAX Reach · Alerts and push
Browser notifications with your own VAPID keys
Clients who manage their account in a browser can allow notifications once. After that, Reach can tell them about a completed payout or a failed debit order even when the portal tab is closed.
- Encrypted end to end
- Subscriptions kept in Reach
- Expired ones retired
Standard Web Push, managed inside your installation
Your portal asks the browser for permission and receives a push subscription. Your server hands it to Reach with the client's reference, and Reach stores it as that client's web push identity. The newest browser a client uses becomes the one Reach notifies.
Each notice is encrypted for that browser alone and signed with your VAPID key, following the Web Push standards. The payload carries a title, the text, the page to open and a tag so repeated notices about one conversation replace each other.
Push services report subscriptions that no longer exist. When that happens Reach retires the subscription, marks the message failed with the reason and opts the address out, so it never keeps sending into the void.
Where it helps
Payout notices for merchants
A merchant working in the portal learns that a settlement has been paid without refreshing the page.
Debit order warnings
Clients get a browser notice two days before a debit order runs on an account that looks short.
New reply alerts
When an agent answers a portal chat, the client sees a notice even if they moved to another tab.
What you need
-
A VAPID key pair
Generated once and stored in the credential vault; the public half goes into your portal page.
-
A service worker
A small script on your portal that shows the notification Reach sends.
-
Your portal back end
Posts each new subscription to the Reach subscription endpoint with a consumer key.
-
Reach Core
Holds the clients the subscriptions belong to.
Good to know
Each notice goes to the client's newest browser; sending to all of their browsers at once is planned. The subscription endpoint never creates clients, so upsert the client first.
Questions
Which browsers are supported?
Current Chrome, Edge, Firefox and Safari support Web Push, including Android browsers and home-screen web apps on iOS.
Can we change the VAPID keys later?
Existing subscriptions are bound to the public key, so a new pair means every browser must subscribe again.
What if a client blocks notifications?
The browser stops issuing the subscription, the push service reports it gone and Reach retires it.
How is this different from site notifications?
Sites notify their own signed-in members; this package serves subscriptions that Reach stores for any application.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Web Push to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 1 |
| Data table | 1 |
| Global variable | 2 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Web Push channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Web Push"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
Chrome, Edge, Firefox and Safari are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.