BursaPay Logo
Knowledge Base
Ticket Sign In
Help Center > Developer Platform & Gateway API > Webhook HMAC Signature Verification

Webhook HMAC Signature Verification

Published 2026-08-24 5 min read
Who is this article for?
This guide is for Developers, Engineering Teams, Platform Operators seeking operational guidance on BursaPay workflows.

UI Navigation Path (Step-by-Step)

  1. Read the signature header and timestamp.
  2. Reconstruct the signed message using the documented payload format.
  3. Calculate the HMAC with the stored webhook secret.
  4. Reject payloads with an invalid signature or stale security context.
Verified BursaPay workflow: Verify BursaPay webhook signatures before trusting incoming event data.

1. Overview & Purpose

BursaPay signs webhook payloads and exposes the timestamp/signature information needed for application-side verification.

2. Requirements & Setup

The webhook secret returned when the endpoint is created must be stored server-side.

3. Step-by-Step Workflow

  1. Read the signature header and timestamp.
  2. Reconstruct the signed message using the documented payload format.
  3. Calculate the HMAC with the stored webhook secret.
  4. Reject payloads with an invalid signature or stale security context.

4. Rules & Troubleshooting

Never log or expose the webhook secret. Treat an invalid signature as untrusted input.

5. Verification & Next Steps

Record successful verification status in your own webhook processing logs.

Was this article useful?

Related Articles

Webhook Endpoint Creation and Event Subscriptions Webhook Event Modes and Versioning
Ask Bursa AI