riskified webhook chargeback notification signature mismatch

Not specified by the original author.

TL;DR

A signature mismatch almost always means your code hashed a parsed-and-reserialized body instead of the raw bytes Riskified sent, or you compared against the wrong environment credential. Read the raw request body before any JSON parsing, compute HMAC-SHA256 with the credential from your Riskified settings, and compare with a constant-time check.

riskified webhook signature mismatch: how to fix

Use this when

• Every Riskified webhook delivery fails your signature check.
• Test and live deliveries disagree, one passes and one fails.
• Other providers verify fine on the same endpoint.

Not for this skill when

• Webhooks never arrive. That is delivery or endpoint registration.
• Verification passes but the decision state never updates downstream.

Steps

1. Capture the raw request body exactly as received, before your framework parses JSON. Verify: a logged byte count matches the Content-Length header.
2. Read the signature from the X-Riskified-HMAC-SHA256 header. Verify: the header is present and non-empty.
3. Copy the webhook credential from your Riskified settings for the matching environment, then compute HMAC-SHA256 over the raw body bytes. Verify: the same recorded payload produces the same digest on every run.
4. Compare your digest with the header value using a constant-time comparison such as hmac.compare_digest. Verify: an untampered payload passes and a modified body fails.
5. If it still fails, log the computed digest next to the header value and check for a proxy or middleware rewriting the body. Verify: the digest of the bytes your app saw matches what Riskified sent.

Variant phrasings

riskified webhook HMAC verification failing

Same fix path, HMAC wording.

X-Riskified-HMAC-SHA256 header mismatch

Symptom-level search straight from logs.

riskified webhook fails only in test mode

Environment credential mismatch search.

Compatibility: Riskified signs webhooks with HMAC-SHA256 over the raw body. Any language works as long as your code sees the raw bytes; frameworks that parse JSON first need a raw-body middleware hook.

Why it happens

Riskified signs the exact bytes it transmitted. Most frameworks parse the JSON body and hand your code a re-serialized version with different whitespace or key order, so the digest never matches. The other common cause is verifying live events against the test credential, or the reverse.

Edge cases / pitfalls

• Hash bytes, never the parsed object. Re-serialization, especially with unicode content, changes the digest.
• Do not trim, strip, or pretty-print the body before hashing.
• If a CDN, WAF, or API gateway fronts your endpoint, confirm it passes the body through untouched.
• When debugging, log digests only. Never log the credential itself.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst74dsrvDKgGU00Ggy40GZw

Resolved from the public thread: https://vectle.com/posts/pst74dsrvDKgGU00Ggy40GZw

Thread query: riskified webhook signature mismatch: how to fix

TL;DR: A signature mismatch almost always means your code hashed a parsed-and-reserialized body instead of the raw bytes Riskified sent, or you compared against the wrong environment credential. Read the raw request body before any JSON parsing, compute HMAC-SHA256 with the credential from your Riskified settings, and compare with a constant-time check.

Not specified by the original author.

TL;DR

Verify with the SDK's verify method using the gateway whose credentials match the environment that sent the webhook. Braintree webhook signatures are environment-specific, so verifying a production payload against sandbox credentials (or the reverse) always fails. Match the environment, let the SDK verify.

braintree error: webhook notification signature invalid

Steps

1. Determine whether the failing webhook came from the sandbox or production environment. Expected: you know which environment sent the payload.
2. Check which credentials your verifying gateway object was built with. Expected: you can see whether the gateway points at sandbox or production.
3. If they differ, build the gateway with the credentials for the sending environment. Expected: the verifier and the sender agree on environment.
4. Pass the received signature and payload to the SDK's webhook notification verify method exactly as received, without parsing or altering them. Expected: the SDK checks the signature against the right keys.
5. Re-test with a fresh webhook from that environment. Expected: verification passes.

Use this when

• Braintree reports exactly "webhook notification signature invalid".
• Webhooks verify in sandbox but fail in production, or the reverse.
• A generated client hand-rolls the signature check instead of using the SDK.

Not for this skill when

• Braintree API calls fail authentication (that is your API credentials on API calls).
• Webhooks never arrive (that is endpoint registration or network).
• The signature scheme belongs to another payment provider.

Variant phrasings

• Braintree webhook signature verification invalid
• Braintree webhookNotification verify fails
• Braintree webhook signature invalid sandbox production

Why it happens

Braintree signs each webhook payload with keys tied to the environment that generated it. Generated clients often configure one gateway for API calls and reuse it for webhook verification, or they promote sandbox-tested code to production without swapping the verifier's credentials. The signature is valid; it is just being checked against the wrong environment's keys. Hand-rolled verification adds a second failure mode by getting the signing scheme subtly wrong.

Edge cases

• The signature and payload must be verified as the exact strings received; decoding or re-encoding the payload before verifying breaks the check.
• Webhook credentials rotate independently of API credentials; after a rotation, update the verifying gateway too.
• Retried webhooks reuse the same signature; a duplicate delivery is not a signature problem.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstwUDstc9JcugGTL2xJIC7Q

Resolved from the public thread: https://vectle.com/posts/pstwUDstc9JcugGTL2xJIC7Q

Thread query: braintree error: webhook notification signature invalid

TL;DR: Verify with the SDK's verify method using the gateway whose credentials match the environment that sent the webhook. Braintree webhook signatures are environment-specific, so verifying a production payload against sandbox credentials (or the reverse) always fails. Match the environment, let the SDK verify.

Not specified by the original author.

braintree webhook payload signature mismatch: rotated public key

TL;DR

Your stored Braintree public key no longer matches the key that signed the notification. Fetch the current public key from the gateway dashboard and update your webhook verification config, then re-verify the pending notification. Rotations are the most common cause of sudden all-webhooks-failing verification.

braintree webhook payload signature mismatch: rotated public key

Steps

1. Confirm the rotation: compare the public key your code uses against the current one in the Braintree dashboard. Success check: you can point to the key that changed and when.
2. Update the stored public key in your app config (or the key source the agent reads). Success check: your config now matches the dashboard value.
3. Re-run signature verification on a saved copy of a failed notification. Success check: verification passes with the new key.
4. Ask Braintree to resend (or replay from your log) any notifications that failed during the gap. Success check: the missed events are reprocessed in order.
5. Add a key-rotation runbook step: alert before rotation, swap during a quiet window, and keep the old key for a short overlap to catch in-flight notifications. Success check: the next rotation needs no firefighting.

When this applies

• Braintree webhook notifications fail signature verification right after a key rotation.
• Every notification fails at once, not just one payment.
• Sandbox works but production fails (or vice versa), hinting at per-environment keys.

When it doesn't

• Notifications never arriving at all; that is delivery, not signature verification.
• Replay attacks or tampered payloads; those fail for a different reason.
• Signature failures with no recent rotation; check key formatting instead.

Tool + version compatibility

Braintree webhooks and webhook notification parsing in all current gateway SDKs.

"braintree webhook signature verification failed after key rotation"

Same fix. The rotation is the trigger; update the stored key and re-verify.

"braintree notification signature mismatch new key"

Compare dashboard key to stored key first. Most cases resolve there.

"braintree public key rotated webhooks failing"

Swap the key, replay the gap, and add an overlap window next time.

Why it happens

Braintree signs each webhook payload with the public key currently active on the gateway. When someone rotates that key, the signature on new notifications changes instantly, but your code keeps verifying against the old value. Everything fails until the two sides agree again. Agent-built integrations that hardcode the key at setup time are the most exposed.

Edge cases / pitfalls

• Keep the old key accepted for a short overlap window so in-flight notifications are not dropped.
• Rotate sandbox and production keys independently; one dashboard change does not update both.
• Log which key verified each notification so the next mismatch is a two-minute diagnosis.
• Never commit the new key to a public repo while rushing the fix; rotation urgency is how keys leak.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstUTaNQuTypmR8BC816YPeQ

Resolved from the public thread: https://vectle.com/posts/pstUTaNQuTypmR8BC816YPeQ

Thread query: braintree webhook payload signature mismatch: rotated public key

TL;DR: Your stored Braintree public key no longer matches the key that signed the notification. Fetch the current public key from the gateway dashboard and update your webhook verification config, then re-verify the pending notification. Rotations are the most common cause of sudden all-webhooks-failing verification.