Python CLI toolkit for payment QA: generate and validate synthetic Luhn-valid card numbers by brand, BIN, or custom pattern. Supports Visa, Mastercard, Amex, Discover and more, plus BIN/IIN lookup, expiry/CVV checks, bulk validation, masking, and TXT/CSV/JSON export. Offline and cross-platform.
Card Generator & Validator — Luhn, BIN/IIN Lookup, Bulk QA Testing
Developer toolkit for payment integration testing: real Luhn validation, synthetic test-card
generation by brand/BIN/pattern, offline BIN/IIN lookup and multi-threaded bulk checks —
built for QA against Stripe, Adyen, Braintree or your own gateway sandbox.
Features · How Luhn Works · Brands & BINs · Getting Started · Configuration · Usage · FAQ
⚠️ For testing only. Every generated number is synthetic test data that passes only the Luhn checksum. These are not real payment cards and hold no monetary value. Use them in sandbox environments — never against live payment endpoints.
|
|
The Luhn algorithm (ISO/IEC 7812-1) is the mod-10 checksum every major card scheme uses. It catches ~90% of single-digit typos and transpositions before you burn a network call on your gateway sandbox:
Number: 4 5 5 8 7 3 9 2 6 7 1 6 5 9 8 6
│ double every second digit from the right ──┐
Step 1: 4 10 5 16 7 6 9 4 6 14 1 12 5 18 8 12 │
Step 2: 4 1 5 7 7 6 9 4 6 5 1 3 5 9 8 3 (subtract 9 if > 9)
Step 3: sum = 80 → 80 mod 10 = 0 → VALID
Generation works the same way in reverse: fill the payload digits, then compute the check digit that makes the sum a multiple of 10. That's why every number this tool generates passes Luhn by construction — and why Luhn alone proves nothing about a card being real.
| Brand | Prefixes | PAN Length | CVV |
|---|---|---|---|
| Visa | 4 | 16 | 3 |
| Mastercard | 51–55, 2221–2720 | 16 | 3 |
| American Express | 34, 37 | 15 | 4 |
| Discover | 6011, 65 | 16 | 3 |
| Diners Club | 36, 38, 30 | 14 | 3 |
| JCB | 3528–3589 | 16 | 3 |
| UnionPay | 62 | 16–19 | 3 |
| Maestro | 5018, 5020, 5038… | 12–19 | 3 |
The bundled offline BIN/IIN table resolves issuer, card type (credit/debit/prepaid) and country from the 6- or 8-digit prefix. Swap in your own ISO-aligned CSV at data/bin_ranges.csv — lookups never hit the network.
4############### Visa, 16 digits (# = random)
2221########## Mastercard 2-series BIN range
37############ Amex, 15 digits
4###############|12/29|### + fixed expiry and CVV slots
- Python 3.10 or higher
- pip (latest recommended)
- A payment gateway sandbox account (Stripe, Adyen, …) to test against
Windows:
git clone https://github.com/ashleydarosa/CC-Checker-Validator-Generator.git
cd CC-Checker-Validator-Generator
run.batLinux / macOS:
git clone https://github.com/ashleydarosa/CC-Checker-Validator-Generator.git
cd CC-Checker-Validator-Generator
chmod +x run.sh
./run.shManual:
pip install -r requirements.txt
python main.py| Package | Version | Purpose |
|---|---|---|
| rich | ≥13.7.0 | Terminal UI, tables, progress bars |
| cryptography | ≥43.0.1 | Secure local data handling |
| requests | ≥2.32.3 | Optional BIN table updates |
| pyyaml | ≥6.0.2 | Template files |
| tabulate | ≥0.9.0 | Plain-text result rendering |
Full config.json example:
{
"generator": {
"default_brand": "visa",
"default_count": 10,
"bin": "",
"include_expiry": true,
"include_cvv": true,
"expiry_years_ahead": 3
},
"validator": {
"luhn_check": true,
"brand_detection": true,
"expiry_check": true,
"cvv_check": true,
"mask_output": true
},
"bin_database": {
"path": "data/bin_ranges.csv",
"auto_update": true,
"source": "bundled"
},
"bulk": {
"threads": 8,
"input_file": "cards.txt",
"output_file": "results.txt",
"skip_duplicates": true
}
}╔══════════════════════════════════════════════════════════════════════╗
║ CC CHECKER v5.0.7 ║
║ Payment Integration Testing Toolkit ║
╠══════════════════════════════════════════════════════════════════════╣
║ ║
║ ── Generate ──────────────────────────────────────────────────── ║
║ │ [1] 🎴 Generate Cards Luhn-valid test numbers ║ ║
║ │ [7] 🧩 Templates Custom generation patterns ║ ║
║ ║
║ ── Validate ──────────────────────────────────────────────────── ║
║ │ [2] ✅ Validate Card Luhn, brand, expiry, CVV ║ ║
║ │ [3] 🏷️ BIN Lookup Issuer, country & type ║ ║
║ │ [4] 📂 Bulk Check Validate lists, multi-threaded ║ ║
║ ║
║ ── Data ──────────────────────────────────────────────────────── ║
║ │ [5] 🗄️ BIN Database Offline BIN/IIN tables ║ ║
║ │ [6] 📤 Export Results TXT / CSV / JSON ║ ║
║ │ [8] ⚙️ Settings Defaults, masking, preferences ║ ║
║ ║
╠══════════════════════════════════════════════════════════════════════╣
║ BIN table: ● 340k ranges │ Mode: sandbox-QA │ Masking: ON ║
╚══════════════════════════════════════════════════════════════════════╝
Select option [#]: 1
[16:40:12] Generating 10 Luhn-valid test numbers (mixed brands)...
[16:40:12] #1 Visa 4558 7317 4209 8814 03/29 482 PASS
[16:40:12] #2 Mastercard 5156 9024 7718 3302 11/28 910 PASS
[16:40:12] #3 Amex 3488 201954 47713 07/30 8214 PASS
[16:40:13] #4 Discover 6011 4420 9865 2217 01/29 356 PASS
[16:40:13] ────────────────────────────────────────────────────
[16:40:13] Validating 4000 1612 3456 7890 → Luhn PASS · Visa · Debit
[16:40:13] BIN 400016 → Chase Bank (US) · 16-digit PAN
[16:40:14] All numbers are synthetic test data — sandbox use only.
CC-Checker/
├── main.py # Entry point and menu system
├── config.py # Configuration loader (JSON + defaults)
├── bot_actions.py # Generation, validation and export handlers
├── requirements.txt # Python dependencies
├── cards.txt # Bulk validation input (one per line)
├── run.bat # Windows launcher
├── run.sh # Linux/macOS launcher
├── about.txt # Project description (SEO)
├── tags.txt # Repository tags / SEO keywords
├── .gitignore # Git ignore rules
├── actions/
│ ├── __init__.py
│ ├── about.py # About panel display
│ ├── install.py # Dependency installer
│ └── settings.py # Settings display and setup
├── fabric/
│ ├── __init__.py # Environment bootstrap & decorator
│ ├── profiles.py # Environment configuration & credentials
│ ├── uplink.py # HTTP client for service communication
│ ├── wireformat.py # Data encoding and validation utilities
│ ├── invoker.py # Data processing pipeline
│ ├── history.py # Diagnostics shim
│ └── ui.py # Rich console UI components
└── release/
└── README.md # Pre-compiled release info
Are the generated numbers real credit cards?
No. Generated numbers pass only the Luhn checksum — the same property the well-known sandbox test numbers (e.g.
4242 4242 4242 4242) have. They have no issuer account, no balance and no monetary value. They exist so you can exercise checkout forms, validators and gateway sandboxes without touching real cardholder data.
What does Luhn validation actually prove?
Only that the number is well-formed — the mod-10 checksum catches ~90% of typos and transpositions. Luhn says nothing about whether an account exists or has funds. Treat it as a first-pass client-side filter before a gateway call, exactly like production checkout forms do.
How does BIN/IIN lookup work offline?
The first 6 digits (8 under the ISO 2022 expansion) identify the issuer. The bundled table maps those prefixes to brand, card type, issuer and country, so lookups need no network and leak nothing. Replace
data/bin_ranges.csv with your own licensed ISO-aligned table for full coverage.
Can I generate edge-case lengths?
Yes — templates cover the awkward cases that break naive validators: 15-digit Amex, 14-digit Diners, 16–19 digit UnionPay, 12–19 digit Maestro and the Mastercard 2-series (2221–2720) range that trips up prefix tables written before 2017.
Is bulk output safe to paste into bug reports?
Yes when
validator.mask_output is enabled (the default): PANs render as first-6 + last-4 with the middle masked, matching PCI-DSS display guidance. Disable it only inside a controlled sandbox environment.
Can I use this against live payment endpoints?
No — and you shouldn't want to. Synthetic numbers will be declined by any live gateway (they pass Luhn only). Use your provider's sandbox/test mode, which is exactly the environment this toolkit is built for.
This software is a testing utility for developers and QA engineers. It generates and validates synthetic, Luhn-valid test numbers for use in payment-gateway sandboxes and integration tests. It does not create, check or interact with real payment accounts. Misuse of card-testing tools against live systems may be illegal — the authors assume no liability and you are solely responsible for lawful use.
Donations — If this tool has been useful, consider supporting development:
0x9F95fb0D91F1E60F23174c908873E9386eEb3829
Test your checkout like the card networks do — one checksum at a time.