Live Lookup
Check any card BIN in seconds — see the issuing bank, brand, card type, and country. VISA cards are saved automatically under their country; anything that isn't VISA is flagged so you don't use it.
Enter the first 6 to 8 digits to identify the card issuer, brand, and country.
Recent lookups
Latest BINs looked up through the app.
Analyst Dashboard
Live metrics, trends, and activity across the BIN database — click any tile to drill into the records behind it.
Search activity — last 14 days
Live lookups, verifies, and AI searches per day.
Search actions
How BINs are being searched.
Top countries (valid BINs)
Click a bar to view those records.
Analyst activity
Searches logged per analyst.
Recent searches
View all →Verify
Confirm your BINs against the live card network. A BIN is marked Valid when it's found and its country matches — fast, reliable, and fully logged. Add newly found BINs and tag your HITS here too.
Add similar BINs
The API doesn't return the similar-BIN list on this plan. Paste it from the dashboard's Similar BINs box: enter the primary BIN, paste the list (JSON array or comma-separated), and they're saved as New BIN inheriting the primary's country — verify each one individually anytime.
Mark BINs as HITS ⚡
Flag one or many BINs as HITS (pinged/live on the VISA server). Enter a single BIN or paste a list (JSON array, comma- or space-separated). New BINs are created under Discovery; existing BINs keep their status/country. Every change is logged to history.
Records
Import
Bring your Visa BIN spreadsheet into Cardium. Drop in an Excel file and we'll load every row — no data left behind.
Import Excel
Required columns: bin, brand, type, category, issuer, alpha_2, alpha_3, country, latitude, longitude, bank_phone, bank_url — matched by name, so a file exported from Cardium re-imports as-is (extra columns are ignored). Replace wipes the table; Append adds to it.
Loads BIN records only. Verification state, discovery links, history and generated cards from an export are not restored — this is a data import, not a full backup restore.
Card Testing
Raise a BIN for card testing, track its status, then mark it Hit or No-Hit. A Hit flags the BIN in the database and the AI assistant starts suggesting it.
Raise a test ticket
Mark a card as HIT
Paste a full 16-digit card that hit. Cardium live-checks its BIN (respecting the revalidation window), flags it in the database, and adds it to the Card Repository for everyone.
Marked HIT cards
Cards confirmed as a verified HIT — who marked each and when. Unmarking clears the card's verified-HIT status, and the BIN's HIT flag too if nothing else still keeps it. Requires your Cardium password.
Tickets
Submit Card
Log a card entry. Saved to its own table and exportable as an Excel sheet in the exact form layout. Not linked to the BIN database.
New entry
Entries
| ID | Start time | Completion time | Name | Last modified | Card Country | Card last 4 | Card Number | File 1 | File 2 |
|---|
Generate Cards
Create unique, Luhn-valid test card numbers from any BIN — for safe payment testing only. These are never real cards.
Generate test cards
Each card gets a random expiry and CVV, Luhn-valid, stored server-side. These are never real cards.
Generated cards repository
Every Luhn-valid test card the team has generated — visible to all users. Tick cards and submit them straight into the Submit Card database.
Analyst Tracker
Log each merchant-compliance test case in one structured form. Your entries are private to you; managers and admins see the master view across all analysts and can export it. WE Date (week-ending Friday) is computed automatically.
Start new case
Enter the URL and the country you'll test from. We check whether it's already been tested before opening the form.
New test case
Fields follow the daily tracker sheet. Required fields are marked. Constant fields are pre-filled — edit if needed.
My cases
Search History
Every BIN search and lookup, logged and searchable — who searched what, when, the result, verification status, source, and whether it was already known (duplicate).
BIN search log
Live BIN lookups, per-row verifications, and AI-assisted searches. Filter and drill in.
Admin Control Panel
Connection, database health, team access, data export, and the security audit trail — all in one place. Admin only.
Database
New BINs are discovered from the API's similar-BIN list and stay “New” until individually verified.
AI assistant settings
Revalidation TTL — how fresh an already-valid BIN must be before the assistant re-checks it live (Already-validated / HITS / Mix pools). Lower burns more live API quota. Default 72 hours; 0 = always re-check.
Daily backup
BIN data, Submit Card data, and the Card Repository are backed up automatically every day at 02:00 IST to a folder on this VM. Leave the path blank to save to the VM user's Documents folder, or set a specific destination below. Files are named BIN_Backup_YYYY-MM-DD_HHMM.db, SubmitCard_Backup_YYYY-MM-DD_HHMM.xlsx, and CardRepository_Backup_YYYY-MM-DD_HHMM.xlsx.
HITS neighbor discovery
When a card is marked Hit, automatically verify its BIN's range-neighbours against the live API and add any new valid BINs. Off by default — it spends API quota. Neighbour BINs are kept out of the AI Assistant's "New BIN" suggestions.
Team & access
Invite teammates and set their role. Each new user sets their own password and authenticator app from a one-time invite. Lock-outs after 5 bad codes are cleared here.
Export database
Download a live snapshot of every BIN table (bins, discovery, history, non-VISA, generated cards) as an Excel file — all columns, current data. Credentials are never exported.
Security audit log
Recent sign-ins, MFA failures, enrollments, admin actions and more — newest first (last 200 events).
Privacy Policy
Cardium ("the Service") is an internal, access-controlled tool operated by Safient for authorized staff. This policy explains what the Service collects and how it is used.
1. What we collect
- Account data — your work email (used as your username), role, authentication credentials (password hash and TOTP secret), and account status.
- Usage data — BIN searches, verifications, generated test cards, sign-in events, last-login time, and administrative actions, recorded in an audit log for security and accountability.
- Operational data — the Bank Identification Numbers and related card-network attributes the Service is built to manage. The Service does not store full payment card numbers.
2. How we use it
To authenticate you, enforce role-based access, operate and secure the Service, maintain an audit trail, and meet Safient's legal and compliance obligations. We do not sell your data or use it for advertising.
3. Sharing
Data is accessible only to authorized Safient personnel and the third-party card-network verification provider used to confirm BIN validity. We disclose data to authorities only where required by law.
4. Retention & security
Data is retained while your account is active and as required for audit and legal purposes, then deleted or anonymized. Access is protected by password authentication, optional multi-factor authentication, encrypted sessions, and role-based permissions.
5. Your choices
Access, correction, or deletion requests go to your Safient administrator. Because this is an internal tool, use is governed by your employment or contractor agreement.
6. Contact
Safient — www.safient.ai.
Terms & Conditions
By accessing Cardium you agree to these terms. If you do not agree, do not use the Service.
1. Authorized use
Cardium is a proprietary internal tool provided to authorized Safient staff for BIN verification, intelligence, and payment-system testing. Access is granted by invitation and may be revoked at any time. You are responsible for activity under your account and for keeping your credentials confidential.
2. Acceptable use
Generated card numbers are Luhn-valid test artifacts for authorized testing only. You must not use the Service or its output for fraud, unauthorized transactions, or any unlawful purpose. Misuse may result in account termination and legal action.
3. Intellectual property
Cardium, including its software, design, and content, is the proprietary property of Safient. All rights reserved. No license is granted except the limited right to use the Service as an authorized user.
4. No warranty
The Service is provided "as is" without warranties of any kind. BIN and verification results are provided for operational use and may contain inaccuracies.
5. Limitation of liability
To the maximum extent permitted by law, Safient is not liable for any indirect, incidental, or consequential damages arising from use of the Service.
6. Changes
Safient may update these terms; continued use after changes constitutes acceptance.
7. Contact
Safient — www.safient.ai.
Legal & Copyright
© 2026 Safient. All rights reserved.
Cardium is a proprietary product of Safient. The Cardium name, logo, software, and all associated materials are owned by Safient and protected by copyright and other intellectual-property laws. Unauthorized copying, distribution, modification, reverse engineering, or use is prohibited.
Trademarks
"Cardium" and "Safient" are marks of Safient. VISA and other card-network names are the property of their respective owners; their use here is descriptive only and implies no affiliation or endorsement.
Third-party notices
Cardium is built on the Node.js runtime and uses a third-party card-network verification API. Card-network data belongs to its respective owners.
Contact
Safient — www.safient.ai.