Missing a country or a custom check? Tell us what you need.Book a 15-min call

Webhook

A message a service sends to your server as soon as something happens, instead of you asking for updates.

A webhook is an HTTP request that a service sends to a URL you choose when an event occurs, for example when a verification finishes. Because anyone could send requests to that URL, good webhooks are signed, so your server can check they really come from the provider, and are retried if your server doesn't respond.

Webhooks and data protection under the nFADP and GDPR

A webhook moves data from a provider to your systems, so it is part of the processing you have to secure under the nFADP and the GDPR. Keep personal data out of notifications where you can: a webhook that only says a verification has finished, with an ID, exposes little if a request goes astray. Your server then fetches the details it needs through an authenticated API call.

Use HTTPS for the endpoint, verify the signature on every request and reject anything that fails. Log what you receive for your records, but don't keep it longer than your retention rules allow.

Handling webhooks reliably

  • Verify the signature over the raw request body before parsing it.
  • Answer quickly with a 2xx status and do slow work afterwards, so the provider doesn't time out and retry.
  • Store event IDs and skip events you've already processed, since retries can deliver the same event twice.
  • Don't rely on the order in which events arrive; read the current state if order matters.

How secuveri handles it

secuveri sends a webhook when a verification finishes or is reviewed. Each request is signed with HMAC-SHA256 in the secuveri-signature header and retried for about 21 hours if your server doesn't accept it.

Frequently asked questions

What is the difference between a webhook and polling an API?
With polling, your server asks the API for updates at intervals, which wastes requests and adds delay. With a webhook, the provider tells you as soon as something happens. Many integrations combine both: the webhook triggers the update, and an occasional API call catches anything missed while your server was unavailable.
What happens if my server is down when secuveri sends a webhook?
secuveri retries the webhook 7 times over about 21 hours if your server doesn't accept it, and each event has an ID so you can drop duplicates. If your server is down for longer, read the outcome from the API. The signed result contains no personal data and can be verified with secuveri's public keys.
How do I verify a secuveri webhook?
Each request carries an HMAC-SHA256 signature in the secuveri-signature header. The @secuveri/node client includes webhook signature checks, or you can follow the public API reference to check the signature yourself. An open-source webhook receiver is among secuveri's example apps on GitHub, which you can use as a starting point.
Contact

Talk to us

Tell us what you’re trying to verify. We’ll show you how secuveri can fit your workflow.

We reply within one business day and use your details only for your inquiry. See our privacy policy.