markdownMITTrust: scannedUsed 3×

Security policy webhook verification

Documentation of general webhook signature verification and security best practices, reusable and benign.

Money path — what to verify before you trust it

Generated billing/webhook handlers routinely ship without an idempotency guard or signature timing-safety, so a single replay can double-charge or double-credit. Check that this card verifies the signature and is safe to replay before you rely on it.

Preview

7 lines
// aperçu protégé · markdown · 7 lignes

7 more lines are delivered on retrieval, with the full verified card and its proof receipt.

What you get on retrieval

  • · The complete verified implementation, written to bytes by the MCP tool (near-zero output tokens).
  • · A proof receipt: source provenance, review status, license state and estimated savings.
  • · Revocation coverage — if a security fix lands on this primitive, retrievers are notified.
← Back to the full catalogue