Skip to main content

Setting Up Webhooks & Event Subscriptions

RaiseNow provides a powerful webhook system to notify partner platforms of events in real-time — such as new transactions, subscription updates, payout status, and organisation events.

You can set up webhooks and event subscriptions directly in the Onboarding endpoint. Alternatively, you can also create webhooks and event subscriptions after you’ve connected an organisation using the RaiseNow API.

How Webhooks Work​

  1. You register a webhook.
  2. You add event subscriptions to the webhook.
  3. RaiseNow sends a POST request to your endpoint when the selected event occurs.
  4. Each webhook includes a payload and an HMAC signature to verify authenticity.

👉 More information in the webhooks documentation.

Supported Events​

Some common webhook events you may want to subscribe to:

Event NameTrigger
raisenow.payments.payment.succeededA new payment was created
raisenow.subscriptions.subscription.createdA new subscription was created
raisenow.organisations.organisation.approval_requestedAn org was submitted for approval
raisenow.organisations.organisation.approvedThe org was approved
raisenow.organisations.organisation.declinedThe org was declined

👉 Full list of supported events:
https://docs.raisenow.com/events

Security (HMAC Signature)​

All webhooks can be signed using HMAC. You define the key when registering the webhook. RaiseNow will include the HMAC signature in the X-Raisenow-Signature header, which you should verify on your server.

HMAC verification guide

How to Register a Webhook​

Use the following endpoint:

API Reference

Example Request​

POST /organisations/webhooks
Authorization: Bearer {your_access_token}
Content-Type: application/json
{
    "organisation_uuid": "OrganisationUUID",
    "account_uuid": "AccountUUID",
    "endpoint": "https://your-url.com/url-webhook"
    "alias": "My Endpoint",
    "username": "yourUser",
    "password": "myPassw0rd",
    "hmac_key": "someSecretString"
}

How to Subscribe to an Event​

Use the following endpoint:

API Reference

Example Request​

POST /organisations/event-subscriptions
Authorization: Bearer {your_access_token}
Content-Type: application/json
{
    "organisation_uuid": "OrganisationUUID",
    "account_uuid": "AccountUUID",
    "action_configuration_uuid": "WebhookUUID", //uuid of the webhook
    "event_name": "raisenow.payments.payment.succeeded",
    "action_type": "webhook",
    "filter": "",
    "enabled":true
}

Managing Webhooks​

You can list, update or delete webhooks using the following endpoints:

  • GET /webhooks
  • PATCH /webhooks/{webhook-uuid}
  • DELETE /webhooks/{webhook-uuid}

See the Webhook API for full details.

You can list, update or delete event subscriptions using the following endpoints:

  • GET /event-subscriptions
  • PATCH /event-subscriptions/{event-subscription-uuid}
  • DELETE /event-subscriptions/{event-subscription-uuid}

See the Event Subscriptions API for full details.

Best Practices​

  • Always validate HMAC to ensure requests come from RaiseNow
  • Log all incoming events for traceability and debugging
  • Use retry logic: RaiseNow will retry failed deliveries for a period of time