Push · SMS · Email · Journeys

Reach users at the right moment

Payghaam is a multi-channel engagement platform — identify users via SDK, trigger journeys from events, and deliver push, SMS, and email with full delivery visibility.

3+
Channels
100%
Delivery log
4
SDKs
The old way
  • One vendor for push, another for email, a third for SMS
  • No shared user identity across channels
  • Silent failures — pushes fail and nobody knows why
  • Journey logic scattered in cron jobs and one-off scripts
With Payghaam
  • One platform for push (APNs + FCM), SMS, and email
  • Single subscriber profile — tags, events, subscriptions
  • Delivery dashboard with actionable error hints
  • Event-driven journeys with per-user ordering
See it in action
Platform capabilities

Everything to engage at scale

From SDK integration to delivery logs — one stack for product and growth teams.

Multi-channel push

Direct APNs on iOS and FCM on Android — no Firebase required on iOS. SMS via Twilio, email via SMTP.

Event-driven journeys

Graph automations with conditions on edges, wait steps as delayed jobs, and per-user FIFO ordering.

Tags & segments

Key/value tags on subscribers, mirrored to Redis for fast journey evaluation.

Delivery visibility

Every send logged with status and operator hints — apns misconfig, invalid tokens, FCM errors surfaced instantly.

Four SDKs

Flutter, React Native, native Android, and native iOS — plus a REST API for server sends.

Identity verification

Optional HMAC on external user IDs so clients can't impersonate other users.

How it works

From first SDK call to confirmed delivery in four steps.

01

Integrate the SDK

Add Flutter, React Native, or native iOS/Android. Call login() with your backend user id and register push tokens.

02

Track events & tags

Send behavioral events and user attributes. Journeys listen for triggers and evaluate segment filters in real time.

03

Send from server or UI

Broadcast with the REST API (include_external_user_ids) or automate via journey steps — push, SMS, or email.

04

Monitor deliveries

Dashboard shows sent, failed, and bounced with hints like apns_not_configured — fix channels without digging through logs.

Example — server send
POST /api/notifications
Authorization: Bearer ek_rest_...

{
  "include_external_user_ids": ["user-123"],
  "headings": { "en": "Order shipped" },
  "contents": { "en": "Your package is on the way." }
}

Built for shipping teams

We replaced three vendors with one API. Push failures show up in the dashboard with actual fix hints — not just 'error 403'.

Engineering lead
Mobile-first SaaS

The Flutter SDK took an afternoon. login(), requestPushPermission(), trackEvent() — done. Journeys handle the rest.

Full-stack developer
Consumer app

Per-user journey ordering was the killer feature. No more race conditions when users trigger multiple events quickly.

Platform engineer
Fintech

Ready to engage smarter?

Create a project, configure channels, and send your first push in under an hour.