Receive webhook events

MONEI notifies your server when something happens to a payment, refund, or subscription — so you can fulfill orders, update your database, or send receipts without polling. There are two ways to receive these notifications.

Account webhooks

Account webhooks send every event you subscribe to, across all your activity. Configure them in Dashboard → Settings → Webhooks:

1. Add a webhook endpoint URL — an https:// URL on your server.
2. Select the event types you want to receive.
3. Enable it.

Add new webhook dialog in the MONEI Dashboard settings, with the endpoint URL and the events to send

You can add more than one endpoint — for example, one for payments and another for subscriptions. Each endpoint is listed with the events it receives and whether it is enabled.

Webhooks page in the MONEI Dashboard settings, listing the endpoints MONEI notifies

Each delivery is a JSON event envelope:

{
  "id": "evt_...",
  "type": "charge.succeeded",
  "object": {"id": "...", "status": "SUCCEEDED"}
}

Read type to know what happened, and object for the affected resource (a payment, refund, or subscription).

Payment callback (callbackUrl)

When you create a payment, you can set a callbackUrl. MONEI then sends the Payment object directly (not an envelope) to that URL when the payment reaches a final state — even if the customer closes their browser during the redirect. Use this when you only care about a specific payment's result.

See Verify signature for ready-to-use Node, PHP, and Python examples that handle the callback.

Event types

A charge is a payment, so charge.* events track the payment lifecycle.

Group	Events
Payments (charges)	charge.succeeded, charge.failed, charge.pending, charge.pending_processing, charge.authorized, charge.captured, charge.canceled, charge.expired, charge.refunded, charge.partially_refunded, charge.paid_out, charge.chargeback, charge.updated
Refunds	refund.succeeded, refund.failed, refund.pending
Subscriptions	subscription.activated, subscription.updated, subscription.canceled, subscription.paused, subscription.past_due, subscription.trialing, subscription.pending, subscription.expired

Retries

If your server doesn't answer 200 OK, MONEI tries again, waiting longer after each failure. There are 18 attempts spread over about three days — seconds apart at first, then minutes, then hours, with the last few 11 hours apart. A brief outage on your side costs you nothing, and a long one still leaves you most of a working week to fix it.

They are not endless. After the last attempt the event is given up on, and events are never queued for later delivery.

An endpoint is disabled only after seven days of failing with no success in between. A single successful delivery at any point resets that clock, so one bad endpoint doesn't switch off on a transient problem. When it does get disabled, MONEI emails your account admins and nothing reaches it until you turn it back on in Dashboard → Settings → Webhooks.

So don't treat delivery as guaranteed. Reconcile anything you might have missed by retrieving the payment rather than waiting for a webhook that may never arrive.

Verify every request

Every webhook and callback includes a MONEI-Signature header — an -SHA256 signature computed with your API key. Always verify the signature before trusting the payload, then respond with a 200 status to acknowledge receipt.

note

If you're a MONEI Connect partner, configure webhooks in the Partner Dashboard instead — see MONEI Connect for developers.