This Webhooks documentation outlines how Senang.io (“Senang.io”, “we”, “us”, or “our”) delivers real-time event notifications to approved partners and developers via webhook integration.
By enabling and using Senang.io webhooks, you agree to comply with our API Documentation, Integration Guides, and applicable platform policies.
1. Overview
1.1 Webhooks allow Senang.io to send real-time HTTP notifications to your system when specific events occur.
1.2 Webhooks eliminate the need for constant polling by automatically notifying your server of status changes.
1.3 Webhooks may be triggered for events including, but not limited to:
Payment success or failure
Policy or coverage issuance
Policy cancellation
Refund processing
Claim submission or claim status updates
Account or onboarding status updates
2. How Webhooks Work
2.1 When a subscribed event occurs, Senang.io will send an HTTP POST request to the webhook endpoint URL you provide.
2.2 The request will contain a structured payload (typically JSON format) including:
Event type
Event timestamp
Unique event ID
Related transaction or policy ID
Status and relevant metadata
2.3 Your system must acknowledge receipt of the webhook by returning a successful HTTP response code (e.g., 200 OK).
2.4 If your system does not respond successfully, Senang.io may retry delivery within a defined retry schedule.
3. Webhook Endpoint Requirements
3.1 You must provide a publicly accessible HTTPS endpoint.
3.2 The endpoint must:
Support secure TLS encryption
Accept HTTP POST requests
Process JSON payloads
Respond within the required timeout period
3.3 Your endpoint must be designed to handle duplicate webhook events safely.
4. Security & Signature Verification
4.1 To ensure authenticity, Senang.io may sign webhook payloads using a secret key provided to you.
4.2 You must verify the webhook signature before processing the event.
4.3 Webhook secret keys must be securely stored and never exposed in client-side applications.
4.4 Failure to implement signature verification may expose your system to security risks.
5. Event Types
5.1 Available webhook events may include (subject to your integration scope):
a.
payment.success
b.payment.failed
c.policy.issued
d.policy.cancelled
e.refund.processed
f.claim.submitted
g.claim.updated5.2 Senang.io may introduce additional event types from time to time.
5.3 Not all partners may have access to all event types.
6. Retry Policy
6.1 If your webhook endpoint fails to respond with a successful HTTP status code, Senang.io may retry delivery.
6.2 Retries may occur at increasing intervals for a limited number of attempts.
6.3 After the maximum retry limit is reached, the webhook event may be marked as failed.
6.4 It is your responsibility to monitor webhook failures and resolve endpoint issues promptly.
7. Idempotency & Duplicate Handling
7.1 Webhook events may be delivered more than once due to retries or network issues.
7.2 Each webhook event contains a unique event ID.
7.3 You must implement idempotency logic to ensure duplicate events do not cause duplicate processing (e.g., double issuance or duplicate database entries).
8. Testing Webhooks
8.1 Webhook functionality may be tested in the sandbox environment.
8.2 You should test:
Successful event delivery
Invalid signature handling
Endpoint downtime scenarios
Duplicate event handling
8.3 Sandbox webhook payloads are simulated and do not represent live production data.
9. Monitoring & Logging
9.1 You are responsible for logging webhook activity for troubleshooting and audit purposes.
9.2 Logs should include:
Event ID
Timestamp
Event type
Processing result
9.3 Sensitive data should not be stored in plain text logs.
10. Suspension or Misuse
10.1 Senang.io may suspend webhook delivery if:
Your endpoint repeatedly fails
Security vulnerabilities are identified
Webhooks are misused or abused
Integration breaches API or security policies
10.2 Reinstatement of webhook services may require corrective action and review.
11. Changes to Webhook Services
11.1 Senang.io may update webhook payload structure, event types, or retry policies from time to time.
11.2 Material changes will be communicated were reasonably practicable.
11.3 Continued use of webhooks constitutes acceptance of updated documentation.
12. Support
12.1 For webhook configuration support or technical inquiries, please contact:
Email: customercare@senang.io
12.2 When requesting support, provide:
Your partner ID
Event ID (if applicable)
Timestamp of issue
Sample payload (with sensitive data masked)