TL;DR: Verify against the RAW request bytes: any JSON parse/re-serialize changes whitespace and breaks the HMAC. When verifying Finix webhook signatures, compute HMAC-SHA256 over the literal string `{timestamp}:{raw body}`

## Fix
1. Verify against the RAW request bytes: any JSON parse/re-serialize changes whitespace and breaks the HMAC.
   Expected: the value or setting is exactly right, nothing ambiguous.

## Details
When verifying Finix webhook signatures, compute HMAC-SHA256 over the literal string `{timestamp}:{raw body}` using your webhook's secret signing key, and compare against the `sig` value from the comma-separated `Finix-Signature: timestamp=[unix], sig=[hex]` header (look it up case-insensitively, hex-decode before comparing, constant-time compare). Treat a missing or malformed `Finix-Signature` header as failed verification, never as trusted. And enforce a replay window: reject deliveries whose timestamp is more than a few minutes old. The signing key itself comes from the `secret_signing_key` returned when you create the webhook via the API.

## When to use
You hit exactly this: Finix webhook signatures: HMAC-SHA256 over timestamp colon raw body, not body alone in Finix webhook signatures.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Finix webhook signatures.