Stripe API Key Regex for PHP
/^(sk|pk|rk)_(live|test)_[0-9a-zA-Z]{24,}$/What this pattern does
This page provides a well-structured, multi-part regular expression for matching stripe api key, ported and verified for PHP. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.
Php Implementation
<?php
// Stripe API Key
// ReDoS-safe | RegexVault — Security > API Keys & Tokens
define('STRIPE_API_KEY_PATTERN', '/^(sk|pk|rk)_(live|test)_[0-9a-zA-Z]{24,}$/');
function validate_stripe_api_key(string $input): bool {
return (bool) preg_match(STRIPE_API_KEY_PATTERN, $input);
}
// Example
var_dump(validate_stripe_api_key("sk_live_4eC39HqLyjWDarjtT1zdp7dc")); // bool(true)Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
sk_live_4eC39HqLyjWDarjtT1zdp7dc | sk_4eC39HqLyjWDarjtT1zdp7dc |
pk_test_TYooMQauvdEDq54NiTphI7jx | sk_live_short |
rk_live_aBcDeFgHiJkLmNoPqRsTuVwX | sk_staging_4eC39HqLyjWDarjtT1zdp7dc |
| — | SK_LIVE_4eC39HqLyjWDarjtT1zdp7dc |
When to use this pattern
This pattern is drawn from the Security > API Keys & Tokens category and carries a ReDoS-safe certification. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
Stripe live secret keys found in public repos can drain bank accounts. Use Stripe's restricted keys for specific API operations. Rotate immediately if a live key is exposed. Stripe provides key scanning on GitHub.
Technical Notes
Prefixes: sk=secret key (server-side only), pk=publishable key (client-safe), rk=restricted key. Environments: live (production) vs test. Secret keys (sk_*) must never be exposed in client-side code or logs. Publishable keys (pk_*) are intentionally public.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern