Setup your webhooks

Klarna webhooks enable your applications to receive real-time business event notifications from the integrated Klarna product suite, allowing your backend systems to respond promptly.

Webhooks are customizable, and all Klarna APIs include a standard set of webhook events to which you can subscribe. For a list of supported event types, refer to the list of event categories listed in the Create and manage webhooks section below.

Consult the API reference for a complete description of the request body parameters.

To maintain seamless integration with Klarna's Payment Services and ensure your systems are equipped to handle Klarna notifications effectively, follow these steps:

• Expose an HTTPS endpoint on your server designed to receive webhook notifications.
• Ensure only HTTPS endpoints are used and that a valid SSL certificate is in place.

• Configure a single endpoint for multiple event types or set up separate endpoints for each event type based on your preferences.

• Verify HMAC Signature to ensure data security and integrity.
• See more info in the Create and manage signing keys section.
• Store the webhook event data for further processing. Sample webhook request

{
  "metadata": {
    "event_type": "event_type",
    "event_id": "unique event UUID",
    "event_version": "v2",
    "occurred_at": "2025-02-28T12:00:00Z",
    "subject_account_id": "Partner account ID",
    "recipient_account_id": "Acquiring Partner Account ID",
    "product_instance_id": "product-specific ID",
    "webhook_id": "webhook-specific ID",
    "live": "boolean"
  },

Immediately respond to webhook notifications with an HTTP status code of 200, 201, 202, or 204 to confirm successful delivery.

Failure to respond, or a response with any other status code, will trigger Klarna's retry mechanism.

Klarna will retry notifications at increasing intervals upon failure (timeout or HTTP 4XX/5XX response codes). Klarna orchestrates these retries with progressively longer delays, which can extend up to 12 hours or until a successful response is received.

Here's how the retry schedule is structured:

• First retry: 10 seconds after the initial failure.
• Second retry: 2 minutes later.
• Third Retry: 15 minutes later.
• If the issue persists, retries are scheduled at 3 hours, 6 hours, and finally 12 hours for the last attempt.

This structured approach ensures multiple opportunities for notifications to succeed, enhancing the reliability of the communication between systems.

If no successful response is received after the final retry attempt at 12 hours, the notification will be considered permanently failed.

If you resolve an issue on your end and need additional assistance to receive the previously failed notification, reach out to Klarna support.

When you modify webhook settings during ongoing retries, these changes will only apply to new notifications. If a triggered Klarna webhook fails to receive a response code of 200, 201, 202, or 204, it will continue to retry using the old configuration until it either successfully communicates or reaches the 12-hour retry limit.

To securely receive webhook notifications, you must  generate and attach signing keys to your webhooks. See createSigningKey for details.

This procedure ensures the authenticity of incoming notifications can be verified. Klarna will sign each notification using the designated signing key before dispatch. Both the signature and its identifier will be included in the notification, enabling you to confirm its validity. When configuring a new webhook, specify the signing key to be used.