Introducing:

• New response options for webhooks to postpone our exponential backoff algorithm:
  • HTTP 429 Too Many Requests
  • HTTP 503 Service Unavailable

For more, please read about webhook delivery attempts: https://support.onlinefundraising.dk/hc/en-001/articles/5356624805916-Webhook-Delivery-Attempts

---

During 2026 we are improving our infrastructure and one element is our separation of webhook handling from the payment engine as previously announced: https://www.onlinefundraising.dk/developer/new-webhook-service/

The migration of webhook event types is still ongoing, but we expect it to be completed in September 2026.

The new webhook infrastructure allows batching of a configurable larger number of webhook payloads per webhook request, and an overall faster execution.

We understand some integrations are built to handle lower volumes at a slower pace and therefore introduce an option to respond with HTTP 429 or HTTP 503 with a Retry-After as described in our documentation.

Introducing:

• Additional IP addresses sending Payment and DataSet webhooks:
  • 63.182.150.245
  • 3.68.254.130
  • 3.126.194.213
  • 3.124.137.18

Integrators are encouraged to limit webhook requests from the IPs listed in this resource: https://info.onlinefundraising.dk/webhooks.json

Please check this at least once daily.

---

During 2026 Q2-Q3 we will gradually transition webhook event types to a new dedicated Webhook Service which will relieve the bottlenecks we have seen, which peaked in December 2025: https://status.onlinefundraising.dk/incidents/scxl4lwm38b6

For more, please see our documentation: https://support.onlinefundraising.dk/hc/en-001/articles/5356622578844-About-webhooks