Stripe Webhook Secret Regex Pattern

Detects a Stripe webhook signing secret (whsec_). Useful for leak-detection and secret scanning.

Pattern
^whsec_[A-Za-z0-9]{32,}$

Tested examples

whsec_AbCdEf0123456789AbCdEf0123456789
whsec_short
pk_test_AbCdEf0123456789AbCdEf0123456789

Test it live

Live Regex TesterJS
1 match
/
/g
whsec_AbCdEf0123456789AbCdEf0123456789
Match 1at index 0
whsec_AbCdEf0123456789AbCdEf0123456789

Use it in your language

Use it in
// JavaScript / Node.js
const regex = /^whsec_[A-Za-z0-9]{32,}$/;
const value = "whsec_AbCdEf0123456789AbCdEf0123456789";
const isMatch = regex.test(value);
console.log(isMatch); // true / false

// Extract all matches
const matches = value.match(/^whsec_[A-Za-z0-9]{32,}$/g) || [];

Tags

Frequently asked questions

How do I use the Stripe Webhook Secret regex pattern in JavaScript?
Wrap the pattern in slashes: const re = /^whsec_[A-Za-z0-9]{32,}$/; — then call re.test(value) to check a single value, or value.match(re) to find matches. The "Use it in" snippets above give you the exact code for 9 languages.
Is this stripe webhook secret regex production-ready?
Yes — every pattern in the library is tested against valid and invalid examples. Still, regex is one layer in a defense-in-depth strategy: pair it with server-side validation (e.g. Luhn for credit cards, mod-97 for IBAN, real DNS lookup for emails) for critical inputs.
Why does my pattern fail in another language?
Different regex engines (PCRE, Java, Python, Go's RE2) support slightly different syntax. The most common gotchas: lookbehinds (not in RE2), named groups syntax, and how backslashes need to be escaped inside string literals. The code snippets above already escape correctly for each language.
Can I edit this pattern and test it live?
Yes — use the live tester above. Type your test string and toggle flags (g, i, m, s, u, y) to see matches highlighted instantly, including capture groups.

Related patterns

See all Security

Browse the full library — 300 tested regex patterns across 16 categories.