Generic Payment Card Number (13–19 digits) Regex for Python
/^(?:[0-9]{4}([\s-])[0-9]{4}\1[0-9]{4}\1[0-9]{1,7}|[0-9]{13,19})$/What this pattern does
This page provides a well-structured, multi-part regular expression for matching generic payment card number (13–19 digits), ported and verified for Python. Financial data validation has zero tolerance for false negatives — a missed invalid entry can corrupt downstream calculations. The snippet below is ready to drop into your Python project — whether you're validating in a Django view, a FastAPI endpoint, or a standalone data processing script.
Python Implementation
# Generic Payment Card Number (13–19 digits)
# ReDoS-safe | RegexVault — Finance > Card Numbers
import re
generic_payment_card_number_1319_digits_pattern = re.compile(r'^(?:[0-9]{4}([\s-])[0-9]{4}\1[0-9]{4}\1[0-9]{1,7}|[0-9]{13,19})$')
def validate_generic_payment_card_number_1319_digits(value: str) -> bool:
return bool(generic_payment_card_number_1319_digits_pattern.fullmatch(value))
# Example
print(validate_generic_payment_card_number_1319_digits("4111111111111111")) # TrueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
4111111111111111 | 41111111111111111111 |
4111 1111 1111 1111 | 4111-1111 1111-1111 |
4111-1111-1111-1111 | abcd1234abcd1234 |
5500005555555559 | — |
378282246310005 | — |
411111111111111 | — |
When to use this pattern
This pattern is drawn from the Finance > Card Numbers category and carries a ReDoS-safe certification. That matters for Python developers because particularly important in Python web servers where CPU-bound regex operations can stall concurrent request handling. 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
Never log full card numbers. Mask to show only the last 4 digits (XXXX XXXX XXXX 1234). PCI-DSS compliance requires minimizing the surface area that touches full PANs.
Technical Notes
Format only — does not validate the Luhn checksum. Always implement Luhn algorithm validation separately. PCI-DSS prohibits storing full PANs (Primary Account Numbers) without encryption.
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