BIN Verification • Pattern Detection • Expiry Checks
Strict Validation Rules Applied
Luhn Algorithm (Mod 10)
Length Validation (12-19 digits)
BIN/IIN Detection
CVV Length by Card Type
Expiry Date Validation
Future Expiry Check
All-Same-Digit Detection
Sequential Pattern Detection
Test Card Rejection
Frequently Asked Questions
Beyond basic Luhn checks, this validator enforces: BIN/IIN detection with length validation per card type, CVV length matching card network standards, expiry date reasonableness (not too old, not too far future), rejection of test/sandbox cards, and detection of suspicious patterns like all-same digits or sequential numbers.
Visa, Mastercard (including 2-series BIN), American Express, Discover, Diners Club, JCB, UnionPay, Maestro, Mir, RuPay, and Troy. Each has specific length and CVV requirements that are strictly enforced.
Never. All validation runs entirely in your browser. No card numbers, expiry dates, or CVV codes leave your device. This tool is 100% client-side JavaScript.
card_number|MM|YY|CVV or card_number|MM|YYYY|CVV. You can use | or : as separator. Lines starting with # are ignored (useful for comments).
Strict mode rejects: known test/sandbox cards (Stripe, PayPal, etc.), cards with all identical digits (e.g., 4444...), sequential patterns (e.g., 1234...), expired cards, cards with expiry too far in future (>10 years), and CVV lengths that don't match the card network standard.
Absolutely not. This tool is strictly for educational and testing purposes — helping developers, QA engineers, and security researchers understand payment card validation standards (ISO/IEC 7812). Never use real card numbers.