Payments
Mollie Webhooks
European payment service provider. Receive events for payments, refunds, chargebacks, and settlements.
Connecting Mollie to Hookbase
Create a source in Hookbase first — it gives you an ingest URL to paste into Mollie. Then:
- 1Set the webhookUrl parameter to your Hookbase ingest URL when you create a payment (or other resource) via the Mollie API
- 2Mollie POSTs only the resource ID (id=tr_...) to that URL when its status changes
- 3Classic webhooks aren't signed, so leave the secret empty in Hookbase
- 4Fetch the resource from the Mollie API with your API key to get its current status
Signature verification
Mollie does not sign its webhooks with an HMAC scheme, so a signing secret on the source would have nothing to verify. Use a custom source with no secret, and keep the ingest URL itself hard to guess.
How Mollie secures them instead: Mollie's classic webhook (what this entry documents) posts only a resource ID (id=tr_...) and is not signed, so there is no secret to paste. Confirm each event by fetching it from the Mollie API with your API key. Mollie's separate Next-gen Webhooks (Dashboard → Developers → Webhooks) are signed, but this template doesn't verify them yet.
Mollie event types
5 of the events people route most often. Hookbase accepts every event Mollie sends, whether or not it is listed here.
payment.paid
Payment status became paid (classic body: id=tr_..., fetch it to see)
payment.authorized
Payment status became authorized
payment.failed
Payment status became failed
payment.expired
Payment status became expired
payment.canceled
Payment status became canceled
What a Mollie webhook looks like
A payment.paid payload. Hookbase stores the raw body exactly as it arrived, so this is also what you get back on a replay.
{
"id": "tr_7UhSN1zuXS"
}Start receiving Mollie webhooks
Create a source, paste the URL into Mollie, and watch the first event arrive. The free tier includes 1,000 events a month.
Get Started Free