Free Credit Card BIN Checker API
The CC Bins BIN checker API is a free, public REST endpoint for credit card BIN (Bank Identification Number) and IIN (Issuer Identification Number) lookups. No API key is required. Simply send a GET request tohttps://ccbins.co/api/v1/bin/{bin} with a 6–8 digit card prefix and receive a JSON response containing the card brand (Visa, Mastercard, Amex, Discover), card type (credit, debit, prepaid), card level (Classic, Gold, Platinum, Business), issuing bank name and contact, and country of issuance.
The database contains over 376,000 verified BIN/IIN records. The API is CORS-enabled for browser-side integration and supports up to 10 requests per minute per IP on the free tier. For high-volume or offline use cases, the complete BIN database is available as a CSV or SQL download.
Free Credit Card BIN Checker API
Query any 6–8 digit BIN prefix and instantly get the card brand, type, issuing bank, and country — no API key required. Used by checkout engineers, fraud analysts, and payment routing systems.
API Playground & Request Tester
Code Integration Snippet
curl -X GET "https://ccbins.co/api/v1/bin/453271" \ -H "Accept: application/json"Premium BIN Checker Pricing Tiers
Choose the routing intelligence capacity that fits your operation. Free sandbox to offline setups.
Perfect for payment risk teams performing manual BIN audits.
- Unlimited Single Lookups
- Bulk Stream Paste (1k rows)
- Standard Brand/Bank Filters
Query card properties programmatically inside dynamic checkouts.
- 10 reqs/min rate limit per IP
- Full JSON Payload structure
- CORS-enabled public access
Host the complete verified dataset locally to bypass routing latency.
- 376,900+ verified rows (CSV/SQL)
- Weekly database updates (12m)
- Zero API latency or query caps
Buy BIN Database Download - Complete CSV / SQL List
Running lookup queries via network APIs can introduce millisecond delays at checkout. For large volume merchants and fraud scoring engines, buying the complete offline database is the industry standard to guarantee sub-millisecond local queries.
Includes weekly database update notifications delivered via email for 12 months.
Buy Database DownloadEndpoint Information & Request Parameters
The public card BIN API endpoint accepts GET queries. We resolve card attributes by inspecting our local indexed database containing 376k+ entries and performing on-the-fly lookups for unrecognized ranges.
| Parameter | Type | Required | Placement | Description |
|---|---|---|---|---|
| number | string | Yes | URL Path | The card Bank Identification Number prefix. Must be exactly 6, 7, or 8 numeric digits. |
JSON Response Property Schema
| Property | Type | Description |
|---|---|---|
| success | boolean | Indicates if the query completed successfully and the BIN record was resolved. |
| bin | string | The verified card prefix digits queried. |
| scheme | string | Card network network classification (e.g., "visa", "mastercard", "amex", "jcb"). |
| type | string | Card funding type (e.g., "debit", "credit", "prepaid"). |
| brand | string | Card tier level (e.g., "CLASSIC", "PLATINUM", "BUSINESS"). |
| bank | object | Nested object holding issuing bank name, support phone, and primary url. |
| country | object | Country properties including country name, ISO alpha2 code, and emoji flag character. |
Anti-Scraping Protection & Limit Guard
To guarantee service stability for all users, the standard public API endpoint rate-limits unauthenticated IPs to exactly 10 requests per minute. Scraping or bulk crawling queries that trigger recurrent 429 status codes will lead to temporary IP address blocking.
Global Routing & High Performance
Deployed on global edge servers close to your checkout locations. Queries hitting cached SQLite records resolve in under 45ms, preventing any delay or visual latency during checkout form validation processes.
How to Use the BIN Checker API
4 steps to integrate BIN lookup in your application
- 1
Choose your BIN prefix
Extract the first 6, 7, or 8 digits from a card number. Most modern cards use 8-digit BINs (effective 2022 ISO 7812 standard). 6-digit BINs are also fully supported.
BIN = card_number[:8] # e.g. '45327185' - 2
Send a GET request to the endpoint
No authentication header or API key is required. Pass the BIN as a URL path parameter.
GET https://ccbins.co/api/v1/bin/45327185 - 3
Parse the JSON response
The API returns a structured JSON object. Check the success field first, then extract the card metadata you need.
{ "success": true, "bin": "453271", "scheme": "visa", "type": "credit", "brand": "CLASSIC", "bank": { "name": "JP Morgan Chase" }, "country": { "name": "United States", "code": "US", "flag": "🇺🇸" } } - 4
Handle rate limits gracefully
The free tier allows 10 requests/minute per IP. Read X-RateLimit-Remaining from response headers and implement exponential backoff when approaching limits.
if (res.status === 429) { await sleep(60000); retry(); }
Need Enterprise Key Capacity?
If you are executing bulk card audits or require higher throughput thresholds, contact our infrastructure team. We offer dedicated API key credentials with higher limits.
Frequently Asked Questions
Common questions about integrating and using the CC Bins BIN lookup API.