Skip to content

Notify Service — Email & SMS Delivery Layer

Dev URL: https://notify.veropulse.com

Purpose

The Notify Service is a centralized messaging and notification layer used across the Tokenise ecosystem.

Instead of letting each service (Broker Core, KYC/Compliance, PayBlock, etc.) send emails or SMS messages on its own, all outbound messaging is handled by this dedicated service.

This design gives us:

  • consistent behavior and formatting across all outgoing messages
  • a single place to manage templates, delivery methods, and providers
  • better monitoring, logging, and auditability of notifications

Why Notify is a Separate Service

We intentionally separated notification logic from other services for several important reasons.

1. Different Messages May Need to Come From Different Sender Identities

Both Compliance (KYC) and Broker Core may need to send emails — but not always from the same sender.

Examples:

  • KYC emails may need to come from a VERO identity / address
  • Broker or trading emails may come from a Broker-specific address
  • Some users may interact with KYC flows through VERO apps without ever entering through the Broker UI

By handling sender identity in Notify:

  • each message can use the correct sender domain/account
  • logic is not hard-coded inside each service
  • identity rules remain flexible for future changes

2. Centralized Control Over Delivery Methods & Providers

Similar to PayBlock (for payments), Notify acts as a central hub for messaging.

Advantages:

  • Central place to configure email / SMS providers
  • Easier to switch or add new delivery methods without touching core services
  • Unified reporting, logs, and delivery tracking
  • Consistent retry and fallback behavior

3. Blacklist & Delivery Rules

Notify allows us to introduce:

  • blacklist rules
  • opt-out logic
  • recipient restriction policies

This is important for:

  • regulatory requirements
  • spam prevention
  • customer protection

Rules can be applied centrally instead of duplicating them across services.

4. Future GDPR Support

As the platform evolves, Notify will support GDPR-related features such as:

  • message retention and deletion policies
  • user communication preferences
  • fine-grained consent management across services

Having a central message layer simplifies compliance and auditing.

5. Backup & Failover for Email Delivery

Notify can be extended to support:

  • multiple email providers or SMTP gateways
  • fallback delivery if one provider is unavailable
  • automatic retry and routing strategies

This reduces the risk of message delivery failures and keeps notification reliability high.

Role in the Overall Architecture

Within the system:

  • Core services (Broker Core, PayBlock, Compliance, etc.) send notification requests to Notify.
  • Notify selects the appropriate sender identity, template, and delivery provider.
  • The message is delivered and logged centrally.

This ensures that messaging remains:

  • consistent
  • auditable
  • scalable
  • and independent from business logic in other services.