Webhook sending classic data but next-gen when testing

[next rover]

I'm currently trying to implement my payment workflow, when I created a webhook in the dashboard it will test with either no body(pressing save in the webhook create/update page), or it sends me (test button in the webhook overview page)
⁨```json
{
"resource": "event",
"id": "event_...",
"type": "hook.ping",
"entityId": "hook_...",
"createdAt": "2026-02-01T12:20:27.0Z",
"embedded": {
"entity": {
"resource": "hook",
"id": "hook...",
"links": {
"self": {
"href": "/v2/webhooks/hook...",
"type": "text/html"
},
"documentation": {
"href": "https://docs.mollie.com/guides/webhooks",
"type": "text/html"
}
}
}
},
"links": {
"self": {
"href": "https://api.mollie.com/v2/events/event_...",
"type": "application/hal+json"
},
"documentation": {
"href": "https://docs.mollie.com/guides/webhooks",
"type": "text/html"
},
"entity": {
"href": "/v2/webhooks/hook...",
"type": "text/html"
}
}
}

However whenever I receive a webhook I get the classic variant
⁨```form
id=tr_...
```⁩

How can I make the webhook use the next-gen? since I saw that classic is no longer recommended

Also, it doesn't register any other webhook event other than hook.ping, however when looking at the sales page it does show that the webhook has been called

[glossy mural]

The next-gen webhook systems doesn't support all events that the original version supports.
You can see here which events are supported: https://docs.mollie.com/reference/webhooks-new#event-types
Where did you see that the original webhooks are no longer recommended?

[next rover]

https://docs.mollie.com/reference/webhooks-new#classic-mollie-webhooks

⁨⁨payment-link.paid⁩⁩ seems supported on next-gen, but that isn't the same as paying through a link like https://www.mollie.com/checkout/credit-card/embedded/...?

[glossy mural]

Payment links are indeed a separate option, it's a long-lived URL, for example to put on an invoice: https://docs.mollie.com/docs/payment-links

[next rover]

So customer payment (with first-off sequence type) will still generate classic webhooks?

[glossy mural]

Hmm, the wording of that recommendation in the docs is a bit unclear. As I don't think it's really possible at the moment to fully migrate to next-gen

[glossy mural]

Correct! As far as I know that is

[next rover]

That was what puzzled me since I can get a variety of responses
⁨```
info: Program[0]
Received Mollie webhook: {"resource":"event","id":"... (rest of json)
info: Program[0]
Received Mollie webhook:
info: Program[0]
Received Mollie webhook: id=tr_...
info: Program[0]
Received Mollie webhook: ["Testing the webhook URL"]

[glossy mural]

I assume that is because you supplied the same webhookUrl while creating the payment as when you created the next-gen webhook?

[next rover]

yes, I thought that was necessary

[glossy mural]

Yeah I can see the confusion about that

@zealous cape do you think we can improve the documentation about this a bit? I'm not sure who best to involve in that.

[zealous cape]

@delicate pivot can you have a look and see if docs could be improved?

[frank vapor]

Hi @glossy mural can you elaborate further on how this is supposed to work?

If a webhook is provided as a parameter during the payment-link creation will it then always use old-school?

And how does it work for the test ping in mollie and specific the test mode?

my testmode webhook (new gen) seemed to be sendiung non-verified/signed items eventhough i had the signing secret created.

[glossy mural]

Sorry I don't really know many details, as I don't work in that area (or work at all today 😇), so I have to go based on the documentation as well.

But based on the documentation, it seems correct that passing a webhook via the POST /v2/payment-links is the classic webhook system.

How the next-gen system works I honestly don't know. But do you mean the X-Mollie-Signature header is missing?
Are you using on of our libraries? https://docs.mollie.com/docs/libraries

[frank vapor]

yes i am using the python library, and on testmode i am receiving hooks without the x-mollie-signature header. even the mollie dashboard test ping comes without it.

[zealous cape]

Hi @frank vapor I've pinged the responsible team to have a look into this. They will reply as soon as they can!