Implementation Guide
Notification Setup
Configure SMS, email, push notification, and webhook channels with customizable templates.
The M2P Platform supports multi-channel notifications for transaction alerts, security events, and system callbacks. All templates are configurable per tenant.
Notification Channels
| Channel | Use Cases | Configuration Required |
|---|---|---|
| SMS | Transaction alerts, OTP delivery, card status updates | SMS gateway credentials provided by your organization |
| Statements, welcome emails, card dispatch notifications | SMTP configuration or M2P-managed delivery | |
| Push (FCM) | Real-time in-app notifications | Firebase project credentials |
| Transactional alerts | WhatsApp Business API credentials | |
| Webhooks | System-to-system event callbacks | Your HTTPS endpoint URL |
Notification Events
Template Configuration
Notification templates use dynamic placeholders that are automatically populated at the time of delivery.
Example: Transaction Alert Template
Dear {customerName}, your {cardType} card ending {last4} was used for
{txnType} of {currency} {amount} at {merchant}.
Balance: {currency} {balance}. Ref: {txnRefNo}.
If not you, call {helpline}.Available Placeholders
| Placeholder | Description | Example Value |
|---|---|---|
{customerName} | Customer's registered name | Jane Smith |
{last4} | Last 4 digits of card number | 1234 |
{amount} | Transaction amount | 5,000.00 |
{currency} | Currency code | INR |
{merchant} | Merchant name | Online Store |
{txnRefNo} | Transaction reference number | TXN20260306001 |
{balance} | Available balance after transaction | 15,000.00 |
{txnType} | Transaction type | DEBIT / CREDIT / REVERSAL |
{cardType} | Card type | Virtual / Physical |
{helpline} | Your program's helpline number | Configured per tenant |
Templates are configured by M2P during onboarding. To update templates, contact your M2P account manager with the new template text and placeholder requirements.
Webhook Configuration
Webhooks are the recommended channel for system-to-system integration. For detailed webhook setup, event types, payload formats, and signature verification, see the dedicated Webhook Guide.
| Setting | Description |
|---|---|
| Webhook URL | Your HTTPS endpoint URL (TLS 1.2+ required) |
| Webhook Secret | Shared secret for HMAC-SHA256 signature verification |
| Subscribed Events | List of event types you want to receive |
| Retry Policy | Automatic retry with exponential backoff (up to 5 attempts) |